Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2023-2251

HIGH

CVE-2023-2251 is a high-severity (CVSS 7.5) CWE-248 vulnerability in yaml. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-2251 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Uncaught Exception in eemeli/yaml

Also known asGHSA-f9xv-q969-pqx4
Published
Apr 24, 2023
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

yamlnpm
183.2Mdownloads / week

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmyaml2.0.0-5&&< 2.2.22.2.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yaml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update yaml to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2251 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-2251 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-2251. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Uncaught Exception in GitHub repository eemeli/yaml prior to 2.0.0-5.
O3 Security · Impact-Aware SCA

Is CVE-2023-2251 in your dependencies?

O3 detects CVE-2023-2251 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.