CVE-2019-25360

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2026-02-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

Aida64 Engineer 6.10.5200 contains a buffer overflow vulnerability in the CSV logging configuration that allows attackers to execute malicious code by crafting a specially designed payload. Attackers can exploit the vulnerability by creating a malformed log file with carefully constructed SEH (Structured Exception Handler) overwrite techniques to achieve remote code execution.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Aida64 6.10.5200 - Buffer Overflow (SEH) - Windows local Exploit

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

Download | AIDA64

https://www.aida64.com/downloads/OTAwMmVmNTE=
generic

AIDA64

https://www.aida64.com

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2019-25360?
CVE-2019-25360 is a critical vulnerability published on February 18, 2026. Aida64 Engineer 6.10.5200 contains a buffer overflow vulnerability in the CSV logging configuration that allows attackers to execute malicious code by crafting a specially designed payload. Attackers can exploit the vulnerability by creating a malformed log file with carefully constructed SEH…
When was CVE-2019-25360 disclosed?
CVE-2019-25360 was first published in the National Vulnerability Database on February 18, 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-2019-25360 actively exploited?
CVE-2019-25360 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.5% of all scored CVEs.
What is the CVSS score of CVE-2019-25360?
CVE-2019-25360 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-25360?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25360, 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-2019-25360

Explore →

Is Your Infrastructure Affected by CVE-2019-25360?

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

Start Free Scan →Browse All CVEs