CVE-2026-27631

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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 uncaught exception 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. Due to an integer overflow, the code attempts to create a huge std::vector, which causes Exiv2 to crash with an uncaught exception. This issue has been patched in version 0.28.8.

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

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Uncaught exception: cannot create std::vector larger than max_size() · Advisory · Exiv2/exiv2 · GitHub

Affected: version v0.28.8. It is fixed by

https://github.com/Exiv2/exiv2/security/advisories/GHSA-p2pw-7935-c73j
github_pr

Add enforce to check for integer overflow

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

https://github.com/Exiv2/exiv2/pull/3514
generic

found by fuzz-preview: Uncaught exception: cannot create std::vector larger than max_size() · Issue #3513 · Exiv2/exiv2 · GitHub

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

commit 659db316eef7 (Exiv2/exiv2)

Fix landed in Exiv2/exiv2 commit 659db316eef7 — awaiting tagged release

https://github.com/Exiv2/exiv2/commit/659db316eef745899a778a1e0b760a971d1b69df

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(1)

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 8× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 18:50 UTCOSV refresh
  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-30 22:04 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 43 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 08:42 UTCEG score recompute
  11. 2026-08-14 08:42 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 00:33 UTCEG score recompute
  14. 2026-08-13 00:33 UTCVendor advisory
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 23:23 UTCEG score recompute
  17. 2026-08-11 23:23 UTCVendor advisory
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 09:30 UTCEG score recompute
  21. 2026-08-10 09:30 UTCVendor advisory
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 08:19 UTCEG score recompute
  24. 2026-08-09 08:19 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-07 20:15 UTCEG score recompute
  27. 2026-08-07 20:15 UTCVendor advisory
  28. 2026-08-06 13:46 UTCEPSS rescore
  29. 2026-08-06 02:49 UTCEG score recompute
  30. 2026-08-06 02:49 UTCVendor advisory
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 04:34 UTCEG score recompute
  34. 2026-08-04 04:34 UTCVendor advisory
  35. 2026-08-03 10:36 UTCEPSS rescore
  36. 2026-08-02 19:09 UTCEG score recompute
  37. 2026-08-02 19:09 UTCVendor advisory
  38. 2026-08-02 02:26 UTCEPSS rescore
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-07-30 16:27 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-28 15:36 UTCEPSS rescore
  43. 2026-07-27 13:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-27631?
CVE-2026-27631 is a medium 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 uncaught exception 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-27631 disclosed?
CVE-2026-27631 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-27631 actively exploited?
CVE-2026-27631 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 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-27631?
CVE-2026-27631 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-27631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27631, 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-27631

Explore →

Is Your Infrastructure Affected by CVE-2026-27631?

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