CVE-2026-57075
Out-of-bounds read in YAML::Syck base64 decoder can leak memory when parsing !!binary.
Is CVE-2026-57075 being exploited?
Not confirmed. CVE-2026-57075 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-57075?
CVE-2026-57075 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57075?
Yes. A fix has been recorded for CVE-2026-57075. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57075 affect?
CVE-2026-57075 affects YAML::Syck < 1.47 (Perl module), Perl apps using Load/LoadFile, Apps bundling libsyck. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57075?
Upgrade to YAML::Syck >=1.47 and avoid loading untrusted YAML; validate/sanitize inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Parsing crafted !!binary YAML triggers an out-of-bounds read, allowing memory contents to be returned in decoded output (information disclosure).
Immediate action required
- affected< 1.47
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.