ETK-2026-356Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-wr5q-7wxw-x568 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
OAuth2 Proxy >= 6.1.0, <= 7.15.3
fixed in > v7.15.4
CWE-290 Authentication Bypass by Spoofing
ETK-2026-356, no cve assigned
18d 12h 42msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −20dwaiting for further signals−19d
−15d
−10d
−5d
0

description

OAuth2 Proxy before v7.15.5 can incorrectly use spoofed client-IP headers when trusted-IP exemptions and reverse-proxy mode are enabled. An unauthenticated remote attacker may gain the access granted to an exempt IP address if they can supply or preserve a client-IP header.

mitigation

Upgrade unnamed to > v7.15.4 or later.

fixed in > v7.15.4

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-01 09:23Z

this entry in the feed

GET /api/v1/feed/ETK-2026-356

{
  "etk_id": "ETK-2026-356",
  "cve_id": null,
  "display_id": "ETK-2026-356",
  "ghsa_id": "GHSA-wr5q-7wxw-x568",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Trusted-IP authentication bypass in OAuth2 Proxy",
  "summary": "OAuth2 Proxy before v7.15.5 can incorrectly use spoofed client-IP headers when trusted-IP exemptions and reverse-proxy mode are enabled. An unauthenticated remote attacker may gain the access granted to an exempt IP address if they can supply or preserve a client-IP header.",
  "mitigation": "Upgrade unnamed to > v7.15.4 or later.",
  "vendor": null,
  "product": "OAuth2 Proxy",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.1.0, <= 7.15.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "> v7.15.4"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    290
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.6550065,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T09:23:44+00:00",
      "days": -19.810414471435184,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:50:43.834061+00:00",
      "url": "https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-wr5q-7wxw-x568"
    }
  }
}

published 2026-10-02 16:55Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.