NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-28948 — gopkg.in/yaml.v3

HIGHFix: go-yaml/yaml@8f96da9

CVE-2022-28948 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in gopkg.in/yaml.v3. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for gopkg.in/yaml.v3 — see the affected versions and patch details below.

gopkg.in/yaml.v3 Denial of Service

Also known asGHSA-hp87-p4gw-j4gqGO-2022-0603
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
0.79%2.09%3.40%4.70%1.5%4.0%May 26Sep 26Nov 26

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.v3

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

An issue in the Unmarshal function in Go-Yaml v3 can cause a program to panic when attempting to deserialize invalid input.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogopkg.in/yaml.v3all versions3.0.1go get gopkg.in/yaml.v3@v3.0.1

Affected Products

2 products · 2 configurations
Application
astra tridentnetapp
all
Application
yamlyaml_project
1 version
3.0.0
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.v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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 HatModerate

Red Hat has designated the CVE rating as 'moderate' as exploitation of Red Hat products is contingent upon the attacker being authenticated when sending the malicious XML payload.

ProductFixed inAdvisory
Cryostat 2 on RHEL 8cryostat-tech-preview/cryostat-operator-bundle:2.1.1-2RHSA-2022:4985
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/devspaces-rhel8-operator:3.15-10RHSA-2024:4631

Frequently Asked Questions

An issue in the Unmarshal function in Go-Yaml v3 can cause a program to panic when attempting to deserialize invalid input.
O3 Security · Impact-Aware SCA

Is CVE-2022-28948 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-28948: gopkg.in/yaml.v3 — Fixed in 3.0.1