CVE-2024-6396

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-07-12. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 53%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 53%CVSS: 9.8Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed services: Not assessed

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

A vulnerability in the _backup_run function in aimhubio/aim version 3.19.3 allows remote attackers to overwrite any file on the host server and exfiltrate arbitrary data. The vulnerability arises due to improper handling of the run_hash and repo.path parameters, which can be manipulated to create and write to arbitrary file paths. This can lead to denial of service by overwriting critical system files, loss of private data, and potential remote code execution.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100CISA SSVC

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%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
53%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 12, 2024

Last Modified

July 23, 2025

Advisory Details (1)

Auto-updated Oct 9, 2026
No fix on record yet.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/c1b17afd-4656-47bb-8310-686a9e1b04a0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 127 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2024/CVE-2024-6396.yaml
    First seen Jan 1, 2024

    Aimhubio Aim Server 3.19.3 - Arbitrary File Overwrite

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-6396?
CVE-2024-6396 is a critical vulnerability published on July 12, 2024. A vulnerability in the backuprun function in aimhubio/aim version 3.19.3 allows remote attackers to overwrite any file on the host server and exfiltrate arbitrary data. The vulnerability arises due to improper handling of the run_hash and repo.path parameters, which can be manipulated to create and…
When was CVE-2024-6396 disclosed?
CVE-2024-6396 was first published on July 12, 2024, with the most recent update on July 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-6396 actively exploited?
CVE-2024-6396 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 53% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-6396?
CVE-2024-6396 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-6396?
No fix for CVE-2024-6396 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-6396

Explore →

Is Your Infrastructure Affected by CVE-2024-6396?

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

Book a Demo →Browse All CVEs