Is CVE-2026-57075 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57075 being exploited in the wild.

How severe is CVE-2026-57075?

Informational severity, with a CVSS score of 5.3, published 16 July 2026.

Which products and versions are affected?

TODDR (CPAN) YAML::Syck versions before 1.47.

Is there a fix for CVE-2026-57075?

A patch was published on 2026-07-13: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-57075 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-57075?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57075: YAML::Syck out-of-bounds read in syck_base64dec

CVE-2026-57075 · Severity: info · CVSS 5.3 · Published 2026-07-16

YAML::Syck, a Perl library used for processing YAML data, contains a flaw in how it handles binary data. An attacker can provide a specially crafted YAML document that causes the library to read memory outside of its intended boundaries. This could allow an attacker to potentially access sensitive information that was not meant to be exposed.

Quick answers

Is CVE-2026-57075 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57075 being exploited in the wild.
How severe is CVE-2026-57075?: Informational severity, with a CVSS score of 5.3, published 16 July 2026.
Which products and versions are affected?: TODDR (CPAN) YAML::Syck versions before 1.47.
Is there a fix for CVE-2026-57075?: A patch was published on 2026-07-13: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57075 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-57075?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds read vulnerability exists in the bundled libsyck C library within YAML::Syck. The base64 decoder in syck_base64dec indexes a 256-entry static table (b64_xtable) using a signed char. When processing a !!binary node containing bytes with the high bit set (>= 0x80), the index sign-extends to a negative value, resulting in a read before the table's memory space. This can be triggered via the default Load or LoadFile paths on untrusted input. The leaked memory values can surface in the resulting decoded output. The issue is fixed in version 1.47 by casting the index to an unsigned char.

Affected products

TODDR (CPAN) YAML::Syck versions before 1.47

Timeline

2026-07-13: patched: Fix committed to repository
2026-07-16: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.