← back to feed
ETK-2026-2441Zero's internal tracking ID, independent of the CVE number.

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

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

GHSA-r75x-xf92-4hxg ↗

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.
rust:auth-framework >= 0.4.1, < 0.4.30; = 0.5.0-rc1
fixed in 0.4.30, 0.5.0-rc18
CWE-287 Improper Authentication
ETK-2026-2441Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/auth-framework
cvss7.0ethiack provisional
1h 34msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −4.5dwaiting for further signals−0.1d
−4d
−3d
−2d
−1d

description

auth-framework OAuth2 placeholder handlers in affected releases can accept unvalidated OAuth requests, allowing an attacker to obtain apparent token or authorization success and use arbitrary redirect targets. In 0.4.x, exposure requires an application to explicitly mount the internal OAuth handlers; 0.5.0-rc1 mounted affected handlers on its default router.

mitigation

Upgrade 0.4.x deployments to 0.4.30 or later, and replace 0.5.0-rc1 with 0.5.0-rc18 or later. Until upgraded, do not mount auth_framework::api::oauth handlers or expose routes backed by them.

fixed in 0.4.30, 0.5.0-rc18

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
25m
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-18 04:02Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2441",
  "cve_id": null,
  "display_id": "ETK-2026-2441",
  "ghsa_id": "GHSA-r75x-xf92-4hxg",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "OAuth2 authentication bypass in auth-framework",
  "summary": "auth-framework OAuth2 placeholder handlers in affected releases can accept unvalidated OAuth requests, allowing an attacker to obtain apparent token or authorization success and use arbitrary redirect targets. In 0.4.x, exposure requires an application to explicitly mount the internal OAuth handlers; 0.5.0-rc1 mounted affected handlers on its default router.",
  "mitigation": "Upgrade 0.4.x deployments to 0.4.30 or later, and replace 0.5.0-rc1 with 0.5.0-rc18 or later. Until upgraded, do not mount auth_framework::api::oauth handlers or expose routes backed by them.",
  "vendor": "rust",
  "product": "rust:auth-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.1, < 0.4.30"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.4.30"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "= 0.5.0-rc1"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.5.0-rc18"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.07227638333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T04:02:13+00:00",
      "days": -4.465343733368056,
      "is_lower_bound": true,
      "measured_at": "2026-10-22T15:12:18.723684+00:00",
      "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-r75x-xf92-4hxg"
    }
  }
}

published 2026-10-22 13:13Z
last change 2026-10-22 15:11Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.