CVE-2022-3064
Excessive resource consumption in gopkg.in/yaml.v2
HIGH
7.5
CVSS Score
Published: December 27, 2022 at 09:17 PM UTC
Updated: June 17, 2026 at 04:58 AM UTC
2 products affected across 2 vendorsYamlProject Yaml
Using gopkg.in/yaml.v2 by gopkg.in/yaml.v2?
Get instant alerts when new vulnerabilities affect gopkg.in/yaml.v2 - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
No known exploit
Description
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
95%
v < 2.2.4
Affected range stops below 2.2.4, so it looks safe — our inference, not a vendor statement
v < 2.2.4
Affected range stops below 2.2.4, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (10)
PatchThird Party Advisory
Source: [email protected]
https://github.com/go-yaml/yaml/commit/f221b8435cfb71e54062f6c6e99e9ade30b124d5Release NotesThird Party Advisory
Source: [email protected]
https://github.com/go-yaml/yaml/releases/tag/v2.2.4SSVC — Action Prioritization
SSVCNo known exploitNot automatablePartial impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
7.5HIGHCISA-ADP
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- NONE
- Integrity
- NONE
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-400
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card