CVE-2023-27781 json
jpegoptim v1.5.2 was discovered to contain a heap overflow in the optimize function at jpegoptim.c.
published 2023-03-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-31517
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
jpegoptim v1.5.2 was discovered to contain a heap overflow in the optimize function at jpegoptim.c.
Patch / fix
- github.com/tjko/jpegoptim/issues/132 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-27781 updated
jpegoptim: Heap overflow in the optimize function at jpegoptim.c.
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 20 mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tjko/jpegoptim/issues/132 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/tjko/jpegoptim/issues/132
exploit, issue-tracking, patch, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/66ZW65INCWSQYIT5E6N6I6PE5D7R6EK7/
vendor-advisory
Sources
- CVE List CVE-2023-27781
- NVD CVE-2023-27781
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.