CVE-2026-2913

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
7.0EG
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.0Exploit: Elevated riskExposed: 0

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

A vulnerability was determined in libvips up to 8.19.0. The affected element is the function vips_source_read_to_memory of the file libvips/iofuncs/source.c. This manipulation causes heap-based buffer overflow. It is possible to launch the attack on the local host. The attack's complexity is rated as high. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. Patch name: a56feecbe9ed66521d9647ec9fbcd2546eccd7ee. Applying a patch is the recommended action to fix this issue. The confirmation of the bugfix mentions: "[T]he impact of this is negligible, since this only affects custom seekable sources larger than 4 GiB (and the crash occurs in user code rather than libvips itself)."

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
48(Track)
EG Risk 48/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
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

February 22, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit.
generic

Heap-buffer-overflow in `vips_source_read_to_memory()` (integer truncation) · Issue #4857 · libvips/libvips · GitHub

https://github.com/libvips/libvips/issues/4857#issuecomment-3878479322
generic

Heap-buffer-overflow in `vips_source_read_to_memory()` (integer truncation) · Issue #4857 · libvips/libvips · GitHub

https://github.com/libvips/libvips/issues/4857#issue-3920154326
generic

Heap-buffer-overflow in `vips_source_read_to_memory()` (integer truncation) · Issue #4857 · libvips/libvips · GitHub

https://github.com/libvips/libvips/issues/4857
github_commit Patch Available

commit a56feecbe9ed (libvips/libvips)

Patch available: libvips/libvips v8.18.1 (contains commit a56feecbe9ed)

https://github.com/libvips/libvips/commit/a56feecbe9ed66521d9647ec9fbcd2546eccd7ee
generic

GitHub - libvips/libvips: A fast image processing library with low memory needs. · GitHub

https://github.com/libvips/libvips/

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vips8.10.5-2 ... 8.18.4-1 (41 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vips8.14.1-3, 8.14.1-3+deb12u1, 8.14.1-3+deb12u28.14.1-3+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vips8.16.1-18.16.1-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vips8.16.1-1, 8.16.1-2, 8.17.3-1, 8.17.3-2, 8.18.0-18.18.0-2—

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 196 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-19 13:33 UTCOSV refresh
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 19:27 UTCEPSS rescore
  6. 2026-09-17 19:30 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-13 16:47 UTCEPSS rescore
  10. 2026-09-12 15:01 UTCEPSS rescore
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-31 17:04 UTCOSV refresh
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-28 21:41 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 14:17 UTCEPSS rescore
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 21:33 UTCGHSA enrichment
  16. 2026-08-14 09:15 UTCEG score recompute
  17. 2026-08-14 09:15 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 01:19 UTCEG score recompute
  20. 2026-08-13 01:19 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-12 01:22 UTCEG score recompute
  23. 2026-08-12 01:22 UTCGHSA enrichment
  24. 2026-08-11 06:45 UTCEG score recompute
  25. 2026-08-11 06:45 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 09:14 UTCGHSA enrichment
  28. 2026-08-09 20:12 UTCEG score recompute
  29. 2026-08-09 20:12 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 08:52 UTCEG score recompute
  32. 2026-08-09 08:52 UTCGHSA enrichment
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 08:21 UTCGHSA enrichment
  35. 2026-08-07 21:02 UTCEG score recompute
  36. 2026-08-07 21:02 UTCGHSA enrichment
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 03:14 UTCEG score recompute
  39. 2026-08-06 03:14 UTCGHSA enrichment
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 19:49 UTCEG score recompute▲ 4.50
  44. 2026-08-02 19:49 UTCGHSA enrichment
  45. 2026-08-02 02:26 UTCEPSS rescore
  46. 2026-07-30 16:27 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-28 15:36 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:17 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:08 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 14:31 UTCEPSS rescore
  63. 2026-07-19 02:29 UTCEPSS rescore
  64. 2026-07-18 10:04 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-16 17:03 UTCEPSS rescore
  67. 2026-07-16 17:03 UTCEPSS rescore
  68. 2026-07-16 09:49 UTCOSV refresh
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 02:00 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-13 22:30 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-13 06:13 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-2913?
CVE-2026-2913 is a high vulnerability published on February 22, 2026. A vulnerability was determined in libvips up to 8.19.0. The affected element is the function vipssourcereadtomemory of the file libvips/iofuncs/source.c. This manipulation causes heap-based buffer overflow. It is possible to launch the attack on the local host. The attack's complexity is rated as…
When was CVE-2026-2913 disclosed?
CVE-2026-2913 was first published in the National Vulnerability Database on February 22, 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-2913 actively exploited?
CVE-2026-2913 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 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-2913?
CVE-2026-2913 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-2913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2913, 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-2913

Explore →

Is Your Infrastructure Affected by CVE-2026-2913?

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

Start Free Scan →Browse All CVEs