libvips is a fast image processing library with low memory needs. The EXIF decoder within libvips versions before and including 8.18.1 was not verifying the range of EXIF tag groups before passing data to libexif, leading to a possible null pointer dereference and crash. This has been patched in version 8.18.2.
CVE-2026-35590
This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(medium)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 2.1%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 20, 2026Possible out-of-bounds read leading to crash when decoding well-crafted EXIF metadata · Advisory · libvips/libvips · GitHub
https://github.com/libvips/libvips/security/advisories/GHSA-jmwm-wc68-mhwmvalidate ifdN in exif decode
Patch available: libvips/libvips v8.18.2 (PR #4972 merged 2026-03-26)
https://github.com/libvips/libvips/pull/4972commit 91ebd4d35341 (libvips/libvips)
Patch available: libvips/libvips v8.18.2 (contains commit 91ebd4d35341)
https://github.com/libvips/libvips/commit/91ebd4d35341a8353ea490392d556d582e4b846fWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:10 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 22:46 UTCEG score recompute
- 2026-07-20 19:16 UTCEG score recompute
- 2026-07-20 18:42 UTCEG score recompute
- 2026-07-20 16:38 UTCEG score recompute
- 2026-07-20 16:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
Frequently asked(5)
What is CVE-2026-35590?
When was CVE-2026-35590 disclosed?
Is CVE-2026-35590 actively exploited?
What is the CVSS score of CVE-2026-35590?
How do I remediate CVE-2026-35590?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-35590
Is Your Infrastructure Affected by CVE-2026-35590?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.