CVE-2019-6292: An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2

This month

MEDIUM 6.5DOWNGRADE

CVE-2019-6292 is a medium-severity flaw (CVSS 6.5) affecting yaml-cpp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2. Stack Exhaustion occurs in YAML::SingleDocParser, and there is a stack consumption problem caused by recursive stack frames: HandleCompactMap, HandleMap, HandleFlowSequence, HandleSequence, HandleNode. Remote attackers could leverage this vulnerability to cause a denial-of-service via a cpp file.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.9% (top 21%)
CISA exploited list	No
Weakness	CWE-674
Published	2019-01-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: yaml-cpp project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-01-15 00:29 UTCPublished CVE record published
2026-06-17 02:38 UTCUpdated Record last modified

yaml-cpp project yaml-cpp DOWNGRADE

Affected: 0.6.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.6.2

1. Check installed version

apt-cache policy yaml-cpp || rpm -q yaml-cpp || yaml-cpp --version

2. No fixed release: DOWNGRADE to a release before 0.6.2 (Debian / Ubuntu)

apt-cache madison yaml-cpp sudo apt install yaml-cpp=<VERSION_BEFORE_0.6.2> sudo apt-mark hold yaml-cpp

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yaml-cpp sudo dnf downgrade yaml-cpp-<VERSION_BEFORE_0.6.2> sudo dnf versionlock add yaml-cpp

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-6292?

yaml-cpp: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-6292 being exploited?

CVE-2019-6292 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-6292 affect?

CVE-2019-6292 affects yaml-cpp. Severity is medium (CVSS 6.5). An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2. Stack Exhaustion occurs in YAML::SingleDocParser, and there is a stack consumption problem caused by recursive stack frames: HandleCompactMap, HandleMap, Ha

How urgent is CVE-2019-6292?

Priority 48/100. Public exploit reference

Related CVEs

CVE-2019-6285 MEDIUM 6.5 DOWNGRADE The SingleDocParser::HandleFlowSequence function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers t
CVE-2018-20574 MEDIUM 6.5 DOWNGRADE The SingleDocParser::HandleFlowMap function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cau
CVE-2018-20573 MEDIUM 6.5 DOWNGRADE The Scanner::EnsureTokensInQueue function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cause
CVE-2017-5950 MEDIUM 5.5 DOWNGRADE The SingleDocParser::HandleNode function in yaml-cpp (aka LibYaml-C++) 0.5.3 allows remote attackers to cause
CVE-2017-11692 HIGH 7.5 UPGRADE The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to ca

References

← Back to latest CVEs