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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-11060 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
SurrealDB🦀SurrealDB🦀SurrealDB🦀SurrealDBReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | SurrealDB | ≥ 2.3.0&&< 2.3.8 | 2.3.8cargo update -p SurrealDB --precise 2.3.8 |
| 🦀crates.io | SurrealDB | ≥ 2.2.0&&< 2.2.8 | 2.2.8cargo update -p SurrealDB --precise 2.2.8 |
| 🦀crates.io | SurrealDB | all versions | 2.1.9cargo update -p SurrealDB --precise 2.1.9 |
| 🦀crates.io | SurrealDB | ≥ 3.0.0-alpha.0&&< 3.0.0-alpha.8 | 3.0.0-alpha.8cargo update -p SurrealDB --precise 3.0.0-alpha.8 |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-11060 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-11060. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-11060 in your dependencies?
O3 Security finds CVE-2025-11060 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.