Bug 2448277 (CVE-2026-4177) - CVE-2026-4177 perl-YAML-Syck: YAML::Syck versions through 1.36 for Perl has several potential security vulnerabilities including a high-severity heap buffer overflow in the YAML emitter
Summary: CVE-2026-4177 perl-YAML-Syck: YAML::Syck versions through 1.36 for Perl has s...
Keywords:
Status: NEW
Alias: CVE-2026-4177
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2448280 2448281
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-16 23:02 UTC by OSIDB Bzimport
Modified: 2026-04-15 13:52 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:6470 0 None None None 2026-04-02 12:19:04 UTC
Red Hat Product Errata RHSA-2026:8311 0 None None None 2026-04-15 13:52:21 UTC

Description OSIDB Bzimport 2026-03-16 23:02:07 UTC
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.

Comment 2 errata-xmlrpc 2026-04-02 12:19:03 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:6470 https://access.redhat.com/errata/RHSA-2026:6470

Comment 3 errata-xmlrpc 2026-04-15 13:52:20 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:8311 https://access.redhat.com/errata/RHSA-2026:8311


Note You need to log in before you can comment on or make changes to this bug.