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

CVE-2026-30969 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:H/I:H/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-30969?

Within 24 hours: Identify all systems running Internet of Agents versions 1.1.0 or earlier and isolate them from production payment/transaction systems; notify affected stakeholders. Within 7 days: Implement compensating controls including strict key validation, enhanced logging/monitoring, and network segmentation; conduct audit of recent transactions for unauthorized access. Within 30 days: Contact vendor for patch timeline; evaluate alternative solutions; perform forensic analysis if compromise is suspected.

Coral Server CVE-2026-30969

CRITICAL

Authorization Bypass Through User-Controlled Key (CWE-639)

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

Obtain or predict valid session identifier
Exploit

Send authenticated request with session ID
Execution

Impersonate agent in active session
Impact

Access confidential agent communications

Vulnerability Assessment

Weakness	CWE CWE-639 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions	Coral Server versions prior to 1.1.0 with weak session authentication enabled. Attacker needs network access to session endpoint and ability to predict or intercept session identifiers. No authentication credentials required for exploitation.
Impact	CVSS 9.1.
Exploit ScenarioDerived	Cross-user data access.

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

No patch listed yet 0.0% 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 an IDOR vulnerability enabling cross-user data access.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 9.1

IDOR in Coral Server.

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-639.

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:H/I:H/A:N

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

High

Integrity

High

Availability

None

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 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.

Executive ViewAI

Why It Matters

A critical authorization bypass vulnerability in Internet of Agents (versions ≤1.1.0) allows attackers to manipulate user-controlled keys to bypass payment and trust controls, potentially enabling unauthorized transactions and fraudulent activities. Organizations using affected versions face immediate risk of financial loss, data theft, and reputational damage until mitigation measures are implemented.

Business Impact: Severe

Compensating Controls

Implement strict input validation and cryptographic key verification mechanisms; deploy WAF rules to detect and block suspicious key manipulation attempts; segment payment systems from affected application instances; enable comprehensive audit logging for all authentication and authorization events; restrict API access through IP whitelisting and API gateway controls; disable user-initiated key modification features until patch is available; implement additional transaction authorization requirements (e.g., multi-factor approval for payments above threshold).

Threat Intelligence Overview

EPSS Score

0.0%

Top 85% 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.0%

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.