Bug 2501583 (CVE-2026-57076) - CVE-2026-57076 YAML-Syck: YAML::Syck: Heap use-after-free via anchor name reuse
Summary: CVE-2026-57076 YAML-Syck: YAML::Syck: Heap use-after-free via anchor name reuse
Keywords:
Status: NEW
Alias: CVE-2026-57076
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2501654 2501655
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-16 23:03 UTC by OSIDB Bzimport
Modified: 2026-07-17 03:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-16 23:03:15 UTC
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 is freed, and as the key in the parser's anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.

Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.


Note You need to log in before you can comment on or make changes to this bug.