CVE-2024-25189: libjwt · n/a
Affects libjwtSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubbenmcollins/libjwtpkg:github/benmcollins/libjwtOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-25189, organizations should immediately audit their use of libjwt and identify affected versions, particularly version 1.15.3. The primary remediation is to update libjwt to a version where the strcmp function is replaced with a constant-time comparison function designed to prevent timing side-channel attacks. If an official patch is not yet available, developers should implement a custom constant-time string comparison for authentication verification. Additionally, applying compensating controls such as rate limiting, anomaly detection for authentication attempts, and enhanced logging can help detect and prevent exploitation attempts. Security teams should monitor libjwt project repositories and vulnerability advisories for patches or updates. Finally, reviewing JWT usage patterns and enforcing strict token validation policies can reduce the attack surface.
Description
libjwt 1.15.3 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass authentication via a timing side channel.