VulertSecurity VulertSecurity

Vulnerability Database · Go · github.com/oauth2-proxy/oauth2-proxy · Version

github.com/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc

v0.0.0-20200831161845-e4e5580852dc is affected by 11 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v3.2.1-0.20190719101153-f29e353586c1+incompatible.

Critical 0 High 1 Medium 1 Low 0 Unrated 9

All github.com/oauth2-proxy/oauth2-proxy versions & vulnerabilities → Source repository Search the database for this package →
Released 31 Aug 2020 Licence MIT Also known from other sources 13 Newer releases 300 Database updated 23/Oct/2026

Release and licence data published by the Go module proxy. 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 Vulnerabilities affecting this version

github.com/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc vulnerabilities

11 vulnerabilities cover github.com/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2020-11053: Open Redirect in OAuth2 Proxy 7.1 high 5.1.1 20 Dec 2021
CVE-2020-5233: Open Redirect Vulnerability in oauth2-proxy 5.9 medium 5.0.0 20 Dec 2021
CVE-2026-41059: OAuth2 Proxy Authentication Bypass via Fragment Confusion N/A unrated No fix published 25 Jun 2026
CVE-2026-40574: Authorization Bypass in OAuth2 Proxy via Malformed Multi-@ Email Claims N/A unrated No fix published 25 Jun 2026
CVE-2026-34454: OAuth2 Proxy Session Cookie Vulnerability N/A unrated No fix published 25 Jun 2026
CVE-2026-40575: OAuth2 Proxy Authentication Bypass via X-Forwarded-Uri Header Spoofing N/A unrated No fix published 25 Jun 2026
CVE-2026-34457: OAuth2 Proxy Health Check User-Agent Matching Bypasses Authentication N/A unrated No fix published 25 Jun 2026
CVE-2025-64484: OAuth2-Proxy Header Smuggling Vulnerability Leading to Privilege Escalation N/A unrated No fix published 17 Nov 2025
CVE-2021-21411: GitLab Group Authorization Flag Malfunction in OAuth2-Proxy N/A unrated No fix published 11 Aug 2025
CVE-2025-54576: OAuth2-Proxy Authentication Bypass Due to Query Parameter Inclusion N/A unrated No fix published 11 Aug 2025
CVE-2021-21291: oauth2-proxy Subdomain Redirect Vulnerability N/A unrated No fix published 21 Aug 2024

Looking for another version, or everything Vulert holds for github.com/oauth2-proxy/oauth2-proxy?

All versions → Full vulnerability list →

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/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc

Is github.com/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc vulnerable?

Yes. 11 vulnerabilities in the Vulert database cover github.com/oauth2-proxy/oauth2-proxy v0.0.0-20200831161845-e4e5580852dc: 0 critical, 1 high, 1 medium and 0 low, plus 9 not yet rated. The upgrade Vulert recommends is v3.2.1-0.20190719101153-f29e353586c1+incompatible, and each entry above names the fixed version to move to.

Which version of github.com/oauth2-proxy/oauth2-proxy should I use instead of v0.0.0-20200831161845-e4e5580852dc?

v3.2.1-0.20190719101153-f29e353586c1+incompatible is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is v0.0.0-20200831161845-e4e5580852dc the latest release of github.com/oauth2-proxy/oauth2-proxy?

No. v0.0.0-20200831161845-e4e5580852dc was published 31 Aug 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor github.com/oauth2-proxy/oauth2-proxy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/oauth2-proxy/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.