libyaml-syck-perl: YAML::Syck versions before 1.38 for Perl has an out-of-bounds read
CVE-2026-5089 is fixed in 5 products on 1 platform, first by ALAS2023-2026-1769, released May 25, 2026. It is not reported as exploited. Patch Radar priority: High.
YAML::Syck versions before 1.38 for Perl has an out-of-bounds read. The base60 (sexagesimal) parsing code in perl_syck.h has a buffer underflow bug in both int#base60 and float#base60 handlers. When processing the leftmost segment of a colon-separated value (e.g., the 1 in 1:30:45), the inner while loop can decrement a pointer past the start of the string buffer: while ( colon >= ptr && *colon != ':' ) { colon--; } if ( *colon == ':' ) *colon = '\0'; // colon may be ptr-1 here When no colon is found (final/leftmost segment), colon becomes ptr-1, and the subsequent *colon dereference reads one byte before the allocated buffer.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libyaml-syck-perl · Debian 12.15 (bookworm) | 1.34-2+deb12u3 | DEBIAN-CVE-2026-5089 | May 27, 2026 |
| libyaml-syck-perl · Debian 13.5 (trixie) | 1.34-2+deb13u3 | DEBIAN-CVE-2026-5089 | May 27, 2026 |
| libyaml-syck-perl · Debian 14 | 1.36-3 | DEBIAN-CVE-2026-5089 | May 27, 2026 |
| perl-YAML-Syck · amzn 2023 | 1.37-1.amzn2023.0.3 | ALAS2023-2026-1769 | May 25, 2026 |
| perl-YAML-Syck · opensuse-leap 16.0 | 1.450.0-bp160.2.1 | OPENSUSE-SU-2026:20938-1 | Jun 10, 2026 |
| perl-YAML-Syck-debuginfo · amzn 2023 | 1.37-1.amzn2023.0.3 | ALAS2023-2026-1769 | May 25, 2026 |
| perl-YAML-Syck-debugsource · amzn 2023 | 1.37-1.amzn2023.0.3 | ALAS2023-2026-1769 | May 25, 2026 |
| perl-YAML-Syck-tests · amzn 2023 | 1.37-1.amzn2023.0.3 | ALAS2023-2026-1769 | May 25, 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.