Mozjpeg
3 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Mozjpeg, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Mozjpeg 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 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 3 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
Latest CVEs
The 3 most recently published vulnerabilities affecting Mozjpeg.
- GHSA-v8gq-5grq-9728mozjpeg DecompressScanlines::read_scanlines is Unsound—
- CVE-2020-13790libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file.8.1
- CVE-2018-14498get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-b...6.5
Product grouping is registry-driven, with AI assist and human review. How it works