CVE-2021-21411: Incorrect authorization in OAuth2-Proxy
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.3% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/oauth2-proxy/oauth2-proxy/v7 (Go) 7.1.0; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1.
Low priority for now. Upgrade to github.com/oauth2-proxy/oauth2-proxy/v7 (Go) 7.1.0; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. The `--gitlab-group` flag for group-based authorization in the GitLab provider stopped working in the v7.0.0 release. Regardless of the flag settings, authorization wasn't restricted. Additionally, any authenticated users had whichever groups were set in `--gitlab-group` added to the new `X-Forwarded-Groups` header to the upstream application. While adding GitLab project based authorization support in #630, a bug was introduced where the user session's groups field was populated with the `--gitlab-group` config entries instead of pulling the individual user's group membership from the GitLab Userinfo endpoint. When the session groups where compared against the allowed groups for authorization, they matched improperly (since both lists were populated with the same data) so authorization was allowed. This impacts GitLab Provider users who relies on group membership for authorization restrictions. Any authenticated users in your GitLab environment can access your applications regardless of `--gitlab-group` membership restrictions. This is patched in v7.1.0. There is no workaround for the Group membership bug. But `--gitlab-project` can be set to use Project membership as the authorization checks instead of groups; it is not broken.
- Published
- Mar 26, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-863
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CNA vs NVD score
- NVD
- 5.5
- CNA · GitHub_M
- 5.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| oauth2 proxy project | oauth2 proxy | cpe:2.3:a:oauth2_proxy_project:oauth2_proxy |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
oauth2-proxy oauth2-proxy
- >= 7.0.0, < 7.1.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oauth2 proxy project oauth2 proxy7.0.0 and later · before 7.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/oauth2-proxy/oauth2-proxy | from 0 | — |
| Go | github.com/oauth2-proxy/oauth2-proxy/v7 | before 7.1.0 | 7.1.0 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250811T192933-1.1 | 0.0.20250811T192933-1.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
Same product
oauth2 proxy project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-40575OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing36Monitor
- CVE-2026-34457OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode36Monitor
- CVE-2025-54576OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-4037Jun 29, 2020 · Open Redirect in OAuth2 Proxy21Monitor
- ← EarlierCVE-2021-21291Feb 2, 2021 · Subdomain checking of whitelisted domains could allow unintended redirects24Monitor
- Later →CVE-2026-34454Apr 14, 2026 · OAuth2 Proxy: Session cookie not cleared when rendering sign-in page14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/oauth2-proxy/oauth2-proxy/v7 | 7.1.0 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.