{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-57076 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-57076 is a high-severity use after free vulnerability in TODDR YAML::Syck, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57076 and fix it if it is affected.\n\nWhat it is: CVE-2026-57076 is a high-severity use after free vulnerability in TODDR YAML::Syck, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57076 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-57076/ (Markdown: https://insights.sbomify.com/CVE-2026-57076/index.md)","id":"CVE-2026-57076","markdown":"https://insights.sbomify.com/CVE-2026-57076/index.md","name":"CVE-2026-57076","record":{"aliases":["ALPINE-CVE-2026-57076","AZL-109502","AZL-92910","BELL-CVE-2026-57076","DEBIAN-CVE-2026-57076","GHSA-q6x2-vfpr-9j7p","UBUNTU-CVE-2026-57076"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Perl YAML library","requires_auth":"low_privilege","summary":"Attackers can trigger a heap use-after-free in YAML::Syck by crafting malicious YAML documents, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.\n\nIn the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-\u003eanchor, freed when the node is freed, and as the key in the parser's anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.\n\nAny caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.","ecosystems":[],"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":"Use after free in YAML::Syck","id":"CVE-2026-57076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via an unbounded newline scan in newline_len","id":"CVE-2026-57077"},"packages":[],"prev":{"headline":"Memory corruption in YAML::Syck","id":"CVE-2026-57075"},"products":["YAML::Syck"],"published":"2026-07-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-17","vendors":["TODDR"]},"summary":"Attackers can trigger a heap use-after-free in YAML::Syck by crafting malicious YAML documents, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-57076/"}