On this page (6 sections)
Ubuntu published USN-9075-1 on 12 November 2026. It covers libjwt, a C library for handling JSON Web Tokens (JWTs). Canonical says the library did not use a constant-time comparison when verifying HMAC signatures, so a remote attacker could possibly forge signatures through a timing side channel and bypass authentication.
If you run a service on Ubuntu 18.04, 20.04 or 22.04 that links against libjwt to validate tokens, this notice is for you. Most websites do not use this library directly, but custom C or C++ APIs and some embedded or appliance software might.
What Ubuntu says happened
The notice is short. It states that libjwt did not use a constant-time comparison when verifying HMAC signatures, and that a remote attacker could possibly use this to forge signatures through a timing side-channel attack and bypass authentication. Ubuntu summarizes it as libjwt "could be made to accept forged tokens."
The notice references CVE-2024-25189. The research available for this article did not include a CVE record, a CVSS score or any exploitation report, so the severity is unrated here and no real-world attacks are confirmed. Only one primary source (the Ubuntu notice) was reviewed, so treat details beyond it as unverified.
Why a non-constant-time comparison matters
A JWT carries a signature. With HMAC-based algorithms, the server recomputes the expected signature using a shared secret and compares it to the one in the token. If that comparison stops at the first byte that differs, the time it takes leaks how many leading bytes were correct. An attacker who can send many requests and measure response times could, in theory, learn a valid signature one piece at a time without knowing the secret.
The standard defense is a constant-time comparison, which takes the same time no matter where the mismatch is. Timing attacks over a network are noisy and hard, which is why Ubuntu words this as "possibly". Still, a successful forgery would mean an attacker could present tokens the application trusts, which is why authentication bypass is the stated impact.
Who is realistically exposed
- Servers on Ubuntu 18.04, 20.04 or 22.04 with the libjwt0 or libjwt-gnutls0 packages installed.
- Applications that actually call libjwt to verify HMAC-signed tokens (for example HS256) on requests an outside party can reach.
- Hosts that have the package installed only as a dependency but never validate tokens are much less likely to matter, though updating is still sensible.
Typical WordPress, PHP, Node.js or Python sites use their own JWT libraries and are not affected by this notice unless they are built on libjwt. If you are unsure, the checks below show whether the package is present.
How to check your exposure
This read-only command lists installed libjwt packages and their versions on Ubuntu. Compare the output with the fixed versions in the table below. No output means the package is not installed.
dpkg -l | grep libjwtTo see which installed packages depend on libjwt, run this read-only query. Replace the package name with libjwt-gnutls0 if that is the one installed.
apt-cache rdepends --installed libjwt0| Ubuntu release | Package | Fixed version |
|---|---|---|
| 22.04 LTS (jammy) | libjwt0, libjwt-gnutls0 | 1.10.2-1ubuntu0.22.04.1~esm1 |
| 20.04 LTS (focal) | libjwt0, libjwt-gnutls0 | 1.10.2-1ubuntu0.20.04.1~esm1 |
| 18.04 LTS (bionic) | libjwt0 | 1.9.0-1ubuntu0.1~esm1 |
What to do now
- Run the dpkg command above on each Ubuntu server and note any libjwt0 or libjwt-gnutls0 versions older than the fixed ones.
- Identify which applications use libjwt for token validation, and whether they are reachable from the internet.
- Attach the machine to Ubuntu Pro if it is not already, since the fixed packages are delivered through ESM Apps.
- Apply a standard system update, as the notice advises, then re-run the version check to confirm the new package is installed.
- Restart the services that load libjwt so they pick up the updated library.
- If an exposed service cannot be updated soon, consider rate limiting requests to token-protected endpoints, which makes timing measurements harder.
This is the standard update path on Ubuntu. The first command refreshes package lists and the second upgrades only the named package.
sudo apt update
sudo apt install --only-upgrade libjwt0Detection and follow-up
A timing attack needs many requests, so look for unusual volumes of failed token validations or repeated requests with slightly varying tokens against one endpoint in your application and web server logs. The notice does not describe any indicators, so this is general guidance rather than a known signature of this issue.
- Alert on spikes of 401 or 403 responses from a single client address.
- Rotate HMAC signing secrets if you suspect forged tokens were accepted, and shorten token lifetimes where practical.
- Keep a short inventory of which services use which JWT library so future notices are quick to triage.
For broader hygiene, a free security headers check and the website security guide for small businesses cover the basics around exposed services. If you want change alerts on your public endpoints, Webforta Monitor tracks uptime, certificate, DNS and header changes, though it does not detect this library flaw.
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.
