CVE-2018-25216

MEDIUMNVD 5.56.2▲
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2026-03-26. NVD baseline CVSS 5.5; sources differ by 0.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

AnyBurn 4.3 contains a local buffer overflow vulnerability that allows local attackers to crash the application by supplying an excessively long string in the image file name field. Attackers can paste a 10000-byte payload into the 'Image file name' parameter during the 'Copy disk to Image' operation to trigger a denial of service condition.

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

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

AnyBurn 4.3 Denial of Service Local Buffer Overflow | Advisories | VulnCheck

https://www.vulncheck.com/advisories/anyburn-denial-of-service-local-buffer-overflow
generic🟡 PoC Available

AnyBurn 4.3 - Local Buffer Overflow (PoC) - Windows dos Exploit

https://www.exploit-db.com/exploits/46002
generic

The Official AnyBurn Website

http://www.anyburn.com/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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 15:36 UTCEPSS rescore
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-17 19:22 UTCEPSS rescore
  4. 2026-09-16 05:06 UTCEPSS rescore
  5. 2026-09-15 03:05 UTCEPSS rescore
  6. 2026-09-13 16:42 UTCEPSS rescore
  7. 2026-09-12 14:56 UTCEPSS rescore
  8. 2026-09-11 14:47 UTCEPSS rescore
  9. 2026-09-11 09:32 UTCEPSS rescore
  10. 2026-09-07 15:57 UTCEPSS rescore
  11. 2026-09-06 13:43 UTCEPSS rescore
  12. 2026-09-05 15:24 UTCEPSS rescore
  13. 2026-09-04 13:56 UTCEPSS rescore
  14. 2026-09-04 05:02 UTCEPSS rescore
  15. 2026-09-02 14:07 UTCEPSS rescore
  16. 2026-09-01 13:49 UTCEPSS rescore
  17. 2026-09-01 03:32 UTCEPSS rescore
  18. 2026-08-28 21:36 UTCEPSS rescore
  19. 2026-08-27 14:21 UTCEPSS rescore
  20. 2026-08-26 14:42 UTCEPSS rescore
  21. 2026-08-25 13:44 UTCEPSS rescore
  22. 2026-08-21 23:45 UTCEPSS rescore
  23. 2026-08-20 22:51 UTCEPSS rescore
  24. 2026-08-19 17:00 UTCEPSS rescore
  25. 2026-08-18 13:44 UTCEPSS rescore
Show 39 more
  1. 2026-08-17 13:43 UTCEPSS rescore
  2. 2026-08-16 14:51 UTCEPSS rescore
  3. 2026-08-16 10:09 UTCEG score recompute
  4. 2026-08-16 10:09 UTCGHSA enrichment
  5. 2026-08-16 02:10 UTCEPSS rescore
  6. 2026-08-15 01:26 UTCEPSS rescore
  7. 2026-08-14 06:27 UTCEG score recompute
  8. 2026-08-14 06:27 UTCGHSA enrichment
  9. 2026-08-13 21:56 UTCEPSS rescore
  10. 2026-08-12 20:44 UTCEG score recompute
  11. 2026-08-12 20:44 UTCGHSA enrichment
  12. 2026-08-12 13:46 UTCEPSS rescore
  13. 2026-08-11 05:18 UTCEG score recompute
  14. 2026-08-11 05:18 UTCGHSA enrichment
  15. 2026-08-10 05:39 UTCEG score recompute
  16. 2026-08-10 05:39 UTCGHSA enrichment
  17. 2026-08-09 13:43 UTCEPSS rescore
  18. 2026-08-09 06:00 UTCEG score recompute
  19. 2026-08-09 06:00 UTCGHSA enrichment
  20. 2026-08-08 16:32 UTCEPSS rescore
  21. 2026-08-07 16:25 UTCEG score recompute
  22. 2026-08-07 16:25 UTCGHSA enrichment
  23. 2026-08-07 16:23 UTCEPSS rescore
  24. 2026-08-06 13:42 UTCEPSS rescore
  25. 2026-08-06 00:53 UTCEG score recompute
  26. 2026-08-06 00:53 UTCGHSA enrichment
  27. 2026-08-05 19:13 UTCEPSS rescore
  28. 2026-08-04 15:05 UTCEPSS rescore
  29. 2026-08-03 23:18 UTCEG score recompute
  30. 2026-08-03 23:18 UTCGHSA enrichment
  31. 2026-08-02 15:24 UTCEG score recompute
  32. 2026-08-02 15:24 UTCGHSA enrichment
  33. 2026-08-02 02:23 UTCEPSS rescore
  34. 2026-08-01 04:12 UTCEPSS rescore
  35. 2026-07-30 16:24 UTCEPSS rescore
  36. 2026-07-30 01:27 UTCEPSS rescore
  37. 2026-07-28 15:32 UTCEPSS rescore
  38. 2026-07-27 14:23 UTCEG score recompute
  39. 2026-07-27 14:23 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-25216?
CVE-2018-25216 is a medium vulnerability published on March 26, 2026. AnyBurn 4.3 contains a local buffer overflow vulnerability that allows local attackers to crash the application by supplying an excessively long string in the image file name field. Attackers can paste a 10000-byte payload into the 'Image file name' parameter during the 'Copy disk to Image'…
When was CVE-2018-25216 disclosed?
CVE-2018-25216 was first published in the National Vulnerability Database on March 26, 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-2018-25216 actively exploited?
CVE-2018-25216 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-2018-25216?
CVE-2018-25216 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.2.
How do I remediate CVE-2018-25216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-25216, 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

Explore the affected products and dependency analysis for CVE-2018-25216

Explore →

Is Your Infrastructure Affected by CVE-2018-25216?

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

Start Free Scan →Browse All CVEs