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

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

GHSA-f66c-6mxj-759h ↗

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.0, < 0.4.47; >= 0.5.0-rc18, < 0.5.0-rc84; >= 0.6.0-rc1, < 0.6.0-rc199
fixed in 0.4.47, 0.5.0-rc84, 0.6.0-rc199
CWE-294 Authentication Bypass by Capture-replay
ETK-2026-3326Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/auth-framework
cvss7.0ethiack provisional
3h 11msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+8h45m
0
+3h
+6h
+12h

description

Affected auth-framework FAPI paths may accept DPoP-bound tokens even when the accompanying proof does not satisfy required validation checks. An attacker who has obtained a DPoP-bound token could use it without controlling the token holder's key; this requires use of the affected FAPI/DPoP-bound token flows.

mitigation

Upgrade auth-framework to 0.4.47, 0.5.0-rc84, or 0.6.0-rc199, as appropriate for your release line. Until upgraded, disable or avoid FAPI flows that use DPoP-bound tokens.

fixed in 0.4.47, 0.5.0-rc84, 0.6.0-rc199

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.
–
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
28m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-02 15:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3326",
  "cve_id": null,
  "display_id": "ETK-2026-3326",
  "ghsa_id": "GHSA-f66c-6mxj-759h",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "DPoP sender-constraint bypass in auth-framework",
  "summary": "Affected auth-framework FAPI paths may accept DPoP-bound tokens even when the accompanying proof does not satisfy required validation checks. An attacker who has obtained a DPoP-bound token could use it without controlling the token holder's key; this requires use of the affected FAPI/DPoP-bound token flows.",
  "mitigation": "Upgrade auth-framework to 0.4.47, 0.5.0-rc84, or 0.6.0-rc199, as appropriate for your release line. Until upgraded, disable or avoid FAPI flows that use DPoP-bound tokens.",
  "vendor": "rust",
  "product": "rust:auth-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, < 0.4.47"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.4.47"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.5.0-rc18, < 0.5.0-rc84"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.5.0-rc84"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.6.0-rc1, < 0.6.0-rc199"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.6.0-rc199"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    }
  ],
  "cwes": [
    294
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.609226883333335,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T15:22:15+00:00",
      "days": -0.4975920749652778,
      "is_lower_bound": true,
      "measured_at": "2026-11-03T03:18:47.189301+00:00",
      "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-f66c-6mxj-759h"
    }
  }
}

published 2026-11-02 23:43Z
last change 2026-11-03 03:18Z

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.