CVE-2026-56651

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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, secondary
Trending — 3 sources updated this week
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: None knownExposed: 0

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

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.0(medium)
EG Risk
14(Track)
EG Risk 14/100SSVC: Track

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
Severity20% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

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 9× in last 7d / 37× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:46 UTCEG score recompute
  3. 2026-09-18 04:46 UTCGHSA enrichment
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 06:20 UTCEG score recompute
  8. 2026-09-15 06:20 UTCGHSA enrichment
  9. 2026-09-15 03:11 UTCEPSS rescore
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 07:54 UTCEG score recompute
  12. 2026-09-12 07:54 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-09 09:28 UTCEG score recompute
  16. 2026-09-09 09:28 UTCGHSA enrichment
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-06 11:03 UTCEG score recompute
  21. 2026-09-06 11:02 UTCGHSA enrichment
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-03 12:37 UTCEG score recompute
  24. 2026-09-03 12:37 UTCGHSA enrichment
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 12 more
  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-31 14:11 UTCEG score recompute
  4. 2026-08-31 14:11 UTCGHSA enrichment
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 15:45 UTCGHSA enrichment
  9. 2026-08-27 20:28 UTCGHSA enrichment
  10. 2026-08-27 17:27 UTCEG score recompute
  11. 2026-08-27 16:49 UTCEG score recompute
  12. 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 vulnerability 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 CVE-2026-56651 disclosed?
CVE-2026-56651 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56651 actively exploited?
CVE-2026-56651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-56651?
CVE-2026-56651 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-56651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56651, 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

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.

Start Free Scan →Browse All CVEs