Ubuntu Fixes PyJWT Token-Revocation Bypass
Quick Answer
Update python3-jwt on matching Ubuntu releases, restart dependent applications, and verify that revoked-token variants are rejected.
Confirm Scope And Apply The Supported Remediation
What to do now: Record Ubuntu release, package versions, active executable or library, application owner, container images and maintenance entitlement. Identify applications that rely on token revocation and the system PyJWT package. Independently assess bundled, virtual-environment and container copies. Install the matching packages through the supported Ubuntu repository; restart or redeploy affected processes so they use the updated runtime or library. Verify installed and active versions, test the relevant application workflows, monitor regressions, and retain package transactions and service-validation evidence.
Last verified: 2026-11-20 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | PyJWT python3-jwt packages |
|---|---|
| Advisory | USN-9177-1 |
| CVE | CVE-2026-102269 |
| Authoritative release date | 2026-11-20T00:45:22Z — Canonical security-notice feed, corroborated by the first-party notice API. |
| Authority revision date | No separate material revision is stated for this release. |
| Affected versions | The listed PyJWT python3-jwt packages on Ubuntu 26.04 LTS resolute, 24.04 LTS noble, 22.04 LTS jammy before their corresponding corrected package builds. Feature and CVE applicability varies by release. |
| Fixed version | Install the Ubuntu-release-specific package builds in the complete version matrix below. |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | The cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred. |
What Changed
PyJWT accepted non-canonical encodings of JWT signature segments, potentially allowing an attacker to bypass token-revocation checks.
What To Validate Now
- Inventory. Record Ubuntu release, package versions, active executable or library, application owner, container images and maintenance entitlement.
- Establish applicability. Identify applications that rely on token revocation and the system PyJWT package. Independently assess bundled, virtual-environment and container copies.
- Remediate. Install the matching packages through the supported Ubuntu repository; restart or redeploy affected processes so they use the updated runtime or library.
- Validate. Verify installed and active versions, test the relevant application workflows, monitor regressions, and retain package transactions and service-validation evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Preserve signing keys and normal token lifetimes while testing. A package update does not prove previously accepted tokens or application-specific revocation stores were reviewed.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Release-Specific Version Matrix
| Ubuntu release | Package, fixed build and channel |
|---|---|
| 26.04 LTS resolute | python3-jwt – 2.10.1-4ubuntu1.4 |
| 24.04 LTS noble | python3-jwt – 2.7.0-1ubuntu0.5 |
| 22.04 LTS jammy | python3-jwt – 2.3.0-1ubuntu0.7 |
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

