On this page (7 sections)

Ubuntu published security notice USN-9177-1 on 20 November 2026 for PyJWT, the Python library many web applications use to create and verify JSON Web Tokens (JWTs). According to the Ubuntu notice, PyJWT incorrectly accepted non-canonical encodings of token signature segments.

If you run Python applications on Ubuntu 22.04 LTS, 24.04 LTS or 26.04 LTS that verify JWTs, especially ones that rely on a token blocklist or revocation list, you should apply the updated python3-jwt package. The notice describes the impact as a possible bypass of token revocation checks.

What Ubuntu says happened

The notice is short. It states that PyJWT accepted non-canonical encodings of the signature segment of a token, and that an attacker could possibly use this to bypass token revocation checks. Ubuntu lists CVE-2026-102269 as the reference. The notice gives no CVSS score, no upstream PyJWT version number and no exploit details, and this article does not go beyond that.

Only one publisher, Ubuntu, covers this issue in the research available so far. Treat details such as severity and upstream fixed versions as unconfirmed until the CVE record or the PyJWT project publishes them.

Why non-canonical signatures matter

A JWT has three parts separated by dots: a header, a payload and a signature. Each part is base64url encoded. In base64-style encodings, more than one text string can sometimes decode to the same underlying bytes, for example when unused trailing bits are set to different values. The canonical form is the single, strictly correct encoding. A strict verifier rejects the alternatives.

If a library accepts those alternative encodings, two different-looking token strings can both verify as validly signed with the same signature bytes. That becomes a problem when an application identifies a token by its raw string. A revocation list that stores the exact string, or a hash of it, of a logged-out or stolen token would not match a re-encoded variant. This is the general mechanism behind the impact Ubuntu describes. The notice itself does not spell out the exact mechanics, so treat this as background, not as a statement about the specific code path.

Who is realistically exposed

  • Applications that verify JWTs with PyJWT and also keep a denylist of revoked tokens keyed by the token string or its hash.
  • Services where logout, password reset or incident response relies on invalidating specific tokens before they expire.
  • Servers running the Ubuntu-packaged python3-jwt, or apps that import the system package rather than a copy installed in a virtual environment.

Applications that use short token lifetimes and never depend on per-token revocation have a smaller practical exposure, but updating is still the right move.

How to check your exposure

The fixed package versions per release are listed in the table below, taken from the Ubuntu notice.

Fixed python3-jwt versions in USN-9177-1
Ubuntu releaseCodenameFixed python3-jwt version
26.04 LTSresolute2.10.1-4ubuntu1.4
24.04 LTSnoble2.7.0-1ubuntu0.5
22.04 LTSjammy2.3.0-1ubuntu0.7

This read-only command shows the installed and candidate versions of the package on Ubuntu. If the installed version is older than the one in the table for your release, you need to update.

Check the installed python3-jwt version (Ubuntu)Shell
apt-cache policy python3-jwt

PyJWT can also be installed with pip inside a virtual environment or container image. Those copies are not changed by the Ubuntu update. This read-only command, run with the same Python environment your app uses, lists the installed version so you can compare it with upstream guidance.

Show the pip-installed PyJWT version in the active environmentShell
pip show pyjwt

What to do now

  1. Run a standard system update on every Ubuntu 22.04, 24.04 and 26.04 host that has python3-jwt installed.
  2. Confirm the installed version matches or exceeds the fixed version for your release.
  3. Restart the application services or workers that import PyJWT so they load the new library.
  4. Check virtual environments and container images that bundle their own PyJWT, and rebuild or upgrade them separately.
  5. Review how your app identifies revoked tokens. Prefer checking a token ID claim (jti) or a server-side session record over the raw token string.
  6. If you suspect revoked tokens were reused, consider rotating signing keys and shortening token lifetimes.

This command refreshes package lists and upgrades only the python3-jwt package on Ubuntu.

Update python3-jwt (Ubuntu)Shell
sudo apt update && sudo apt install --only-upgrade python3-jwt
Caution. Restarting application services interrupts requests in flight. Schedule it for a maintenance window, and note that rotating signing keys will log out every user holding an existing token.
Tip. A full system update also works, as the notice says a standard update will make the necessary changes. If you prefer, run your usual unattended or scheduled upgrade process.

Detection and monitoring afterwards

The notice does not describe indicators of compromise, so there is nothing specific to search for. Practical steps are general ones: watch authentication logs for tokens that are used after a logout or revocation event, and for the same session appearing from unexpected addresses. Keep an eye on the CVE record for CVE-2026-102269 for a severity score and any upstream details.

For the public side of your site, the free security headers checker and the SSL checker help confirm your basic configuration, and our guide to small business website security covers patching routines.

Timeline

  • 20 November 2026: Ubuntu publishes USN-9177-1 with fixed python3-jwt packages for 22.04 LTS, 24.04 LTS and 26.04 LTS.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9177-1: PyJWT vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • PyJWT
  • Ubuntu
  • JWT
  • USN
  • Python