CVE-2026-102273

validatedZero produced an exploit or a check.

GHSA-w2cx-738m-mc7w ↗EUVD-2026-88541 ↗

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:PyJWT = 2.13.0
fixed in 2.14.0
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-14, permanent identifier
pkg:pypi/PyJWT
+1.0dTTV
12mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+24h27magent stopped
0
+6h
+12h
+18h

description

PyJWT 2.13.0 can mishandle public-key material stored in JWK container formats during HMAC JWT verification. An attacker with the public key may create tokens carrying attacker-chosen authenticated claims when the application mixes HMAC and asymmetric algorithms and reuses raw public JWK or JWKS data as an HMAC key.

mitigation

Upgrade PyJWT to version 2.14.0 or later. Keep symmetric and asymmetric verification flows separate, and do not use public JWK or JWKS data as an HMAC secret.

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%6th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-28 20:38Z
Δ 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

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:38Z
  2. 2026-09-28 20:38Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-14",
  "cve_id": "CVE-2026-102273",
  "display_id": "CVE-2026-102273",
  "ghsa_id": "GHSA-w2cx-738m-mc7w",
  "euvd_id": "EUVD-2026-88541",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Algorithm-confusion token forgery in PyJWT HMAC key handling",
  "summary": "PyJWT 2.13.0 can mishandle public-key material stored in JWK container formats during HMAC JWT verification. An attacker with the public key may create tokens carrying attacker-chosen authenticated claims when the application mixes HMAC and asymmetric algorithms and reuses raw public JWK or JWKS data as an HMAC key.",
  "mitigation": "Upgrade PyJWT to version 2.14.0 or later. Keep symmetric and asymmetric verification flows separate, and do not use public JWK or JWKS data as an HMAC secret.",
  "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.0655,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 11.581535066666667,
  "t0_at": "2026-09-28T20:38:28.161000+00:00",
  "signals": {
    "check": {
      "at": "2026-09-29T21:05:22.842607+00:00",
      "days": 1.018688444525463,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:38:28.161000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-28T20:38:28.161000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-28T20:38:28.161000+00:00",
      "url": "https://github.com/jpadilla/pyjwt/security/advisories/GHSA-w2cx-738m-mc7w"
    }
  }
}

published 2026-09-29 20:53Z
last change 2026-10-21 05:00Z

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.