CVE-2026-102266

validatedZero produced an exploit or a check.

GHSA-9j54-fg26-wv3r ↗EUVD-2026-88484 ↗

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).+1.1dkevAttacks confirmed in the real world.
pip:PyJWT 2.13.0
fixed in 2.14.0
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-22, permanent identifier
pkg:pypi/PyJWT
+1.1dTTV
13mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+25h39magent stoppedpublic poc+27h22m
0
+6h
+12h
+18h
+24h
+30h

description

PyJWT versions 2.13.0 through 2.13.x can accept forged HS256 tokens when verification uses a PyJWK or PyJWKSet entry containing an empty symmetric key. An attacker can impersonate authenticated users or supply arbitrary claims if the application has such an empty oct JWK configured.

mitigation

Upgrade PyJWT to version 2.14.0 or later. Audit configured JWK sets for empty symmetric keys and reject them; enable minimum HMAC key-length enforcement until the upgrade is complete.

fixed in 2.14.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.
0.18%7th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-28 20:21Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1.1d
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-09-28 20:21Z
  2. 2026-09-28 20:21Z
  3. 2026-09-29 23:43Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-22",
  "cve_id": "CVE-2026-102266",
  "display_id": "CVE-2026-102266",
  "ghsa_id": "GHSA-9j54-fg26-wv3r",
  "euvd_id": "EUVD-2026-88484",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Empty HMAC JWK authentication bypass in PyJWT",
  "summary": "PyJWT versions 2.13.0 through 2.13.x can accept forged HS256 tokens when verification uses a PyJWK or PyJWKSet entry containing an empty symmetric key. An attacker can impersonate authenticated users or supply arbitrary claims if the application has such an empty `oct` JWK configured.",
  "mitigation": "Upgrade PyJWT to version 2.14.0 or later. Audit configured JWK sets for empty symmetric keys and reject them; enable minimum HMAC key-length enforcement until the upgrade is complete.",
  "vendor": "pip",
  "product": "pip:PyJWT",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.13.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.14.0"
      ],
      "package_name": "PyJWT",
      "purl": "pkg:pypi/PyJWT"
    }
  ],
  "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": 0.0018,
  "epss_percentile": 0.0736,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 12.846870283333333,
  "t0_at": "2026-09-28T20:21:26.164000+00:00",
  "signals": {
    "check": {
      "at": "2026-09-29T21:59:57.025947+00:00",
      "days": 1.0684127540162036,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:21:26.164000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-09-29T23:43:19+00:00",
      "days": 1.140194861111111,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:21:26.164000+00:00",
      "url": "https://github.com/advisories/GHSA-9j54-fg26-wv3r"
    },
    "trigger_signal": {
      "at": "2026-09-28T20:21:26.164000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:21:26.164000+00:00",
      "url": "https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9j54-fg26-wv3r"
    }
  }
}

published 2026-09-29 21:47Z
last change 2026-10-21 06:02Z

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.