CVE Catalog

CVE-2026-57076

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.19%

8th percentile - higher than 8% of all known CVEs

Summary

A heap use-after-free vulnerability exists in YAML::Syck for Perl before version 1.47. The issue occurs when an anchor name is reused as a key in the anchors table in syck_hdlr_add_anchor, leading to reading freed heap memory.

Risk Assessment

An attacker can supply a malicious YAML document that redefines an anchor, causing a read of freed memory. This could lead to disclosure of sensitive information, application crash, or potentially arbitrary code execution.

Recommendation

Immediately update YAML::Syck to version 1.47 or later. If an update is not possible, avoid processing untrusted YAML documents using Load or LoadFile functions.

Other vulnerabilities in YAML::Syck

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS