CVE-2023-2251: Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5.

Q: How do I fix CVE-2023-2251?

yaml: upgrade to 2.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2023-2251 being exploited?

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

Q: What does CVE-2023-2251 affect?

CVE-2023-2251 affects yaml. Severity is high (CVSS 7.5). Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5.

Q: How urgent is CVE-2023-2251?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2023-2251 is a high-severity flaw (CVSS 7.5) affecting yaml. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-248
Published	2023-04-24
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: yaml project

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

Am I affected?

Timeline

2023-04-24 15:15 UTCPublished CVE record published
2026-06-17 05:52 UTCUpdated Record last modified

yaml project yaml UPGRADE

Affected: >= 2.0.0-5 and < 2.2.2

Fixed in: 2.2.2

Safe to downgrade to: a release before 2.0.0-5

1. Check installed version

npm ls yaml

2. UPGRADE to 2.2.2

npm install yaml@">=2.2.2"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0-5

npm view yaml versions npm install yaml@"<2.0.0-5"

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-2023-2251?

yaml: upgrade to 2.2.2. Exact commands for each OS are on this page.

Is CVE-2023-2251 being exploited?

CVE-2023-2251 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-2023-2251 affect?

CVE-2023-2251 affects yaml. Severity is high (CVSS 7.5). Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5.

How urgent is CVE-2023-2251?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2026-33532 MEDIUM 4.3 UPGRADE `yaml` is a YAML parser and serialiser for JavaScript
CVE-2022-3064 HIGH 7.5 UPGRADE Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
CVE-2022-28948 HIGH 7.5 DOWNGRADE MITIGATE An issue in the Unmarshal function in Go-Yaml v3 causes the program to crash when attempting to deserialize in
CVE-2021-4235 MEDIUM 5.5 UPGRADE Due to unbounded alias chasing, a maliciously crafted YAML file can cause the system to consume significant sy

References

← Back to latest CVEs