CVE-2026-4177
Toddr Yaml::syck buffer overflow
- Published16 Mar 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:6470
- https://access.redhat.com/errata/RHSA-2026:8311
- https://access.redhat.com/security/cve/CVE-2026-4177
- https://bugzilla.redhat.com/show_bug.cgi?id=2448277
- https://github.com/cpan-authors/YAML-Syck/commit/e8844a31c8cf0052914b198fc784ed4e6b8ae69e.patch
- https://metacpan.org/release/TODDR/YAML-Syck-1.37_01/changes#L21
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4177.json
- http://www.openwall.com/lists/oss-security/2026/03/16/6
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-4177 being actively exploited?
CVE-2026-4177 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.
How severe is CVE-2026-4177?
CVE-2026-4177 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.60% probability of exploitation.
Which products are affected by CVE-2026-4177?
Affected products include Toddr Yaml::syck.
How do I fix CVE-2026-4177?
Upgrade affected software to a fixed version, for example Toddr Yaml::syck 1.37 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-4177 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.