Описание
YAML versions before 1.27_001 for Perl allow a loaded perl/glob document to replace any package variable, which can lead to arbitrary code execution.
A perl/glob document names a package and a symbol, and supplies the value assigned to it. Nothing restricts the name, so the target can be @INC or YAML's own load options.
A perl/glob document that sets $YAML::LoadCode or $YAML::UseCode turns on code loading, which is off by default, for every later Load() in the process. A perl/code document is then passed to a string eval, so an attacker who supplies two documents to separate Load() calls in one process can execute arbitrary Perl code.
A flaw was found in perl-yaml. This vulnerability can lead to arbitrary code execution because the parser fails to restrict package variable modifications specified in YAML documents. An attacker capable of submitting crafted YAML input can overwrite internal configuration settings to enable code loading, allowing them to execute arbitrary Perl code within the running process.
Отчет
This vulnerability is rated as Important severity because successful exploitation allows an attacker to achieve arbitrary code execution within the context of the running Perl application, potentially compromising the host system. Although embedded code evaluation is disabled by default in Red Hat Enterprise Linux packages, an attacker supplying malicious serialized YAML data can bypass these safeguards by modifying package-level variables and runtime configurations in memory. Exploitation requires the target application to accept untrusted inputs and process them across multiple deserialization calls within a persistent execution context.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | perl-YAML | Not affected | ||
| Red Hat Enterprise Linux 6 | perl-YAML | Not affected | ||
| Red Hat Enterprise Linux 7 | perl-YAML | Affected | ||
| Red Hat Enterprise Linux 9 | perl-YAML | Not affected | ||
| Red Hat Enterprise Linux 8 | perl-YAML | Fixed | RHSA-2026:93471 | 02.11.2026 |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
EPSS
8.1 High
CVSS3
Связанные уязвимости
YAML versions before 1.27_001 for Perl allow a loaded perl/glob document to replace any package variable, which can lead to arbitrary code execution. A perl/glob document names a package and a symbol, and supplies the value assigned to it. Nothing restricts the name, so the target can be @INC or YAML's own load options. A perl/glob document that sets $YAML::LoadCode or $YAML::UseCode turns on code loading, which is off by default, for every later Load() in the process. A perl/code document is then passed to a string eval, so an attacker who supplies two documents to separate Load() calls in one process can execute arbitrary Perl code.
YAML versions before 1.27_001 for Perl allow a loaded perl/glob document to replace any package variable, which can lead to arbitrary code execution. A perl/glob document names a package and a symbol, and supplies the value assigned to it. Nothing restricts the name, so the target can be @INC or YAML's own load options. A perl/glob document that sets $YAML::LoadCode or $YAML::UseCode turns on code loading, which is off by default, for every later Load() in the process. A perl/code document is then passed to a string eval, so an attacker who supplies two documents to separate Load() calls in one process can execute arbitrary Perl code.
YAML versions before 1.27_001 for Perl allow a loaded perl/glob docume ...
YAML versions before 1.27_001 for Perl allow a loaded perl/glob document to replace any package variable, which can lead to arbitrary code execution. A perl/glob document names a package and a symbol, and supplies the value assigned to it. Nothing restricts the name, so the target can be @INC or YAML's own load options. A perl/glob document that sets $YAML::LoadCode or $YAML::UseCode turns on code loading, which is off by default, for every later Load() in the process. A perl/code document is then passed to a string eval, so an attacker who supplies two documents to separate Load() calls in one process can execute arbitrary Perl code.
EPSS
8.1 High
CVSS3