dbcve.org
Coral ServerApplication · Coralos

CVE-2026-30969

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Coral Server prior to 1.1.0 failed to enforce strong authentication within active sessions, allowing attackers who obtained or predicted session identifiers to impersonate agents or join existing sessions. This is a session hijacking vulnerability in the agent-server communication layer.

MitigationUpgrade Coral Server to version 1.1.0 or later to obtain the fixed session authentication mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Coral ServerApplication
Affected:< 1.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Coral Server installation
    Locate the Coral Server installation directory or running process on the system. Common locations include /opt/coral-server, /usr/local/coral-server, or check running processes for coral-server or similar process names.
    Affected if Coral Server is installed and running on the system
  2. Determine installed version
    Run the version check command for Coral Server (typically 'coral-server --version' or check a version file in the installation directory) to obtain the exact version number.
    Affected if The version returned is lower than 1.1.0 (for example, 1.0.x, 0.9.x, etc.)
  3. Verify session handling is active
    Check if the Coral Server is configured to handle agent connections or active sessions. Review server configuration files for session-related settings or examine active network connections on the server port.
    Affected if The server is actively managing agent sessions or accepting client connections
  4. Check for session token exposure
    Inspect server logs, memory, or network traffic for session identifiers (session IDs, tokens, or session keys) that may be visible in plain text or weakly protected.
    Affected if Session identifiers are logged, transmitted unencrypted, or accessible without proper authentication controls

The environment is affected if Coral Server version is below 1.1.0 and the server handles active agent sessions, since the vulnerability allows session hijacking through predictable or obtainable session identifiers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Upgrade Coral Server to version 1.1.0 or later to obtain the fixed session authentication mechanisms.

Recommended fix High confidence

1.1.0

  1. 1. Identify the current Coral Server version currently running (e.g., check with `coral-server --version` or review your deployment configuration)
  2. 2. Create a backup of the Coral Server configuration and any persistent data according to your backup procedures
  3. 3. Upgrade Coral Server to version 1.1.0 using your package manager or deployment method (e.g., `pip install coral-server==1.1.0`, docker pull, or your CI/CD pipeline)
  4. 4. Restart the Coral Server service to load the updated version
  5. 5. Verify the upgrade was successful by checking the version (e.g., `coral-server --version` should return 1.1.0)
  6. 6. Test that agent authentication and session management work correctly to confirm the vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coral Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30969 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data