CVE-2026-4177 | YAML::Syck versions through 1.36 for Perl has several potential security vulnerabilities including a high-severity heap buffer overflow in the YAML emitter

YAML::Syck versions through 1.36 for Perl has several potential security vulnerabilities including a high-severity heap buffer overflow in the YAML emitter. The heap overflow occurs when class names exceed the initial 512-byte allocation. The base64 decoder could read past the buffer end on trailing newlines. strtok mutated n->type_id in place, corrupting shared node data. A memory leak occurred in syck_hdlr_add_anchor when a node already had an anchor. The incoming anchor string 'a' was leaked on early return.

Published: 2026-03-16 Last update: 2026-03-23 Assigner: 9b29abf9-4ab0-4765-b253-1875cd9b441e Source: 9b29abf9-4ab0-4765-b253-1875cd9b441e
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4177 is rated Low Risk (36.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-4177

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-17 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4177

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-4177

OS Trackers for CVE-2026-4177

vendor priority summary link
debian not yet assigned CVE-2026-4177 not yet assigned priority: Debian including 1 source packages (libyaml-syck-perl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-4177
redhat high — https://access.redhat.com/security/cve/CVE-2026-4177
ubuntu medium CVE-2026-4177 medium priority: Ubuntu including 1 source packages (libyaml-syck-perl), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 6, released 1. https://ubuntu.com/security/CVE-2026-4177

Affected software / configurations for CVE-2026-4177

Vendor Product Version Raw CPE
toddr yaml::syck < 1.37 cpe:2.3:a:toddr:yaml\:\:syck:*:*:*:*:*:perl:*:*

References for CVE-2026-4177

cvelogic Threat Intelligence