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

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

GHSA-jr9j-g3xj-q9x8 ↗

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.29; >= 0.5.0-rc1, < 0.5.0-rc51; >= 0.6.0-rc41, < 0.6.0-rc85
fixed in 0.4.29, 0.5.0-rc51, 0.6.0-rc85
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-2266Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/auth-framework
cvss7.0ethiack provisional
1h 29msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+3.1d
0
+1d
+2d

description

Affected auth-framework releases can use publicly known built-in secrets for JARM, JWT introspection, or default SAML processing. An attacker may forge signed authorization or introspection data, or SAML tokens, that an application accepts when it relies on the affected key configuration or defaults. Material issued under those keys should be considered untrustworthy.

mitigation

Upgrade to 0.4.29, 0.5.0-rc51, or 0.6.0-rc85, as appropriate for your release line, and explicitly configure application-controlled signing keys and secrets. Rotate affected secrets and revoke or revalidate tokens and sessions issued under the prior configuration.

fixed in 0.4.29, 0.5.0-rc51, 0.6.0-rc85

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
14m
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 00:24Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2266",
  "cve_id": null,
  "display_id": "ETK-2026-2266",
  "ghsa_id": "GHSA-jr9j-g3xj-q9x8",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Hard-coded signing keys in auth-framework",
  "summary": "Affected auth-framework releases can use publicly known built-in secrets for JARM, JWT introspection, or default SAML processing. An attacker may forge signed authorization or introspection data, or SAML tokens, that an application accepts when it relies on the affected key configuration or defaults. Material issued under those keys should be considered untrustworthy.",
  "mitigation": "Upgrade to 0.4.29, 0.5.0-rc51, or 0.6.0-rc85, as appropriate for your release line, and explicitly configure application-controlled signing keys and secrets. Rotate affected secrets and revoke or revalidate tokens and sessions issued under the prior configuration.",
  "vendor": "rust",
  "product": "rust:auth-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.4.0, < 0.4.29"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.4.29"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.5.0-rc1, < 0.5.0-rc51"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.5.0-rc51"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.6.0-rc41, < 0.6.0-rc85"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.6.0-rc85"
      ],
      "package_name": "auth-framework",
      "purl": "pkg:cargo/auth-framework"
    }
  ],
  "cwes": [
    321
  ],
  "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": 14.04770775,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T00:24:57+00:00",
      "days": -3.1328664917939815,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T03:36:16.724085+00:00",
      "url": "https://github.com/ciresnave/auth-framework/security/advisories/GHSA-jr9j-g3xj-q9x8"
    }
  }
}

published 2026-10-21 02:29Z
last change 2026-10-21 03:26Z

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.