CVE-2026-35505

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

An unauthenticated remote attacker can repeatedly send crafted connection requests to leak memory. In single-process deployments the memory grows until the service is killed and the port stops responding until restart.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Patch available. Sources: github_release, cisa.
cisa Patch Available

OFFIS DCMTK Toolkit | CISA

https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-181-01
github_release Patch Available

DCMTK-3.7.0

Patch available: DCMTK/dcmtk DCMTK-3.7.0

https://github.com/DCMTK/dcmtk/releases/tag/latest

Vendor Advisories for CVE-2026-35505(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 16× in last 7d / 72× 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-07-27 01:58 UTCEG score recompute
  2. 2026-07-27 01:58 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:50 UTCEG score recompute
  6. 2026-07-26 13:50 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:10 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:24 UTCEPSS rescore
  16. 2026-07-20 17:08 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-17 03:52 UTCGHSA enrichment
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 15:41 UTCGHSA enrichment
  23. 2026-07-16 03:17 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 47 more
  1. 2026-07-15 15:08 UTCGHSA enrichment
  2. 2026-07-15 02:59 UTCGHSA enrichment
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 14:50 UTCGHSA enrichment
  5. 2026-07-14 02:37 UTCGHSA enrichment
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 14:30 UTCGHSA enrichment
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 02:18 UTCGHSA enrichment
  11. 2026-07-12 14:09 UTCGHSA enrichment
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 01:55 UTCGHSA enrichment
  14. 2026-07-11 13:46 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 01:37 UTCGHSA enrichment
  17. 2026-07-10 13:26 UTCGHSA enrichment
  18. 2026-07-10 01:18 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 13:09 UTCGHSA enrichment
  21. 2026-07-09 01:00 UTCGHSA enrichment
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 12:51 UTCGHSA enrichment
  24. 2026-07-08 00:42 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 12:34 UTCGHSA enrichment
  27. 2026-07-07 00:26 UTCGHSA enrichment
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 12:17 UTCGHSA enrichment
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-06 00:08 UTCGHSA enrichment
  34. 2026-07-05 11:59 UTCGHSA enrichment
  35. 2026-07-05 02:30 UTCEPSS rescore
  36. 2026-07-04 23:49 UTCGHSA enrichment
  37. 2026-07-04 11:41 UTCGHSA enrichment
  38. 2026-07-04 06:31 UTCEPSS rescore
  39. 2026-07-03 23:32 UTCGHSA enrichment
  40. 2026-07-03 11:23 UTCGHSA enrichment
  41. 2026-07-02 23:07 UTCGHSA enrichment
  42. 2026-07-02 10:59 UTCGHSA enrichment
  43. 2026-07-01 22:50 UTCGHSA enrichment
  44. 2026-07-01 15:06 UTCEPSS rescore
  45. 2026-07-01 10:41 UTCGHSA enrichment
  46. 2026-06-30 22:33 UTCEG score recompute
  47. 2026-06-30 22:33 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-35505?
CVE-2026-35505 is a high vulnerability published on June 30, 2026. An unauthenticated remote attacker can repeatedly send crafted connection requests to leak memory. In single-process deployments the memory grows until the service is killed and the port stops responding until restart.
When was CVE-2026-35505 disclosed?
CVE-2026-35505 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35505 actively exploited?
CVE-2026-35505 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 65.9% of all scored CVEs.
What is the CVSS score of CVE-2026-35505?
CVE-2026-35505 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-35505?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35505, 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-35505

Explore →

Is Your Infrastructure Affected by CVE-2026-35505?

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