CVE-2026-27596

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. Prior to version 0.28.8, an out-of-bounds read was found in Exiv2. The vulnerability is in the preview component, which is only triggered when running Exiv2 with an extra command line argument, like -pp. The out-of-bounds read is at a 4GB offset, which usually causes Exiv2 to crash. This issue has been patched in version 0.28.8.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Integer overflow in LoaderNative::getData() causes out-of-bounds read · Advisory · Exiv2/exiv2 · GitHub

Affected: version v0.28.8. It is fixed by

https://github.com/Exiv2/exiv2/security/advisories/GHSA-3wgv-fg4w-75x7
github_pr

add enforce to prevent integer overflow

Fix merged in Exiv2/exiv2 PR #3512 on 2026-02-27 — awaiting tagged release

https://github.com/Exiv2/exiv2/pull/3512
generic🟡 PoC Available

Integer Underflow in LoaderNative::getData() · Issue #3511 · Exiv2/exiv2 · GitHub

https://github.com/Exiv2/exiv2/issues/3511
github_commit

commit eaa9e21aabe0 (Exiv2/exiv2)

Fix landed in Exiv2/exiv2 commit eaa9e21aabe0 — awaiting tagged release

https://github.com/Exiv2/exiv2/commit/eaa9e21aabe06b3f91cfe66686f5ebc3ca3c0ed4

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
exiv20.27.3-3 ... 0.28.8+dfsg-1 (25 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
exiv20.27.6-1 ... 0.28.9+dfsg-1 (18 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
exiv20.28.5+dfsg-1, 0.28.7+dfsg-1, 0.28.7+dfsg-2, 0.28.8+dfsg-1, 0.28.9+dfsg-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
exiv20.28.5+dfsg-1, 0.28.7+dfsg-1, 0.28.7+dfsg-20.28.8+dfsg-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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.

  1. 2026-09-19 13:02 UTCOSV refresh
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-31 16:34 UTCOSV refresh
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
Show 48 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 21:11 UTCVendor advisory
  11. 2026-08-14 08:42 UTCEG score recompute
  12. 2026-08-14 08:42 UTCVendor advisory
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 00:32 UTCEG score recompute
  15. 2026-08-13 00:32 UTCVendor advisory
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:23 UTCEG score recompute
  18. 2026-08-11 23:23 UTCVendor advisory
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 05:56 UTCEG score recompute
  21. 2026-08-11 05:56 UTCVendor advisory
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 09:17 UTCVendor advisory
  24. 2026-08-09 20:48 UTCEG score recompute
  25. 2026-08-09 20:48 UTCVendor advisory
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 08:19 UTCEG score recompute
  28. 2026-08-09 08:19 UTCVendor advisory
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 08:44 UTCVendor advisory
  31. 2026-08-07 20:15 UTCEG score recompute
  32. 2026-08-07 20:15 UTCVendor advisory
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 02:49 UTCEG score recompute
  35. 2026-08-06 02:49 UTCVendor advisory
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 04:34 UTCEG score recompute
  39. 2026-08-04 04:34 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 19:09 UTCEG score recompute
  42. 2026-08-02 19:09 UTCVendor advisory
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 04:16 UTCEPSS rescore
  45. 2026-07-30 16:27 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-28 15:36 UTCEPSS rescore
  48. 2026-07-27 13:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-27596?
CVE-2026-27596 is a high vulnerability published on March 2, 2026. Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. Prior to version 0.28.8, an out-of-bounds read was found in Exiv2. The vulnerability is in the preview component, which is only triggered when running Exiv2 with an extra…
When was CVE-2026-27596 disclosed?
CVE-2026-27596 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27596 actively exploited?
CVE-2026-27596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.5% of all scored CVEs.
What is the CVSS score of CVE-2026-27596?
CVE-2026-27596 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-27596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27596

Explore →

Is Your Infrastructure Affected by CVE-2026-27596?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.