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

CVE-2021-4235

MEDIUM

CVE-2021-4235 is a medium-severity (CVSS 5.5) vulnerability in gopkg.in/yaml.v2. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2021-4235 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

YAML Go package vulnerable to denial of service

Also known asGHSA-r88r-gmrh-7j83GO-2021-0061
Published
Dec 27, 2022
Updated
Jul 9, 2026
Affected
2 pkgs
Patched
1 / 2
Exploits
1 known

Blast Radius

2 pkgs affected
🐹gopkg.in/yaml.v2🐹github.com/go-yaml/yaml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Due to unbounded alias chasing, a maliciously crafted YAML file can cause the system to consume significant system resources. If parsing user input, this may be used as a denial of service vector.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogopkg.in/yaml.v2all versions2.2.3
🐹Gogithub.com/go-yaml/yamlall versionsNo fix
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 gopkg.in/yaml.v2. 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 gopkg.in/yaml.v2 to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4235 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-2021-4235 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-2021-4235. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Due to unbounded alias chasing, a maliciously crafted YAML file can cause the system to consume significant system resources. If parsing user input, this may be used as a denial of service vector.
O3 Security · Impact-Aware SCA

Is CVE-2021-4235 in your dependencies?

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