CVE-2026-75329

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

The Netty configuration distribution service (port 8283) of super-diamond-server <= 1.3.3 has no authentication mechanism. Attackers can directly obtain the full configuration of any project (including database passwords, API keys, etc.) by sending a TCP request without any credential.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

CVE/super-diamond/NETTY-NOAUTH.md at main · fangtang7/CVE · GitHub

https://github.com/fangtang7/CVE/blob/main/super-diamond/NETTY-NOAUTH.md

Vendor Advisories for CVE-2026-75329(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 28× in last 7d / 28× 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-08-30 04:10 UTCEG score recompute
  2. 2026-08-30 04:10 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-30 00:12 UTCGHSA enrichment
  5. 2026-08-29 20:14 UTCGHSA enrichment
  6. 2026-08-29 16:13 UTCGHSA enrichment
  7. 2026-08-29 12:09 UTCGHSA enrichment
  8. 2026-08-29 07:58 UTCGHSA enrichment
  9. 2026-08-29 03:57 UTCGHSA enrichment
  10. 2026-08-28 23:59 UTCEG score recompute
  11. 2026-08-28 23:59 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-28 17:45 UTCGHSA enrichment
  14. 2026-08-28 13:38 UTCGHSA enrichment
  15. 2026-08-28 09:36 UTCGHSA enrichment
  16. 2026-08-28 05:32 UTCGHSA enrichment
  17. 2026-08-28 01:26 UTCGHSA enrichment
  18. 2026-08-27 21:29 UTCEG score recompute
  19. 2026-08-27 21:29 UTCGHSA enrichment
  20. 2026-08-27 17:32 UTCEG score recompute
  21. 2026-08-27 17:31 UTCGHSA enrichment
  22. 2026-08-27 16:53 UTCEG score recompute▲ 9.80
  23. 2026-08-27 16:52 UTCGHSA enrichment
  24. 2026-08-27 16:43 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 3 more
  1. 2026-08-26 22:24 UTCNVD update
  2. 2026-08-26 22:03 UTCEG score recompute
  3. 2026-08-26 22:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75329?
CVE-2026-75329 is a critical vulnerability published on August 26, 2026. The Netty configuration distribution service (port 8283) of super-diamond-server <= 1.3.3 has no authentication mechanism. Attackers can directly obtain the full configuration of any project (including database passwords, API keys, etc.) by sending a TCP request without any credential.
When was CVE-2026-75329 disclosed?
CVE-2026-75329 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75329 actively exploited?
CVE-2026-75329 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 75.0% of all scored CVEs.
What is the CVSS score of CVE-2026-75329?
CVE-2026-75329 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-75329?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75329, 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-75329

Explore →

Is Your Infrastructure Affected by CVE-2026-75329?

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

Start Free Scan →Browse All CVEs