How severe is CVE-2022-23206?

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

Which packages are affected by CVE-2022-23206?

CVE-2022-23206 affects the following packages: github.com/apache/trafficcontrol (Go), github.com/apache/trafficcontrol (Go). Ecosystems affected: Go.

How do I fix CVE-2022-23206?

Update github.com/apache/trafficcontrol to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23206 is resolved across your whole dependency graph.

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

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

No public exploit code has been indexed for CVE-2022-23206 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-23206?

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

CVE-2022-23206 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2022-23206 was published on February 6, 2022 and was last updated on October 8, 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-23206 — trafficcontrol

HIGH

CVE-2022-23206 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in github.com/apache/trafficcontrol. A fix is available for github.com/apache/trafficcontrol — see the affected versions and patch details below.

Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth

Also known asGHSA-wp47-9r3h-xfgqGO-2022-0585

Published

Feb 6, 2022

Updated

Oct 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-23206 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrol

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

In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged user who can reach Traffic Ops over HTTPS can send a specially-crafted POST request to /user/login/oauth to scan a port of a server that Traffic Ops can reach.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/apache/trafficcontrol`	≥ 6.0.0&&< 6.1.0	6.1.0`go get github.com/apache/trafficcontrol@v6.1.0`
🐹Go	`github.com/apache/trafficcontrol`	all versions	5.1.6`go get github.com/apache/trafficcontrol@v5.1.6`

Affected Products

1 product · 2 configurations

Application

traffic controlapache

≥ 6.0.0 && < 6.1.0

range

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/apache/trafficcontrol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/apache/trafficcontrol to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23206 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-23206 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 6, 2022

Last updated

Oct 8, 2026

Identifiers

CVE-2022-23206

GHSA-wp47-9r3h-xfgq

GO-2022-0585

References

Advisorygithub.com Advisorynvd.nist.gov Weblists.apache.org

Related vulnerabilities

Also affects trafficcontrol

This CVE is high severity; 3 of 5 other CVEs affecting trafficcontrol are rated as high or higher (top: critical).

CVE-2021-43350CVE-2017-7670CVE-2021-42009CVE-2020-17522CVE-2019-12405

Same weakness: CWE-918

This CVE is high severity; 2 of 3 other CVEs with CWE-918 are rated as high or higher (top: high).

GHSA-39wr-7q6h-cf68GHSA-jgh3-fggc-mcpmCVE-2026-85732Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 8, 2026

CVE-2022-23206 — trafficcontrol

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-23206 in your dependencies?