How severe is CVE-2022-1996?

CVE-2022-1996 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-1996?

CVE-2022-1996 affects the following packages: github.com/emicklei/go-restful/v3 (Go), github.com/emicklei/go-restful (Go), github.com/emicklei/go-restful/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-1996?

Update github.com/emicklei/go-restful/v3 to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1996 is resolved across your whole dependency graph.

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

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

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

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.

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

Yes. There are 1 known exploit references for CVE-2022-1996, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2022-1996 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th 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-1996?

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

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

CVE-2022-1996 was published on June 6, 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

CRITICAL severity

CVE-2022-1996 — go-restful

CRITICALFix: emicklei/go-restful@fd3c327

CVE-2022-1996 is a critical-severity (CVSS 9.3) CWE-639 vulnerability in github.com/emicklei/go-restful/v3. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/emicklei/go-restful/v3 — see the affected versions and patch details below.

Authorization Bypass Through User-Controlled Key in emicklei/go-restful

Also known asGHSA-r48q-9g5r-8q2hGO-2022-0619

Published

Jun 6, 2022

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% 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

3 pkgs affected

🐹github.com/emicklei/go-restful/v3🐹github.com/emicklei/go-restful🐹github.com/emicklei/go-restful/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

Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/emicklei/go-restful/v3`	≥ 3.0.0&&< 3.8.0	3.8.0`go get github.com/emicklei/go-restful/v3@v3.8.0`
🐹Go	`github.com/emicklei/go-restful`	all versions	2.16.0`go get github.com/emicklei/go-restful@v2.16.0`
🐹Go	`github.com/emicklei/go-restful/v2`	all versions	No fix

Affected Products

2 products · 4 configurations

fedorafedoraproject

2 versions

3536

Application

go-restfulgo-restful_project

≥ 3.0.0 && < 3.8.0

range

Exploits & PoCs

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

Authorization Bypass Through User-Controlled Key in GitHub repository em…

huntr.devNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/emicklei/go-restful/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/emicklei/go-restful/v3 to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1996 is resolved across your whole dependency graph.
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.

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

The go-restful package is a transitive dependency which is being pulled with k8s.io/api and not directly being used anywhere in OpenShift Container Platform (OCP), OpenShift Container Storage, OpenShift Data Foundation, OpenShift Do and OpenShift Pipelines, hence these components are marked as 'Will not fix' or even…

Product	Fixed in	Advisory
Cryostat 2 on RHEL 8	`cryostat-tech-preview/cryostat-grafana-dashboard-rhel8:2.2.0-14`	RHSA-2023:0814
Openshift Serveless 1.24	`openshift-serverless-1/client-kn-rhel8:1.3.1-4`	RHSA-2022:6040
Openshift Serverless 1 on RHEL 8	`openshift-serverless-clients-0:1.3.1-4.el8`	RHSA-2022:6042
Red Hat OpenShift GitOps 1.8	`openshift-gitops-kam-0:1.8.3-6.el8`	RHSA-2023:3229
Red Hat OpenShift GitOps 1.9	`openshift-gitops-kam-0:1.9.0-102.el8`	RHSA-2023:3557
RHEL-8-CNV-4.9	`container-native-virtualization/cluster-network-addons-operator:v4.9.7-4`	RHSA-2022:8609

Frequently Asked Questions

Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.

O3 Security · Impact-Aware SCA

Is CVE-2022-1996 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works