VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

yaml-cpp: vulnerability history, versions and safety

yaml-cpp is a package in the Debian ecosystem. Vulert records 12 vulnerabilities for it across 1 affected range, from Apr 2017 to Jan 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded U12
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all yaml-cpp vulnerabilities

Vulert verdict on yaml-cpp i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 15 Jan 2019. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 12 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 12 over 1 year · 0 in the last year i
  • Latest disclosure 15 Jan 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 0.6.3-1 (exclusive) 12

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 4
  • 2018 4
  • 2019 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 12 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for yaml-cpp

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in yaml-cpp 7.5 high 0.6.3-1 30 Jul 2017
Stack Exhaustion in yaml-cpp (CVE-2019-6292) 6.5 medium 0.6.3-1 15 Jan 2019
Denial of Service Vulnerability in yaml-cpp 6.5 medium 0.6.3-1 14 Jan 2019
Denial of Service Vulnerability in yaml-cpp 6.5 medium 0.6.3-1 28 Dec 2018
Denial of Service Vulnerability in yaml-cpp 6.5 medium 0.6.3-1 28 Dec 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About yaml-cpp

Is yaml-cpp safe to use?

Vulert records 12 vulnerabilities for yaml-cpp in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 12 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does yaml-cpp have?

12 vulnerabilities are recorded for yaml-cpp in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 12 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new yaml-cpp vulnerabilities disclosed?

0 vulnerabilities were recorded for yaml-cpp in the last 12 months, and the oldest entry in this database dates to 03 Apr 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of yaml-cpp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor yaml-cpp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the yaml-cpp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.