CVE-2026-75856

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% 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
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

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

CodeWhale before 0.8.64 contains a server-side request forgery bypass vulnerability in DNS pinning logic that fails to prevent time-of-check-time-of-use attacks. Attackers can manipulate DNS responses to fail initial resolution checks and succeed on secondary requests, allowing requests to internal IP addresses and bypassing SSRF mitigations.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

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
Severity86% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

CodeWhale before 0.8.64 SSRF Bypass via DNS Pinning TOCTOU | Advisories | VulnCheck

https://www.vulncheck.com/advisories/codewhale-before-ssrf-bypass-via-dns-pinning-toctou
github_commit

commit 26de44a8bd50 (Hmbown/CodeWhale)

Fix landed in Hmbown/CodeWhale commit 26de44a8bd50 — awaiting tagged release

https://github.com/Hmbown/CodeWhale/commit/26de44a8bd5051f8f944ea60b2c37ae1d2b7d25e
github Patch Available🟡 PoC Available

SSRF‌ bypass - TOCTOU on DNS failure for DNS pinning · Advisory · Hmbown/CodeWhale · GitHub

https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-6v2g-fpxh-pmmh

Vendor Advisories for CVE-2026-75856(1)

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

Affected Packages

(4 across 2 ecosystems)
crates.io(2)
PackageVulnerable rangeFixed inDependents
codewhale-tui—0.8.64—
deepseek-tui———
npm(2)
PackageVulnerable rangeFixed inDependents
codewhale—0.8.64—
deepseek-tui—0.8.41—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 53× 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 23:53 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:15 UTCEG score recompute
  4. 2026-09-16 23:32 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 11:46 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 11:53 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 00:11 UTCEG score recompute
  11. 2026-09-13 00:38 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-12 01:01 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 13:14 UTCEG score recompute
  16. 2026-09-10 12:54 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 08:40 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:23 UTCEG score recompute
  21. 2026-09-06 16:44 UTCEG score recompute
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-05 17:11 UTCEG score recompute
  24. 2026-09-04 17:33 UTCEG score recompute
  25. 2026-09-04 05:46 UTCEG score recompute
Show 35 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 16:50 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 14:36 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-31 03:09 UTCEG score recompute
  9. 2026-08-30 19:18 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 03:34 UTCEG score recompute
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 03:58 UTCEG score recompute
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-27 19:24 UTCEG score recompute
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 18:13 UTCEG score recompute
  18. 2026-08-26 14:47 UTCEPSS rescore
  19. 2026-08-25 17:17 UTCEG score recompute
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 17:43 UTCEG score recompute
  22. 2026-08-24 14:18 UTCEPSS rescore
  23. 2026-08-23 06:21 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 06:49 UTCEG score recompute
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-21 07:16 UTCEG score recompute
  28. 2026-08-20 22:56 UTCEPSS rescore
  29. 2026-08-19 19:56 UTCEG score recompute
  30. 2026-08-19 17:04 UTCEPSS rescore
  31. 2026-08-18 20:23 UTCEG score recompute
  32. 2026-08-18 19:20 UTCEG score recompute
  33. 2026-08-18 16:33 UTCEG score recompute
  34. 2026-08-18 15:30 UTCEG score recompute
  35. 2026-08-18 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-75856?
CVE-2026-75856 is a high vulnerability published on August 18, 2026. CodeWhale before 0.8.64 contains a server-side request forgery bypass vulnerability in DNS pinning logic that fails to prevent time-of-check-time-of-use attacks. Attackers can manipulate DNS responses to fail initial resolution checks and succeed on secondary requests, allowing requests to internal…
When was CVE-2026-75856 disclosed?
CVE-2026-75856 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75856 actively exploited?
CVE-2026-75856 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 60.8% of all scored CVEs.
What is the CVSS score of CVE-2026-75856?
CVE-2026-75856 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-75856?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75856, 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-2026-75856

Explore →

Is Your Infrastructure Affected by CVE-2026-75856?

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

Start Free Scan →Browse All CVEs