{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4177 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-4177 is a critical memory corruption vulnerability in TODDR YAML::Syck, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4177 and fix it if it is affected.\n\nWhat it is: CVE-2026-4177 is a critical memory corruption vulnerability in TODDR YAML::Syck, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4177 in the wild and no public exploit code.\n\nAffected product: TODDR YAML::Syck. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4177/ (Markdown: https://insights.sbomify.com/CVE-2026-4177/index.md)","id":"CVE-2026-4177","markdown":"https://insights.sbomify.com/CVE-2026-4177/index.md","name":"CVE-2026-4177","record":{"aliases":["ALPINE-CVE-2026-4177","ALSA-2026:6470","AZL-109508","AZL-79977","BELL-CVE-2026-4177","DEBIAN-CVE-2026-4177","DSA-6175-1","GHSA-72r6-p2x3-g9gj","MGASA-2026-0058","RHSA-2026:6470","RHSA-2026:8311","RLSA-2026:6470","UBUNTU-CVE-2026-4177","openSUSE-SU-2026:10551-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl YAML library","requires_auth":"none","summary":"Heap buffer overflow and memory corruption in YAML::Syck allow attackers to execute code or cause denial of service via crafted YAML input.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"yaml\\","vendor":"toddr"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"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.\n\nThe heap overflow occurs when class names exceed the initial 512-byte allocation.\n\nThe base64 decoder could read past the buffer end on trailing newlines.\n\nstrtok mutated n-\u003etype_id in place, corrupting shared node data.\n\nA 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.","ecosystems":["AlmaLinux:8","Red Hat:enterprise_linux:8::crb","Red Hat:rhel_els:7","Rocky Linux:8","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in YAML::Syck","id":"CVE-2026-4177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":8,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-4178"},"packages":[{"ecosystem":"AlmaLinux:8","fixed":["1.30-6.el8_10"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck","purl":"pkg:rpm/almalinux/perl-YAML-Syck","source":"ALSA-2026:6470"},{"ecosystem":"Red Hat:enterprise_linux:8::crb","fixed":["0:1.30-6.el8_10"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck","purl":"pkg:rpm/redhat/perl-YAML-Syck","source":"RHSA-2026:6470"},{"ecosystem":"Red Hat:enterprise_linux:8::crb","fixed":["0:1.30-6.el8_10"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck-debuginfo","purl":"pkg:rpm/redhat/perl-YAML-Syck-debuginfo","source":"RHSA-2026:6470"},{"ecosystem":"Red Hat:enterprise_linux:8::crb","fixed":["0:1.30-6.el8_10"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck-debugsource","purl":"pkg:rpm/redhat/perl-YAML-Syck-debugsource","source":"RHSA-2026:6470"},{"ecosystem":"Red Hat:rhel_els:7","fixed":["0:1.27-3.el7_9.1"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck","purl":"pkg:rpm/redhat/perl-YAML-Syck","source":"RHSA-2026:8311"},{"ecosystem":"Red Hat:rhel_els:7","fixed":["0:1.27-3.el7_9.1"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck-debuginfo","purl":"pkg:rpm/redhat/perl-YAML-Syck-debuginfo","source":"RHSA-2026:8311"},{"ecosystem":"Rocky Linux:8","fixed":["0:1.30-6.el8_10"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck","purl":"pkg:rpm/rocky-linux/perl-YAML-Syck?distro=rocky-linux-8\u0026epoch=0","source":"RLSA-2026:6470"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.440.0-1.1"],"introduced":["0"],"last_affected":[],"package":"perl-YAML-Syck","purl":"pkg:rpm/opensuse/perl-YAML-Syck\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10551-1"}],"prev":{"headline":"Supply chain in perl","id":"CVE-2026-4176"},"products":["YAML::Syck"],"published":"2026-03-16","related":[{"cvss_score":6.5,"headline":"Information disclosure in YAML::Syck","id":"CVE-2025-11683","kev_date_added":null,"published":"2025-10-16"}],"sources":[{"class":"attribution","licence":"MIT","name":"AlmaLinux","prefix":"ALSA"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"BSD","name":"Rocky Linux","prefix":"RLSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["TODDR"]},"summary":"Heap buffer overflow and memory corruption in YAML::Syck allow attackers to execute code or cause denial of service via crafted YAML input.","url":"https://insights.sbomify.com/CVE-2026-4177/"}