How severe is CVE-2022-3064?

CVE-2022-3064 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-3064?

CVE-2022-3064 affects the following packages: gopkg.in/yaml.v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-3064?

Update gopkg.in/yaml.v2 to 2.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3064 is resolved across your whole dependency graph.

How do I detect CVE-2022-3064 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gopkg.in/yaml.v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-3064 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-3064 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-3064 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-3064?

CVE-2022-3064 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-3064?

CVE-2022-3064 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-3064 published, and has it been updated?

CVE-2022-3064 was published on December 27, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-3064 — gopkg.in/yaml.v2

HIGHFix: go-yaml/yaml@f221b84

CVE-2022-3064 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in gopkg.in/yaml.v2. A fix is available for gopkg.in/yaml.v2 — see the affected versions and patch details below.

Excessive resource consumption in gopkg.in/yaml.v2

Also known asGHSA-6q6q-88xp-6f2rGO-2022-0956

Published

Dec 27, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-3064.

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹gopkg.in/yaml.v2

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

Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gopkg.in/yaml.v2`	all versions	2.2.4`go get gopkg.in/yaml.v2@v2.2.4`

Affected Products

1 product · 1 configurations

Application

yamlyaml_project

< 2.2.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gopkg.in/yaml.v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gopkg.in/yaml.v2 to 2.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3064 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

RHC package for Red Hat Enterprise Linux 9 mark as Low severity as we do ship the affected code but it's not easily exposed because YAML files are not parsed by RHC.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`container-tools:4.0-8090020230828093056.e7857ab1`	RHSA-2023:6938
Red Hat Enterprise Linux 8	`container-tools:rhel8-8090020230825121312.e7857ab1`	RHSA-2023:6939
Red Hat Enterprise Linux 8	`rhc-1:0.2.5-1.el8_10`	RHSA-2024:10784
Red Hat Enterprise Linux 9	`toolbox-0:0.0.99.4-6.el9_3`	RHSA-2023:6346
Red Hat Enterprise Linux 9	`rhc-1:0.2.5-1.el9_5`	RHSA-2024:10759
Red Hat Enterprise Linux 9.2 Extended Update Support	`toolbox-0:0.0.99.4-1.el9_2`	RHSA-2024:4443
Red Hat OpenShift Container Platform 4.10	`openshift4/ose-configmap-reloader:v4.10.0-202302072301.p0.g1e5a18e.assembly.stream`	RHSA-2023:0698
Red Hat OpenShift Container Platform 4.10	`openshift4/ose-telemeter:v4.10.0-202302201054.p0.g3b5eb87.assembly.stream`	RHSA-2023:0899

Frequently Asked Questions