Jwcrypto
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Jwcrypto, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Jwcrypto CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 1 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Medium4
Latest CVEs
The 5 most recently published vulnerabilities affecting Jwcrypto.
- CVE-2026-39373JWCrypto: JWE ZIP decompression bomb5.3
- CVE-2024-28102JWCrypto vulnerable to JWT bomb Attack in `deserialize` function6.8
- CVE-2023-6681Jwcrypto: denail of service via specifically crafted jwe5.3
- CVE-2022-3102jwcrypto token substitution can lead to authentication bypass—
- CVE-2016-6298The _Rsa15 class in the RSA 1.5 algorithm implementation in jwa.py in jwcrypto before 0.3.2 lacks the Random Filling protection mechanism, which makes it easier for remote attackers to obtain clear...5.3
Product grouping is registry-driven, with AI assist and human review. How it works