CVE-2025-55286

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2025-28586 (ENISA EUVD)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

z2d is a pure Zig 2D graphics library. z2d v0.7.0 released with a new multi-sample anti-aliasing (MSAA) method, which uses a new buffering mechanism for storing coverage data. This differs from the standard alpha mask surface used for the previous super-sample anti-aliasing (SSAA) method. Under certain circumstances where the path being drawn existed in whole or partly outside of the rendering surface, incorrect bounding could cause out-of-bounds access within the coverage buffer. This affects the higher-level drawing operations, such as Context.fill, Context.stroke, painter.fill, and painter.stroke, when either the .default or .multisample_4x anti-aliasing modes were used. .supersample_4x was not affected, nor was drawing without anti-aliasing. In non-safe optimization modes (consumers compiling with ReleaseFast or ReleaseSmall), this could potentially lead to invalid memory accesses or corruption. z2d v0.7.1 fixes this issue, and it's recommended to upgrade to v0.7.1, or, given the small period of time v0.7.0 has been released, use v0.7.1 immediately, skipping v0.7.0.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 16, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Oct 24, 2026
Fix named in the CVE record. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

OOB drawing with new multi-sample anti-aliasing could lead to invalid memory access and corruption · Advisory · vancluever/z2d · GitHub

https://github.com/vancluever/z2d/security/advisories/GHSA-2vq8-cp8r-vcf3
GitHub pull request

painter: oob drawing fixes

Fix merged in vancluever/z2d PR #137 on 2025-08-15 — awaiting tagged release

https://github.com/vancluever/z2d/pull/137
GitHub commit

commit 93e45d36af53 (vancluever/z2d)

Fix landed in vancluever/z2d commit 93e45d36af53 — awaiting tagged release

https://github.com/vancluever/z2d/commit/93e45d36af53cda0d7f454ed8440713b7ac155b6

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-55286?
CVE-2025-55286 is a high-severity vulnerability; its CVE record was published on August 16, 2025. z2d is a pure Zig 2D graphics library. z2d v0.7.0 released with a new multi-sample anti-aliasing (MSAA) method, which uses a new buffering mechanism for storing coverage data. This differs from the standard alpha mask surface used for the previous super-sample anti-aliasing (SSAA) method. Under…
When was the CVE record for CVE-2025-55286 published?
The CVE record for CVE-2025-55286 was published on August 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-55286 actively exploited?
CVE-2025-55286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-55286?
CVE-2025-55286 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2025-55286?
The CVE record for CVE-2025-55286 names the fix: "z2d v0.7.1 fixes this issue, and it's recommended to upgrade to v0.7.1, or, given the small period of time v0.7.0 has been released, use v0.7.1 immediately, skipping v0.7.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-55286

Explore →

Is Your Infrastructure Affected by CVE-2025-55286?

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

Book a Demo →Browse All CVEs