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

CVE-2017-1000069 — oauth2_proxy

HIGHFix: bitly/oauth2_proxy#360

CVE-2017-1000069 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in github.com/bitly/oauth2_proxy. A fix is available for github.com/bitly/oauth2_proxy — see the affected versions and patch details below.

Cross-site Request Forgery (CSRF)

Also known asGHSA-rrm8-32g4-w8m3
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.41%0.83%1.24%0.1%0.7%Apr 26Jul 26Oct 26

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

How urgent is this, really

CVE-2017-1000069 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

1 pkg affected
🐹github.com/bitly/oauth2_proxy

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

CSRF in Bitly oauth2_proxy 2.1 during authentication flow

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/bitly/oauth2_proxyall versions2.2.0go get github.com/bitly/oauth2_proxy@v2.2.0

Affected Products

1 product · 1 configurations
Application
oauth2 proxyoauth2_proxy_project
1 version
2.1

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/bitly/oauth2_proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/bitly/oauth2_proxy to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000069 is resolved across your whole dependency graph.

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

Frequently Asked Questions

CSRF in Bitly oauth2_proxy 2.1 during authentication flow
O3 Security · Impact-Aware SCA

Is CVE-2017-1000069 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-1000069: oauth2_proxy CSRF — Fixed in 2.2.0