CVE-2026-102272

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

GHSA-r6x4-923q-g947 ↗EUVD-2026-88540 ↗

no check availablenot proven exploitable
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:PyJWT 2.13.0
fixed in 2.14.0
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-18, permanent identifier
pkg:pypi/PyJWT
6d 00h 25msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+394h01m
0
+2h
+4h
+6h
+8h
+10h

description

PyJWT 2.13.0 can mishandle encoded public JWK data and use it as HMAC key material during JWT verification. An attacker who knows the public key may forge tokens if the application supplies a raw RSA JWK and permits both HMAC and RSA algorithms.

mitigation

Upgrade PyJWT to 2.14.0. Until upgrading, restrict each verification path to its expected algorithm family and do not combine HMAC and asymmetric algorithms for the same raw public JWK key.

fixed in 2.14.0

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.18%7th percentile
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-28 20:36Z
Δ 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-09-28 20:36Z
  2. 2026-09-28 20:36Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-18",
  "cve_id": "CVE-2026-102272",
  "display_id": "CVE-2026-102272",
  "ghsa_id": "GHSA-r6x4-923q-g947",
  "euvd_id": "EUVD-2026-88540",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Algorithm-confusion flaw in PyJWT token verification",
  "summary": "PyJWT 2.13.0 can mishandle encoded public JWK data and use it as HMAC key material during JWT verification. An attacker who knows the public key may forge tokens if the application supplies a raw RSA JWK and permits both HMAC and RSA algorithms.",
  "mitigation": "Upgrade PyJWT to 2.14.0. Until upgrading, restrict each verification path to its expected algorithm family and do not combine HMAC and asymmetric algorithms for the same raw public JWK key.",
  "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.0732,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.527347033333333,
  "t0_at": "2026-09-28T20:36:31.530000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-28T20:36:31.530000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:36:31.530000+00:00",
      "url": "https://github.com/jpadilla/pyjwt/security/advisories/GHSA-r6x4-923q-g947"
    }
  }
}

published 2026-09-29 21:17Z
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.