{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-11683 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-11683 is a medium-severity vulnerability in TODDR YAML::Syck, published on 16 Oct 2025. 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-2025-11683 and fix it if it is affected.\n\nWhat it is: CVE-2025-11683 is a medium-severity vulnerability in TODDR YAML::Syck, published on 16 Oct 2025. 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-2025-11683 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-2025-11683/ (Markdown: https://insights.sbomify.com/CVE-2025-11683/index.md)","id":"CVE-2025-11683","markdown":"https://insights.sbomify.com/CVE-2025-11683/index.md","name":"CVE-2025-11683","record":{"aliases":["AZL-109466","AZL-109514","BELL-CVE-2025-11683","DEBIAN-CVE-2025-11683","GHSA-gr2g-vmxj-5cv8","UBUNTU-CVE-2025-11683","USN-7844-1","openSUSE-SU-2026:10746-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Perl YAML library","requires_auth":"none","summary":"Attackers can read adjacent memory via out-of-bounds read in YAML::Syck when processing complex YAML files, potentially disclosing sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"yaml\\","vendor":"toddr"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"YAML::Syck versions before 1.36 for Perl has missing null-terminators which causes out-of-bounds read and potential information disclosure\n\nMissing null terminators in token.c leads to but-of-bounds read which allows adjacent variable to be read\n\nThe issue is seen with complex YAML files with a hash of all keys and empty values.  There is no indication that the issue leads to accessing memory outside that allocated to the module.","ecosystems":["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":"Information disclosure in YAML::Syck","id":"CVE-2025-11683","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":1,"n_references":2,"next":{"headline":"Gi-docgen: reflected dom xss in gi-docgen","id":"CVE-2025-11687"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.450.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:10746-1"}],"prev":{"headline":"Stored Cross-Site Scripting in Perx Customer Engagement \u0026 Loyalty Platform","id":"CVE-2025-11682"},"products":["YAML::Syck"],"published":"2025-10-16","related":[{"cvss_score":9.1,"headline":"Memory corruption in YAML::Syck","id":"CVE-2026-4177","kev_date_added":null,"published":"2026-03-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-16","vendors":["TODDR"]},"summary":"Attackers can read adjacent memory via out-of-bounds read in YAML::Syck when processing complex YAML files, potentially disclosing sensitive information.","url":"https://insights.sbomify.com/CVE-2025-11683/"}