CVE-2026-56258

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-23. The CNA's CVSS baseline 8.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
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Crawl4AI before 0.8.8 contains an arbitrary file write vulnerability in the screenshot and PDF endpoints that allows unauthenticated attackers to write files outside the intended directory via symlink and time-of-check-time-of-use (TOCTOU) attacks on the output_path parameter. Remote attackers can exploit insufficient path validation and symlink following to achieve arbitrary file write and potential code execution on systems where the runtime user has write access to executable or cron locations.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

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

June 23, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
Web page

Crawl4AI - Arbitrary File Write via output_path Symlink and TOCTOU | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-arbitrary-file-write-via-output-path-symlink-and-toctou
GitHub advisoryMentions a patch (unverified)

Arbitrary file write (symlink/TOCTOU) plus log and webhook-header injection in Docker server · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-7cx2-g3h9-382p

Vendor Advisories for CVE-2026-56258(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.7 (65 versions)
  • every version up to 0.8.8: fixed in 0.8.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 35× 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 268 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 168 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56258?
CVE-2026-56258 is a high-severity vulnerability; its CVE record was published on June 23, 2026. Crawl4AI before 0.8.8 contains an arbitrary file write vulnerability in the screenshot and PDF endpoints that allows unauthenticated attackers to write files outside the intended directory via symlink and time-of-check-time-of-use (TOCTOU) attacks on the output_path parameter. Remote attackers can…
When was CVE-2026-56258 made public?
CVE-2026-56258 was made public on June 4, 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 June 23, 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-56258 actively exploited?
CVE-2026-56258 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56258?
CVE-2026-56258 has a CVSS base score of 8.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-56258?
A fix for CVE-2026-56258 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56258 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-56258

Explore →

Is Your Infrastructure Affected by CVE-2026-56258?

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

Book a Demo →Browse All CVEs