How many CVEs have patched _decode_base64url_segment?

1 published CVEs changed _decode_base64url_segment in jpadilla/pyjwt, in 1 distinct patches totalling 17 changed lines, between 2026 and 2026.

What is the latest CVE that changed _decode_base64url_segment?

CVE-2026-102269 (PyJWT: Non-canonical signature segments enable raw-token revocation bypass), published 2026-09-28, changed lines 326 to 342 of jwt/api_jws.py.

How does _decode_base64url_segment compare to the rest of jpadilla/pyjwt?

jpadilla/pyjwt has 17 CVEs with a located fix in total; 1 of them changed _decode_base64url_segment.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

jpadilla/pyjwt

Function

_decode_base64url_segment

Name: _decode_base64url_segment in jpadilla/pyjwt: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

jwt/api_jws.py

Last patched September 28, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

17

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_decode_base64url_segment in jpadilla/pyjwt was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 17 lines in total.

jpadilla/pyjwt has 17 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _decode_base64url_segment, newest first, with the lines each fix touched.

PyJWT: Non-canonical signature segments enable raw-token revocation bypass
CVE-2026-102269 · lines 326–342 · +17 −0
Medium · CVSS 5.4
EPSS 0.2%2026-09-28

Get an alert when the next CVE fix lands in jpadilla/pyjwt, with the patched functions.

Monitor pyjwt CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in jpadilla/pyjwt changed by the most CVE fixes.

prepare_key4 CVEs · jwt/algorithms.py raw_to_der_signature3 CVEs · jwt/utils.py _load2 CVEs · jwt/api_jws.py fetch_data2 CVEs · jwt/jwks_client.py _verify_signature2 CVEs · jwt/api_jws.py decode2 CVEs · jwt/api_jws.py

All patched functions in jpadilla/pyjwt

Frequently asked questions

Common questions about CVE fixes to _decode_base64url_segment.

How many CVEs have patched _decode_base64url_segment?: 1 published CVEs changed _decode_base64url_segment in jpadilla/pyjwt, in 1 distinct patches totalling 17 changed lines, between 2026 and 2026.
What is the latest CVE that changed _decode_base64url_segment?: CVE-2026-102269 (PyJWT: Non-canonical signature segments enable raw-token revocation bypass), published 2026-09-28, changed lines 326 to 342 of jwt/api_jws.py.
How does _decode_base64url_segment compare to the rest of jpadilla/pyjwt?: jpadilla/pyjwt has 17 CVEs with a located fix in total; 1 of them changed _decode_base64url_segment.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track jpadilla/pyjwt CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing