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

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

GHSA-jrv7-v6qw-mm98 ↗

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.50; >= 0.5.0-rc1, < 0.5.0-rc86; >= 0.6.0-rc1, < 0.6.0-rc202
fixed in 0.4.50, 0.5.0-rc86, 0.6.0-rc202
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-3331Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/auth-framework
1h 39msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+0h57m
0
+2h

description

auth-framework releases before 0.4.50, 0.5.0-rc86, and 0.6.0-rc202 can inadequately validate JWT access tokens through the legacy DPoP validation method. An attacker may cause an application to accept a token they did not obtain from a trusted issuer if the application relies on that method and accepts the result for authorization.

mitigation

Upgrade to auth-framework 0.4.50, 0.5.0-rc86, or 0.6.0-rc202, as appropriate. Until upgraded, stop using the legacy method and independently verify token signature, lifetime, issuer, audience, and the DPoP key binding before authorizing requests.

fixed in 0.4.50, 0.5.0-rc86, 0.6.0-rc202

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
30m
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-03 01:42Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3331",
  "cve_id": null,
  "display_id": "ETK-2026-3331",
  "ghsa_id": "GHSA-jrv7-v6qw-mm98",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Improper DPoP-bound token validation in auth-framework",
  "summary": "auth-framework releases before 0.4.50, 0.5.0-rc86, and 0.6.0-rc202 can inadequately validate JWT access tokens through the legacy DPoP validation method. An attacker may cause an application to accept a token they did not obtain from a trusted issuer if the application relies on that method and accepts the result for authorization.",
  "mitigation": "Upgrade to auth-framework 0.4.50, 0.5.0-rc86, or 0.6.0-rc202, as appropriate. Until upgraded, stop using the legacy method and independently verify token signature, lifetime, issuer, audience, and the DPoP key binding before authorizing requests.",
  "vendor": "rust",
  "product": "rust:auth-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, < 0.4.50"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.4.50"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.5.0-rc1, < 0.5.0-rc86"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.5.0-rc86"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.6.0-rc1, < 0.6.0-rc202"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.6.0-rc202"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    }
  ],
  "cwes": [
    347
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.730288933333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T01:42:25+00:00",
      "days": -0.10864189591435185,
      "is_lower_bound": true,
      "measured_at": "2026-11-03T04:18:51.759969+00:00",
      "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-jrv7-v6qw-mm98"
    }
  }
}

published 2026-11-03 02:11Z
last change 2026-11-03 03:55Z

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.