HIGH CVSS 8.2
Published: 2026-04-22

CVE-2026-41059

oauth2_proxy_project oauth2_proxy Security Advisory (CVE-2026-41059)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-41059?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-41059 impacting oauth2_proxy_project oauth2_proxy. Evaluated with CVSS Base Score of 8.2 (HIGH).

Original NVD Description

Source: NIST NVD
OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 have a configuration-dependent authentication bypass. Deployments are affected when all of the following are true: Use of `skip_auth_routes` or the legacy `skip_auth_regex`; use of patterns that can be widened by attacker-controlled suffixes, such as `^/foo/.*/bar$` causing potential exposure of `/foo/secret`; and protected upstream applications that interpret `#` as a fragment delimiter or otherwise route the request to the protected base path. In deployments that rely on these settings, an unauthenticated attacker can send a crafted request containing a number sign in the path, including the browser-safe encoded form `%23`, so that OAuth2 Proxy matches a public allowlist rule while the backend serves a protected resource. Deployments that do not use these skip-auth options, or that only allow exact public paths with tightly scoped method and path rules, are not affected. A fix has been implemented in version 7.15.2 to normalize request paths more conservatively before skip-auth matching so fragment content does not influence allowlist decisions. Users who cannot upgrade immediately can reduce exposure by tightening or removing `skip_auth_routes` and `skip_auth_regex` rules, especially patterns that use broad wildcards across path segments. Recommended mitigations include replacing broad rules with exact, anchored public paths and explicit HTTP methods; rejecting requests whose path contains `%23` or `#` at the ingress, load balancer, or WAF level; and/or avoiding placing sensitive application paths behind broad `skip_auth_routes` rules.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
Low (I:L)
Partial data modification possible
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product oauth2_proxy_project / oauth2_proxy
Affected Versions *
Weakness Enumeration CWE-288

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-41059 impacting oauth2_proxy_project oauth2_proxy.

⚡ Nuclei Detection Template (YAML) cve-2026-41059.yaml
id: cve-2026-41059

info:
  name: oauth2_proxy_project oauth2_proxy - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2026-41059 affecting oauth2_proxy_project oauth2_proxy.
    Evaluation: OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 have a configuration-dependent auth...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-41059
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
    cvss-score: 8.2
    cve-id: CVE-2026-41059
    cwe-id: CWE-288
  tags: cve,cve-2026-41059,oauth2_proxy_project,oauth2_proxy,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "oauth2_proxy"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-41059.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-41059
# Target: oauth2_proxy_project oauth2_proxy | CVSS: 8.2 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-41059 (oauth2_proxy_project oauth2_proxy)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against oauth2_proxy_project oauth2_proxy scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-41059.sh
# Recommended Remediation & Patching Commands for CVE-2026-41059
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install oauth2_proxy 2>/dev/null || \
sudo dnf upgrade oauth2_proxy 2>/dev/null || \
sudo yum update oauth2_proxy

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i oauth2_proxy 2>/dev/null || rpm -qa | grep -i oauth2_proxy

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-41059 in oauth2_proxy_project oauth2_proxy?

Review vendor-specific security notices and update oauth2_proxy_project oauth2_proxy packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-41059?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-41059?

CVE-2026-41059 is classified with a CVSS 3.1 Base Score of 8.2 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
8.2
HIGH SEVERITY
CVE ID CVE-2026-41059
Weakness CWE-288
Vendor oauth2_proxy_project
Product oauth2_proxy
Published 2026-04-22
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N