VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/bitly/oauth2_proxy: vulnerability history, versions and safety

github.com/bitly/oauth2_proxy is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Dec 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/bitly/oauth2_proxy vulnerabilities

Vulert verdict on github.com/bitly/oauth2_proxy v2.0.1+incompatible i

Updated on 23 Oct 2026

Action needed: v2.0.1+incompatible has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 67/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v2.0.1+incompatible — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 Dec 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 5,083 i
  • OpenSSF scorecard 2/10 i
  • Last release 135 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/bitly/oauth2_proxy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.1.2-0.20190123224120-fa2771998a98 23 Jan 2019 H1 M1 MIT Yes Details →
v2.0.2-0.20190123224120-fa2771998a98+incompatible 23 Jan 2019 H1 M1 MIT Yes Details →
v2.0.2-0.20190123202907-9cf5da7b595a+incompatible 23 Jan 2019 H1 M1 MIT Yes Details →
v2.0.2-0.20190123194844-75c5ec1007a4+incompatible 23 Jan 2019 H1 M1 MIT Yes Details →
v2.0.2-0.20190111114259-7c57a72d8849+incompatible 11 Jan 2019 H1 M1 MIT Yes Details →
v0.0.0-20180325034845-a94b0a8b25e5 25 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180325034845-a94b0a8b25e5+incompatible 25 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180325034515-1c1db881c321+incompatible 25 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180325034416-ae78840614ee+incompatible 25 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180309004411-542ef540939c+incompatible 09 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180301171002-2db0443e0484+incompatible 01 Mar 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180216081441-008ffae3bb5f+incompatible 16 Feb 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180123150809-ae49c7d23c8b+incompatible 23 Jan 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180123150441-a6e247825c1d+incompatible 23 Jan 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180116155753-1209c63b5850+incompatible 16 Jan 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20180116154741-1a8218037674+incompatible 16 Jan 2018 H1 M1 MIT Yes Details →
v2.0.2-0.20171219021651-74d0fbc86852+incompatible 19 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171219015537-20e87edde8b2+incompatible 19 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204221225-d75f626cdd66+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204205148-882fcf0a0108+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204175654-faff555c5533+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204175247-1cefc96311f6+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204175247-69550cbb23b4+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204175247-9341dcbf79fe+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204153933-085c6cf79b58+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171204145431-842a45b1dbe5+incompatible 04 Dec 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171121200030-dc65ff800f37+incompatible 21 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171120194814-b0c1c851770e+incompatible 20 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171120190227-731fa9f8e00b+incompatible 20 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171120180048-6ddbb2c57284+incompatible 20 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171120163753-e955d2be0e14+incompatible 20 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171120155056-a7c5d9c478e1+incompatible 20 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171117205515-781bd0851e81+incompatible 17 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171117015811-c4905f234744+incompatible 17 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171107144606-363a0dda16a6+incompatible 07 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171107125524-e241fe86d33f+incompatible 07 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171106181545-28e217dc8fd8+incompatible 06 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171106170558-f2a995b8d980+incompatible 06 Nov 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171023181445-bfda078caa55+incompatible 23 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171023175635-bc1b839f7fb9+incompatible 23 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171023162417-8a77cfcac357+incompatible 23 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171023155221-fd3925d2044a+incompatible 23 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171013131044-b7f9438b8a5e+incompatible 13 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171008170515-f6828631cfe7+incompatible 08 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171008050115-d118cb7bbb0a+incompatible 08 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20171008044036-34d96f8d8458+incompatible 08 Oct 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170913142736-7b26256df62d+incompatible 13 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170912214349-a32ff08d6865+incompatible 12 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170912214207-982439a8d8a7+incompatible 12 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170910004459-e87c3eee131d+incompatible 10 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170908163251-cb48577ede89+incompatible 08 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170905205853-94574df27483+incompatible 05 Sep 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829005709-b1e29c329bc0+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829005007-678290035cef+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829004843-01ef8162a863+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829004630-23cef892365a+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829004526-11bdcc96c545+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170829004449-79fff535313b+incompatible 29 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170805165542-3d8b59ef7167+incompatible 05 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170805165515-e9bbecfacecb+incompatible 05 Aug 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170720195431-0b117133b949+incompatible 20 Jul 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170720112841-f4321c4b45fb+incompatible 20 Jul 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170713183348-ba67e5c847c3+incompatible 13 Jul 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170713182958-8d6e16bf224c+incompatible 13 Jul 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170629063631-e6e60c4b60aa+incompatible 29 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170621220536-b640a69d6384+incompatible 21 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170621132424-3c51c914ac75+incompatible 21 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170621100324-7fea71a4ceaa+incompatible 21 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170609162350-cddd2fcd7c91+incompatible 09 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170609161724-c8c6b6646546+incompatible 09 Jun 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170526124207-6d6cb7e1f83f+incompatible 26 May 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170518034534-17b1fa31dd81+incompatible 18 May 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170516005028-f4c356637fb1+incompatible 16 May 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424215921-6d295f8446b0+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424215615-7f5672b433f7+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424203422-ea2540bc898f+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424200436-68e317881299+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424200406-d7e327d71210+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424200340-b6bd878f276f+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424162211-b90a23473f10+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424161616-f457a9042a12+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170424161123-3fa5635d6c5d+incompatible 24 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170420185739-f511cac6a6bc+incompatible 20 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170407132033-120a47a52677+incompatible 07 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170407120147-1e7d2a08a3df+incompatible 07 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170402202327-f983933d88ee+incompatible 02 Apr 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329161424-af7be2d622e2+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329155855-829b442302f7+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329155855-90a22b2f39a3+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329155855-fe44b89f574a+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329150226-93852a24cbeb+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329145707-dcf62d06df18+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329135319-bb9b60744023+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329133638-c5fc7baa8690+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329133623-c1116ea5068f+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329133604-446465527687+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v0.0.0-20170329133110-55085d969796 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329133110-55085d969796+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329014229-6c690b699b7b+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329014011-107b4811b416+incompatible 29 Mar 2017 H1 M1 MIT Yes Details →
v2.0.2-0.20170329013855-cd0d13e3fbee+incompatible 29 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170329013423-86d083266b74+incompatible 29 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170329011233-289a6ccf463a+incompatible 29 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170328140615-652f43ed38d6+incompatible 28 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170328010708-712739f77753+incompatible 28 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170328005615-2ebab604eb0e+incompatible 28 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170328003635-b884b36f2671+incompatible 28 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170328001644-951b5f325b30+incompatible 28 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327234012-9167c8ace8c4+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327231742-a2eeec2b7ad1+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327231305-2024dc34ac3d+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327221639-86c9638572f3+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327184940-7d920c98a625+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170327183528-bc3fe00be4d8+incompatible 27 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170323030847-87847316d48d+incompatible 23 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170321164047-562cc2e46641+incompatible 21 Mar 2017 H1 M1 — Yes Details →
v2.0.2-0.20170223234834-3379e05fec7a+incompatible 23 Feb 2017 H1 M1 — Yes Details →
v2.0.2-0.20170124101158-24f91a0b6039+incompatible 24 Jan 2017 H1 M1 — Yes Details →
v2.0.2-0.20161118180022-89ba1d813ac8+incompatible 18 Nov 2016 H1 M1 — Yes Details →
v2.0.2-0.20161118173122-4203c26d7c6a+incompatible 18 Nov 2016 H1 M1 — Yes Details →

The newest 120 of 366 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/bitly/oauth2_proxy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000069: Cross-site Request Forgery (CSRF) in Bitly oauth2_proxy 8.8 high 2.2.0 20 Dec 2021
CVE-2017-1000070: Open Redirect in oauth2_proxy 6.1 medium 2.2.0 20 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/bitly/oauth2_proxy

Is github.com/bitly/oauth2_proxy safe to use?

Vulert records 2 vulnerabilities for github.com/bitly/oauth2_proxy in Go: 0 critical, 1 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/bitly/oauth2_proxy's Vulert package health score?

Vulert scores github.com/bitly/oauth2_proxy 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/bitly/oauth2_proxy affected?

Yes. v2.0.1+incompatible, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/bitly/oauth2_proxy should I use?

v2.0.1+incompatible is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/bitly/oauth2_proxy have?

2 vulnerabilities are recorded for github.com/bitly/oauth2_proxy in the Go ecosystem: 0 critical, 1 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/bitly/oauth2_proxy vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/bitly/oauth2_proxy in the last 12 months, and the oldest entry in this database dates to 20 Dec 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/bitly/oauth2_proxy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/bitly/oauth2_proxy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bitly/oauth2_proxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.