Coral Server is open collaboration infrastructure that enables communication, coordination, trust and payments for The Internet of Agents. Prior to 1.1.0, Coral Server did not enforce strong authentication between agents and the server within an active session. This could allow an attacker who obtained or predicted a session identifier to impersonate an agent or join an existing session. This vulnerability is fixed in 1.1.0.
CVE-2026-30969
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(low)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 28, 2026Insufficient agent authentication in session communication channels · Advisory · Coral-Protocol/coral-server · GitHub
https://github.com/Coral-Protocol/coral-server/security/advisories/GHSA-ccx7-7wv9-c55xv1.1.0
Patch available: Coral-Protocol/coral-server v1.1.0
https://github.com/Coral-Protocol/coral-server/releases/tag/v1.1.0Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:45 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-30969?
When was CVE-2026-30969 disclosed?
Is CVE-2026-30969 actively exploited?
What is the CVSS score of CVE-2026-30969?
How do I remediate CVE-2026-30969?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-30969
Is Your Infrastructure Affected by CVE-2026-30969?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.