What is the CVSS score of CVE-2026-30970?

CVE-2026-30970 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2026-30970?

Within 24 hours: Immediately restrict network access to /api/v1/sessions endpoint to trusted sources only and enable request rate limiting. Within 7 days: Implement Web Application Firewall rules to block unauthenticated session creation requests and monitor for exploitation attempts. Within 30 days: Evaluate migration timeline to Coral Server 1.1.0 or later once patches become available, and consider alternative collaboration platforms if patch availability remains uncertain.

Coral Server CVE-2026-30970

CRITICAL

Missing Authorization (CWE-862)

2026-03-10 security-advisories@github.com

Authentication Bypass AI / ML Coral Server Coralos

9.1

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send POST request to /api/v1/sessions endpoint
Delivery

Create multiple agent sessions without authentication
Exploit

Spawn resource-intensive containers
Execution

Exhaust system memory and CPU
Impact

Cause denial of service

Vulnerability Assessment

Weakness	CWE CWE-862 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Authorization checks on every request MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Coral Server versions prior to 1.1.0 with /api/v1/sessions endpoint accessible over network. No authentication required; vulnerable to unauthenticated remote attackers with network access to the endpoint.
Impact	CVSS 9.1.
Exploit ScenarioDerived	Unauthorized access.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Coral Server has a third missing authorization flaw.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 9.1

Third Coral Server auth flaw.

RemediationAI

Apply patches.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-862.

Know when Coral Server gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.1 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

DescriptionGitHub Advisory

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 allowed the creation of agent sessions through the /api/v1/sessions endpoint without strong authentication. This endpoint performs resource-intensive initialization operations including container spawning and memory context creation. An attacker capable of accessing the endpoint could create sessions or consume system resources without proper authorization. This vulnerability is fixed in 1.1.0.

Executive ViewAI

Why It Matters

Coral Server instances are vulnerable to unauthenticated resource exhaustion attacks that could render infrastructure unavailable without a vendor patch. Attackers can repeatedly spawn resource-intensive agent sessions, potentially disrupting service availability and increasing infrastructure costs for affected organizations.

Business Impact: High

Compensating Controls

Implement network segmentation to restrict access to /api/v1/sessions endpoint; deploy WAF rules requiring authentication headers and rate limiting per IP; disable the sessions endpoint if not operationally critical; monitor resource consumption metrics for anomalous session creation patterns; implement API gateway authentication requirements before endpoint exposure.

Threat Intelligence Overview

EPSS Score

0.1%

Top 76% exploitable

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.1%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.