CVE-2025-55013

MEDIUMNVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.2 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 4.2Exploit: NoneExposed: 0

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

The Assemblyline 4 Service Client interfaces with the API to fetch tasks and publish the result for a service in Assemblyline 4. In versions below 4.6.1.dev138, the Assemblyline 4 Service Client (task_handler.py) accepts a SHA-256 value returned by the service server and uses it directly as a local file name.A malicious or compromised server (or any MITM that can speak to client) can return a path-traversal payload such as ../../../etc/cron.d/evil and force the client to write the downloaded bytes to an arbitrary location on disk. This is fixed in version 4.6.1.dev138.

CVSS v3
4.2
EG Score
4.2(medium)
EPSS
42.3%
KEV
Not listed

Published

August 9, 2025

Last Modified

April 15, 2026

References (2)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
assemblyline-service-client4.6.1.dev0 ... 4.6.1.dev99 (115 versions)4.6.1.dev138—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 44× 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 104 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-55013?
CVE-2025-55013 is a medium vulnerability published on August 9, 2025. The Assemblyline 4 Service Client interfaces with the API to fetch tasks and publish the result for a service in Assemblyline 4. In versions below 4.6.1.dev138, the Assemblyline 4 Service Client (task_handler.py) accepts a SHA-256 value returned by the service server and uses it directly as a local…
When was CVE-2025-55013 disclosed?
CVE-2025-55013 was first published in the National Vulnerability Database on August 9, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-55013 actively exploited?
CVE-2025-55013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-55013?
CVE-2025-55013 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2025-55013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-55013, 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-2025-55013

Explore →

Is Your Infrastructure Affected by CVE-2025-55013?

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

Start Free Scan →Browse All CVEs