{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75432 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75432 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75432 is a medium-severity vulnerability in n/a, published on 22 Sep 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-75432 and fix it if it is affected.\n\nWhat it is: CVE-2026-75432 is a medium-severity vulnerability in n/a, published on 22 Sep 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-75432 in the wild and no public exploit code.\n\nAffected product: n/a. 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-75432/ (Markdown: https://insights.sbomify.com/CVE-2026-75432/index.md)","id":"CVE-2026-75432","markdown":"https://insights.sbomify.com/CVE-2026-75432/index.md","name":"CVE-2026-75432","record":{"aliases":["DEBIAN-CVE-2026-75432","GHSA-8gfp-q62c-5p3c","UBUNTU-CVE-2026-75432"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"C++ YAML parser","requires_auth":"none","summary":"A remote attacker can obtain sensitive information from the yaml-cpp library via flaws in the scanner component.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-822","name":"Untrusted Pointer Dereference"}],"description":"An issue in yaml-cpp 0.9.0 allows a remote attacker to obtain sensitive information via the src/scanner.cpp, Scanner::PopIndent(), and Scanner::PushIndentTo() components","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2026-75432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-75438"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2026-75431"},"products":["n/a"],"published":"2026-09-22","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":"partial"},"state":"PUBLISHED","updated":"2026-10-03","vendors":["n/a"]},"summary":"A remote attacker can obtain sensitive information from the yaml-cpp library via flaws in the scanner component.","url":"https://insights.sbomify.com/CVE-2026-75432/"}