Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Server-Side Request Forgery in Apache Traffic ControlGHSA-wp47-9r3h-xfgq

HIGH

GHSA-wp47-9r3h-xfgq 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.

Also known asCVE-2022-23206GO-2022-0585
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 10, 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
0.34%1.05%1.77%2.48%0.8%2.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-wp47-9r3h-xfgq 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
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/apache/trafficcontrol≥ 6.0.0&&< 6.1.06.1.0go get github.com/apache/trafficcontrol@v6.1.0
🐹Gogithub.com/apache/trafficcontrolall versions5.1.6go 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

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

  2. 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 GHSA-wp47-9r3h-xfgq is resolved across your whole dependency graph.

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

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.
O3 Security · Impact-Aware SCA

Is GHSA-wp47-9r3h-xfgq in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Server-Side Request Forgery in Apache Traffic Control