CVE-2026-114615

validatedZero produced an exploit or a check.

GHSA-7vr2-2fgp-9w7p ↗EUVD-2026-108514 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
pip:Authlib >= 1.3.1, <= 1.8.0
fixed in 1.9.0
ETK-2026-2789Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/authlib
+5.0dTTV
15mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+5.0dagent stopped
0
+1d
+2d
+3d
+4d

description

Authlib versions 1.3.1 through 1.8.0 can misclassify prefixed PEM public keys or certificates as HMAC secrets during JWT verification. An unauthenticated attacker who knows the public key may forge tokens with arbitrary identity or authorization claims when the application accepts both symmetric and asymmetric JWT algorithms and uses affected key text.

mitigation

Upgrade Authlib to version 1.9.0. Until upgraded, restrict JWT verification to the intended asymmetric algorithm and remove leading whitespace, comments, or byte-order marks from configured PEM and certificate data.

fixed in 1.9.0

check
available
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 21:10Z
Δ 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 check: a technique exists and was validated, 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-22 21:10Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 21:10Z

this entry in the feed

GET /api/v1/feed/CVE-2026-114615

{
  "etk_id": "ETK-2026-2789",
  "cve_id": "CVE-2026-114615",
  "display_id": "CVE-2026-114615",
  "ghsa_id": "GHSA-7vr2-2fgp-9w7p",
  "euvd_id": "EUVD-2026-108514",
  "status": "published",
  "anchor_state": "anchored",
  "title": "JWT algorithm confusion in Authlib JOSE key handling",
  "summary": "Authlib versions 1.3.1 through 1.8.0 can misclassify prefixed PEM public keys or certificates as HMAC secrets during JWT verification. An unauthenticated attacker who knows the public key may forge tokens with arbitrary identity or authorization claims when the application accepts both symmetric and asymmetric JWT algorithms and uses affected key text.",
  "mitigation": "Upgrade Authlib to version 1.9.0. Until upgraded, restrict JWT verification to the intended asymmetric algorithm and remove leading whitespace, comments, or byte-order marks from configured PEM and certificate data.",
  "vendor": "pip",
  "product": "pip:Authlib",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.3.1, <= 1.8.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.9.0"
      ],
      "package_name": "authlib",
      "purl": "pkg:pypi/authlib"
    }
  ],
  "cwes": null,
  "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": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 15.175328116666666,
  "t0_at": "2026-10-22T21:10:02.023000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-27T20:33:33.696801+00:00",
      "days": 4.974672150474537,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T21:10:02.023000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-22T21:10:02.023000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T21:10:02.023000+00:00",
      "url": "https://github.com/advisories/GHSA-7vr2-2fgp-9w7p"
    }
  }
}

published 2026-10-27 20:18Z
last change 2026-10-27 21:27Z

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.