CVE-2026-75856

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th 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
Elevated
8.6EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.6HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.5%
EPSS %ILE
40th
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 public PoC (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

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github.
Web page

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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
codewhale-tui—
  • 0.8.41 up to 0.8.64: fixed in 0.8.64
—
deepseek-tui—
  • 0.8.5 through 0.8.41: no fix on record
—
npm(2)
PackageVulnerable rangeFix by version rangeDependents
codewhale—
  • 0.8.41 up to 0.8.64: fixed in 0.8.64
—
deepseek-tui—
  • 0.8.5 up to 0.8.41: fixed in 0.8.41
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 53× 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 98 of 102 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-75856?
CVE-2026-75856 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-75856 was made public on July 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 August 18, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-75856 actively exploited?
CVE-2026-75856 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75856?
CVE-2026-75856 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75856?
A fix for CVE-2026-75856 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75856 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-75856

Explore →

Is Your Infrastructure Affected by CVE-2026-75856?

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

Book a Demo →Browse All CVEs