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

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

GHSA-9r7g-3hh2-8x65 ↗

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.28; >= 0.5.0-rc1, < 0.5.0-rc49; >= 0.6.0-rc1, < 0.6.0-rc73
fixed in 0.4.28, 0.5.0-rc49, 0.6.0-rc73
ETK-2026-2394Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/auth-framework
cvss7.0ethiack provisional
47msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+4.7d
0
+1d
+2d
+3d
+4d
+5d

description

auth-framework is affected when a deployment uses its default configuration or does not explicitly set a JWT signing secret. An attacker can forge tokens accepted by such a deployment because the default signing key was publicly known.

mitigation

Upgrade to the fixed releases 0.4.28, 0.5.0-rc49, or 0.6.0-rc73; because those releases were yanked, use 0.4.29, 0.5.0-rc51, or 0.6.0-rc85 or later instead. Configure a unique JWT secret, rotate the old secret, and invalidate existing tokens.

fixed in 0.4.28, 0.5.0-rc49, 0.6.0-rc73

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
12m
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-17 12:27Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2394",
  "cve_id": null,
  "display_id": "ETK-2026-2394",
  "ghsa_id": "GHSA-9r7g-3hh2-8x65",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Default JWT signing key in auth-framework",
  "summary": "auth-framework is affected when a deployment uses its default configuration or does not explicitly set a JWT signing secret. An attacker can forge tokens accepted by such a deployment because the default signing key was publicly known.",
  "mitigation": "Upgrade to the fixed releases 0.4.28, 0.5.0-rc49, or 0.6.0-rc73; because those releases were yanked, use 0.4.29, 0.5.0-rc51, or 0.6.0-rc85 or later instead. Configure a unique JWT secret, rotate the old secret, and invalidate existing tokens.",
  "vendor": "rust",
  "product": "rust:auth-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, < 0.4.28"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.4.28"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.5.0-rc1, < 0.5.0-rc49"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.5.0-rc49"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.6.0-rc1, < 0.6.0-rc73"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.6.0-rc73"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    }
  ],
  "cwes": null,
  "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": 12.170476833333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-17T12:27:42+00:00",
      "days": -4.757534205497685,
      "is_lower_bound": true,
      "measured_at": "2026-10-22T06:38:32.994096+00:00",
      "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-9r7g-3hh2-8x65"
    }
  }
}

published 2026-10-22 05:56Z
last change 2026-10-22 06:36Z

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.