ETK-2026-3176Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
Affected auth-framework releases may accept an OAuth client access token where an authenticated user session is required. An attacker operating a registered OAuth client could use such a token with user-protected endpoints; exposure requires the ability to obtain a client token. Tokens issued before an upgrade may remain usable until they expire.
mitigation
Upgrade auth-framework to 0.4.46, 0.5.0-rc82, or 0.6.0-rc46, as appropriate for the release line. For routes intended to accept delegated access, use the delegated-token validation provided by the fixed releases and account for previously issued client tokens until expiration.
fixed in 0.4.46, 0.5.0-rc82, 0.6.0-rc46
outcome
Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-31 14:03Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-3176
{ "etk_id": "ETK-2026-3176", "cve_id": null, "display_id": "ETK-2026-3176", "ghsa_id": "GHSA-jghc-wgvq-4r28", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "OAuth client token authentication bypass in auth-framework", "summary": "Affected auth-framework releases may accept an OAuth client access token where an authenticated user session is required. An attacker operating a registered OAuth client could use such a token with user-protected endpoints; exposure requires the ability to obtain a client token. Tokens issued before an upgrade may remain usable until they expire.", "mitigation": "Upgrade auth-framework to 0.4.46, 0.5.0-rc82, or 0.6.0-rc46, as appropriate for the release line. For routes intended to accept delegated access, use the delegated-token validation provided by the fixed releases and account for previously issued client tokens until expiration.", "vendor": "rust", "product": "rust:auth-framework", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0.4.0, < 0.4.46" ], "ecosystem": "rust", "fixed_versions": [ "0.4.46" ], "package_name": "auth-framework", "purl": "pkg:cargo/auth-framework" }, { "affected_notes": [], "affected_ranges": [ ">= 0.5.0-rc1, <= 0.5.0-rc79" ], "ecosystem": "rust", "fixed_versions": [ "0.5.0-rc82" ], "package_name": "auth-framework", "purl": "pkg:cargo/auth-framework" }, { "affected_notes": [], "affected_ranges": [ ">= 0.6.0-rc41, <= 0.6.0-rc45" ], "ecosystem": "rust", "fixed_versions": [ "0.6.0-rc46" ], "package_name": "auth-framework", "purl": "pkg:cargo/auth-framework" } ], "cwes": [ 863 ], "cvss_score": 8.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/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": 18.990151, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-10-31T14:03:38+00:00", "days": -0.17959272708333332, "is_lower_bound": true, "measured_at": "2026-10-31T18:22:14.843968+00:00", "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-jghc-wgvq-4r28" } } }
published 2026-10-31 14:34Z
last change 2026-10-31 18:03Z
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.