Skip to content
OpenAdvisories
Critical openSUSE-SU-2026:21497-1 5 CVEs

Security update for perl-YAML-Syck

Published Jul 29, 2026 · Updated Jul 31, 2026

Summary

This update for perl-YAML-Syck fixes the following issues:

Changes in perl-YAML-Syck:

- updated to 1.470.0 (1.47)
[Security]
- Fix four libsyck memory-safety CVEs reachable from the default
YAML::Syck::Load() path on untrusted input with no special flags
(reported by Paul Johnson via CPANSec, PR #213):
- CVE-2026-57075 (CWE-125): out-of-bounds read in the base64 decoder
caused by signed-char indexing of the decode table on !!binary input
bsc#1271632
- CVE-2026-57076 (CWE-416): use-after-free of an anchor key string
shared between the node and the anchors table
bsc#1271633
- CVE-2026-57077 (CWE-125): one-byte out-of-bounds read in the lexer
newline scan during block-scalar parsing (incomplete-fix follow-on
to CVE-2025-11683)
bsc#1271634
- CVE-2026-13713 (CWE-416/CWE-415): use-after-free / double-free of an
anchor node on anchor redefinition, a remote-crash DoS from a
7-byte input
bsc#1271631
- Harden syck_base64dec() to bounds-check each read so it cannot run past
a non-NUL-terminated input buffer (defense-in-depth for callers passing
raw buffers; PR #213)
[Bug Fixes]
- Fix: enforce $MaxDepth on Load to prevent C-stack exhaustion from
deeply nested YAML/JSON input; YAML::Syck and JSON::Syck Load now
default to 512, matching Dump (PR #204)
- Fix: emit YAML canonical forms (.nan, .inf, -.inf) for NaN/Inf values
in Dump so they roundtrip with ImplicitTyping instead of reloading as
plain strings (PR #201)
[Maintenance]
- CI: add an AddressSanitizer job that builds the XS with
-fsanitize=address and runs the suite plus the CVE trigger inputs to
catch libsyck memory-safety defects; de-pin the libasan version so it
tracks the runner's GCC (PR #213)

- updated to 1.460.0 (1.46)
[Bug Fixes]
- Fix: preserve string nature of numeric-looking values in Dump; pure
strings (POK only, no IOK/NOK) are now quoted to maintain roundtrip
fidelity (GH #199, PR #200)
- Fix: accept trailing commas in flow sequences and mappings
([a, b,] and {a: 1,}), valid per YAML 1.0/1.1/1.2 spec
(GH #195, PR #196)

[Maintenance]
- CI: upgrade install-with-cpm to v2 for compatibility with Perl
versions prior to 5.24 in perldocker containers (GH #197, PR #198)
- Clean up MANIFEST.SKIP: add #!include_default, remove redundant
entries, exclude .claude/ from distribution

Fixed packages 1

ReleasePackageFixed in
openSUSE · Leap 16.0 perl-YAML-Syck 1.470.0-bp160.1.1

Vulnerabilities 5

  • Critical 9.1

    YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via a signed-char lookup-table index in syck_base64dec

    YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via a signed-char lookup-table index in syck_base64dec. The base64 decoder in the bundled libsyck indexes the 256-entry static table b64_xtable with a signed char, so any !!binary byte >= 0x…

  • High 7.8

    YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor

    YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor. In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node->anchor, freed when the node…

  • High 7.7

    YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via an unbounded newline scan in newline_len

    YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via an unbounded newline scan in newline_len. In the bundled libsyck newline_len and is_newline dereference the scan pointer, and the following byte for a "\r\n" pair, with no NUL-terminator…

  • Medium 6.5

    YAML::Syck versions before 1.36 for Perl has missing Null-Terminators which causes Out-of-Bounds Read and potential Information Disclosure

    YAML::Syck versions before 1.36 for Perl has missing null-terminators which causes out-of-bounds read and potential information disclosure Missing null terminators in token.c leads to but-of-bounds read which allows adjacent variable to be read The issue is s…

  • Medium 6.2

    YAML::Syck versions before 1.47 for Perl allow a use-after-free and double-free via an anchor node freed while still on the parser value stack

    YAML::Syck versions before 1.47 for Perl allow a use-after-free and double-free via an anchor node freed while still on the parser value stack. In the bundled libsyck, when an anchor name is redefined or removed, syck_hdlr_add_anchor and syck_hdlr_remove_anch…

References

  • report
    https://bugzilla.suse.com/1271631
  • report
    https://bugzilla.suse.com/1271632
  • report
    https://bugzilla.suse.com/1271633
  • report
    https://bugzilla.suse.com/1271634
  • web
    https://www.suse.com/security/cve/CVE-2025-11683
  • web
    https://www.suse.com/security/cve/CVE-2026-13713
  • web
    https://www.suse.com/security/cve/CVE-2026-57075
  • web
    https://www.suse.com/security/cve/CVE-2026-57076
  • web
    https://www.suse.com/security/cve/CVE-2026-57077