libyaml-perl: YAML versions before 1.27_001 for Perl allow a loaded perl/glob document to replace any package variable, which can l...
CVE-2019-25777 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2019-25777, released October 5, 2026. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libyaml-perl · Debian 12.15 (bookworm) | 1.29-1 | DEBIAN-CVE-2019-25777 | Oct 5, 2026 |
| libyaml-perl · Debian 13.5 (trixie) | 1.29-1 | DEBIAN-CVE-2019-25777 | Oct 5, 2026 |
| libyaml-perl · Debian 14 | 1.29-1 | DEBIAN-CVE-2019-25777 | Oct 5, 2026 |
| libyaml-perl · Ubuntu 18.04.6 LTS (bionic) | 1.24-1ubuntu0.1~esm1 | libyaml-perl 1.24-1ubuntu0.1~esm1 | Oct 16, 2026 |
| perl-YAML · RHEL 8 | 0:1.24-4.module+el8.10.0+25073+d1062575 | RHSA-2026:93471 | Nov 3, 2026 |
| perl-YAML · almalinux 8 | 1.24-4.module_el8.10.0+4341+ab0ec422 | ALSA-2026:93471 | Nov 7, 2026 |
| perl-YAML · ol 8 | 0:1.24-4.module+el8.10.0+91104+f3b3492f | ELSA-2026-93471 | Nov 7, 2026 |
| perl-YAML · rocky 8 | 0:1.24-4.module+el8.10.0+40403+bd06a93a | RLSA-2026:93471 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.