Is there a public exploit for CVE-2026-101917?

No public exploit for CVE-2026-101917 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-101917?

CVE-2026-101917 scores CVSS 7.5 (v3.1), rated high. EPSS puts the chance of exploitation in the next 30 days at 0.43%.

What does CVE-2026-101917 affect?

CVE-2026-101917 affects jpadilla pyjwt.

7.5 High

PyJWT is a Python implementation of JSON Web Token standards.

CVE-2026-101917

Summary CVE-2026-48524 (GHSA-fhv5-28vv-h8m8, "PyJWKClient unbounded JWKS endpoint requests via attacker-controlled kid values (DoS)") was fixed in 2.13.0 by stopping fetchdata() from clearing the cache on a fetch error. That closed one amplification path but did not add the mitigation the advisory's title implies: there is still no rate-limit, negative-cache, or minimum-refresh-interval for unknown kids. At HEAD, getsigningkey(kid) (jwt/jwksclient.py:185-211), on any unknown kid, calls getsigningkeys(refresh=True), and refresh=True bypasses jwksetcache unconditionally and forces a fresh fetchdata(). The kid is read from the unverified token header (getsigningkeyfromjwt decodes with verifysignature=False), so no valid token and no authentication is required. lrucache does not cache the raised exception, so even the same unknown kid repeated re-fetches on every call. Affected pyjwt fetches:', hits['n']) print('same unknown kid x5 -> extra fetches:', hits['n'] - before) Output: distinct unknown kids: 8 -> fetches: 9 same unknown kid x5 -> extra fetches: 5 Each unknown kid forces a fresh JWKS fetch; a repeated identical unknown kid still re-fetches every time against an unexpired…

Assessment

CVSS: 7.5 (v3.1)
Severity: High
EPSS: 0.43% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 28 September 2026
Last updated: 7 October 2026
Affected: jpadilla · pyjwt · pyjwt
Weakness: CWE-770
Assigner: security-advisories@github.com

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 5? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-101917