How severe is CVE-2025-11060?

CVE-2025-11060 has a CVSS score of 5.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-11060?

CVE-2025-11060 affects the following packages: SurrealDB (crates.io), SurrealDB (crates.io), SurrealDB (crates.io), SurrealDB (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-11060?

Update SurrealDB to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11060 is resolved across your whole dependency graph.

How do I detect CVE-2025-11060 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for SurrealDB, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-11060 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-11060 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-11060 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-11060?

CVE-2025-11060 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-11060?

CVE-2025-11060 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-11060 published, and has it been updated?

CVE-2025-11060 was published on September 26, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

CVE-2025-11060 — SurrealDB

MEDIUMFix: surrealdb/surrealdb@d81169a

CVE-2025-11060 is a medium-severity (CVSS 5.7) CWE-863 vulnerability in SurrealDB. A fix is available for SurrealDB — see the affected versions and patch details below.

Surrealdb: surrealdb is vulnerable to unauthorized data exposure via live query subscriptions

Also known asGHSA-7vm2-j586-vcvc

Published

Sep 26, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-11060.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🦀SurrealDB🦀SurrealDB🦀SurrealDB🦀SurrealDB

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

LIVE SELECT statements are used to capture changes to data within a table in real time. Documents included in WHERE conditions and DELETE notifications were not properly reduced to respect the querying user's security context. Instead the leaked documents reflect the context of the user triggering the notification.

This allows a record or guest user with permissions to run live query subscriptions on a table to observe unauthorised records within the same table, when another user is altering or deleting these records, bypassing access controls.

Impact

A record or guest user with permissions to run live query subscriptions on a table is able to observe unauthorised records within the same table, with unauthorised records returned when deleted, or when records matching the WHERE conditions are created, updated, or deleted, by another user. This impacts confidentiality, limited to the table the attacker has access to, and with the data disclosed dependent of the actions taken by other users.

Patches

A patch has been created for the following versions:

Versions 2.1.9, 2.2.8 and 2.3.8 and later are not affected by this issue.
The first release following v3.0.0-alpha.7 will be patched.

Workarounds

Assess the impact of users with permissions on table records effectively having full read access to the table, use separate tables if required, with impacts to functionality.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`SurrealDB`	≥ 2.3.0&&< 2.3.8	2.3.8`cargo update -p SurrealDB --precise 2.3.8`
🦀crates.io	`SurrealDB`	≥ 2.2.0&&< 2.2.8	2.2.8`cargo update -p SurrealDB --precise 2.2.8`
🦀crates.io	`SurrealDB`	all versions	2.1.9`cargo update -p SurrealDB --precise 2.1.9`
🦀crates.io	`SurrealDB`	≥ 3.0.0-alpha.0&&< 3.0.0-alpha.8	3.0.0-alpha.8`cargo update -p SurrealDB --precise 3.0.0-alpha.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for SurrealDB, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update SurrealDB to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11060 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-11060 (CC BY 4.0)

Frequently Asked Questions

`LIVE SELECT` statements are used to capture changes to data within a table in real time. Documents included in `WHERE` conditions and `DELETE` notifications were not properly reduced to respect the querying user's security context. Instead the leaked documents reflect the context of the user triggering the notification. This allows a record or guest user with permissions to run live query subscriptions on a table to observe unauthorised records within the same table, when another user is altering or deleting these records, bypassing access controls. ### Impact A record or guest user with pe