Vulnerabilities
Summary — last 7 days
New vulnerabilities3,202▲ 616 vs. last week
Critical / high1,511▲ 116 vs. last week
New active exploitation (KEV)5▼ 1 vs. last week
Unscored (no CVSS)236▲ 222 vs. last week
3 results, sorted by published date (most recent first)
| CVE | Status | Severity | EPSS | Active exploitation | Affected technologies | Published ▼ | Modified | Description |
|---|---|---|---|---|---|---|---|---|
| Modified | Medium (6.5) | 0.14% | — | Google Firebase Php-jwt | 7/31/2025 | 6/17/2026 | php-jwt v6.11.0 was discovered to contain weak encryption. NOTE: this issue has been disputed on the basis that key lengths are expected to be set by an application, not by this library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an… | |
| Modified | Critical (9.8) | 0.89% | — | Zihanggao Php-jwt | 2/8/2024 | 6/17/2026 | 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. | |
| Modified | Critical (9.1) | 0.79% | — | Google Firebase Php-jwt | 3/29/2022 | 6/17/2026 | In Firebase PHP-JWT before 6.0.0, an algorithm-confusion issue (e.g., RS256 / HS256) exists via the kid (aka Key ID) header, when multiple types of keys are loaded in a key ring. This allows an attacker to forge tokens that validate under the incorrect key. NOTE: this provides a straightforward way to use the PHP-JWT… |