CVE-2026-56651

LOWPre-NVD 2.02.0
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
2.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.0Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Dool in versions up to 1.3.8 is vulnerable to symlink following when the "--devel" flag is used, as the application opens a log file without the "O_NOFOLLOW" flag. A local attacker can exploit this by creating a symlink at the expected log file path pointing to a sensitive file, causing dool to truncate and overwrite the target file with log data, which is especially impactful if dool is run with elevated privileges. The issue was addressed by pull request #116

CVSS v3
2.0
EG Score
2.0LOWmedium confidence
EG Risk
9
EG Risk 9/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)
Severity20% × 45%
The EG Score, 2.0 of 10.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

August 27, 2026

Last Modified

August 28, 2026

References (2)

Vendor Advisories for CVE-2026-56651(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× 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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-12 15:54 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-09 03:08 UTCEG score recompute
  11. 2026-10-09 03:08 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-06 01:56 UTCEG score recompute
  16. 2026-10-06 01:56 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-03 03:30 UTCEG score recompute
  21. 2026-10-03 03:30 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-30 05:04 UTCEG score recompute
Show 51 more
  1. 2026-09-30 05:04 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  2. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-09-27 00:05 UTCEG score recompute
  6. 2026-09-27 00:05 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-09-24 01:38 UTCEG score recompute
  10. 2026-09-24 01:38 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  11. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-09-21 03:13 UTCEG score recompute
  13. 2026-09-21 03:12 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-09-18 04:46 UTCEG score recompute
  17. 2026-09-18 04:46 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  18. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-15 06:20 UTCEG score recompute
  22. 2026-09-15 06:20 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  23. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-12 07:54 UTCEG score recompute
  26. 2026-09-12 07:54 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-09-09 09:28 UTCEG score recompute
  30. 2026-09-09 09:28 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-06 11:03 UTCEG score recompute
  35. 2026-09-06 11:02 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  36. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-03 12:37 UTCEG score recompute
  38. 2026-09-03 12:37 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  39. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-08-31 14:11 UTCEG score recompute
  43. 2026-08-31 14:11 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  44. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  47. 2026-08-28 15:45 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  48. 2026-08-27 20:28 UTCGHSA enrichmentGHSA-q9x7-4mx4-prwq · GitHub severity LOW
  49. 2026-08-27 17:27 UTCEG score recompute
  50. 2026-08-27 16:49 UTCEG score recomputeFirst assessed: 2.0 LOW
  51. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56651?
CVE-2026-56651 is a low-severity vulnerability; its CVE record was published on August 27, 2026. Dool in versions up to 1.3.8 is vulnerable to symlink following when the "--devel" flag is used, as the application opens a log file without the "O_NOFOLLOW" flag. A local attacker can exploit this by creating a symlink at the expected log file path pointing to a sensitive file, causing dool to…
When was the CVE record for CVE-2026-56651 published?
The CVE record for CVE-2026-56651 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-56651 actively exploited?
CVE-2026-56651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56651?
CVE-2026-56651 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56651?
A fix for CVE-2026-56651 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-56651 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56651

Explore →

Is Your Infrastructure Affected by CVE-2026-56651?

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

Book a Demo →Browse All CVEs