CVE-2026-56260

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-12. The CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 12, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
Web page

Crawl4AI - Arbitrary File Write via output_path Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-arbitrary-file-write-via-output-path-parameter
Web page

GitHub - unclecode/crawl4ai: 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & Scraper. Don't be shy, join here: https://discord.gg/jP8KfhDhyN · GitHub

https://github.com/unclecode/crawl4ai
GitHub advisoryMentions a patch (unverified)

Multiple Docker API Vulnerabilities - File Write, SSRF, Auth Bypass, XSS, JS Execution · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-365w-hqf6-vxfg

Vendor Advisories for CVE-2026-56260(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
crawl4ai0.3.0 ... 0.8.6 (64 versions)
  • every version up to 0.8.7: fixed in 0.8.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 48× 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 100 of 385 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. None are among the latest 100 rows. The 285 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56260?
CVE-2026-56260 is a critical-severity vulnerability; its CVE record was published on July 12, 2026. Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location…
When was CVE-2026-56260 made public?
CVE-2026-56260 was made public on June 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 12, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-56260 actively exploited?
CVE-2026-56260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56260?
CVE-2026-56260 has a CVSS base score of 9.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-56260?
A fix for CVE-2026-56260 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56260 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56260

Explore →

Is Your Infrastructure Affected by CVE-2026-56260?

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

Book a Demo →Browse All CVEs