Loading vulnerability…
CVE-2026-57075 is an out-of-bounds read in YAML::Syck versions before 1.47, within the bundled libsyck base64 decoder, syck_base64dec. The decoder uses signed character values to index a 256-entry base64 lookup table. On platforms where char is signed, a byte with its high bit set in a YAML !!binary scalar is sign-extended to a negative index, causing a read before the lookup table. The vulnerable decoder is reachable through the default YAML::Syck Load and LoadFile parsing paths and does not require enabling blessed-object or code loading.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remotely exploitable, low-complexity vulnerability affecting the FreeBSD p5-yaml-syck (YAML-Syck) package. The cited CVSS vector indicates high confidentiality and availability impact, with no integrity impact; the content does not identify the underlying flaw type.
A YAML::Syck/libsyck out-of-bounds read in the Base64 decoder. An untrusted YAML !!binary scalar containing a byte with the high bit set can cause a negative lookup-table index on the default Load or LoadFile path; the value read may surface in decoded output.
An out-of-bounds read vulnerability in libsyck's base64 decoder reachable via the default YAML::Syck::Load() path when parsing untrusted !!binary input.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.