CVE-2026-75432: yaml-cpp · CVE-2026-75432 is a medium severity
Affects yaml-cppSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjbeder/yaml-cpppkg:github/jbeder/yaml-cppOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor vendor communications for updates and consider restricting local access to affected systems as a precaution.
Description
CVE-2026-75432 is a medium severity vulnerability in yaml-cpp version 0.9.0. It involves components in the src/scanner.cpp file, specifically the Scanner::PopIndent() and Scanner::PushIndentTo() functions, which allow a remote attacker to obtain sensitive information. The vulnerability has a CVSS score of 5.1, indicating limited impact on confidentiality and availability, with no impact on integrity. No patch or remediation information is currently available.