ETK-2026-2467Zero's internal tracking ID, independent of the CVE number.
validatedZero produced an exploit or a check.description
PyJWT through 2.13.0 can accept an empty symmetric key when it is loaded from an oct JWK during JWT verification. An unauthenticated attacker may create JWTs with chosen claims if the application resolves verification keys from a JWK or JWKS containing an empty key.
mitigation
Upgrade pyjwt to version 2.14.0. Audit JWK and JWKS sources, remove any symmetric entries with empty keys, and ensure signing secrets cannot default to empty values.
fixed in 2.14.0
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.
- 2026-10-22 15:48Zghsa: trigger signal, started the run
- 2026-10-22 15:48Z
this entry in the feed
GET /api/v1/feed/ETK-2026-2467
{ "etk_id": "ETK-2026-2467", "cve_id": null, "display_id": "ETK-2026-2467", "ghsa_id": "GHSA-pxh4-856f-4h89", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Empty JWK HMAC key acceptance in PyJWT", "summary": "PyJWT through 2.13.0 can accept an empty symmetric key when it is loaded from an `oct` JWK during JWT verification. An unauthenticated attacker may create JWTs with chosen claims if the application resolves verification keys from a JWK or JWKS containing an empty key.", "mitigation": "Upgrade `pyjwt` to version 2.14.0. Audit JWK and JWKS sources, remove any symmetric entries with empty keys, and ensure signing secrets cannot default to empty values.", "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": 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": 10.454053216666667, "t0_at": null, "signals": { "check": { "at": "2026-10-22T17:19:19.692787+00:00", "days": -0.02975819622685185, "is_lower_bound": true, "measured_at": "2026-10-22T18:02:10.847550+00:00", "url": null }, "public_poc": { "at": "2026-10-22T15:48:04+00:00", "days": -0.09313427015046297, "is_lower_bound": true, "measured_at": "2026-10-22T18:02:10.847550+00:00", "url": "https://github.com/advisories/GHSA-pxh4-856f-4h89" }, "trigger_signal": { "at": "2026-10-22T15:48:04+00:00", "days": -0.09313427015046297, "is_lower_bound": true, "measured_at": "2026-10-22T18:02:10.847550+00:00", "url": "https://github.com/advisories/GHSA-pxh4-856f-4h89" } } }
published 2026-10-22 17:08Z
last change 2026-10-22 17:52Z
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.