CVE-2024-25191: php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypa
CVE-2024-25191 is a critical-severity flaw (CVSS 9.8) affecting php-jwt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass authentication via a timing side channel.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.9% (top 41%) |
| CISA exploited list | No |
| Weakness | CWE-203 |
| Published | 2024-02-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-25191?
php-jwt: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2024-25191 being exploited?
CVE-2024-25191 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-25191 affect?
CVE-2024-25191 affects php-jwt. Severity is critical (CVSS 9.8). php-jwt 1.0.0 uses strcmp (which is not constant time) to verify authentication, which makes it easier to bypass authentication via a timing side channel.
How urgent is CVE-2024-25191?
Priority 59/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action