SurrealDB 2.0.0 before 3.3.1 deny-funcs Capability Bypass via Method-Style Invocations
Only affects SurrealDB 2.0.0 before 3.3.1 configured with --deny-funcs; deployments with no deny rules are not affected. Fixed in 3.3.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.3.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SurrealDB versions from 2.0.0 before 3.3.1 Requires --deny-funcs to be configured; deployments with no deny rules are not affected Method-style invocation on the streaming engine (the default engine in 3.x)
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-121416 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects surrealdb; fixed in 3.3.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SurrealDB 2.0.0 before 3.3.1 does not enforce --deny-funcs restrictions on method-style function calls in the streaming engine, because MethodPart::evaluate invokes resolved functions without a capability check. Authenticated users who can submit queries can run denied functions via method syntax, e.g. [1,2].map() or $f.put()/$f.get() to write and read file bucket data despite file::* denials.
What to do
Check whether your setup matches what the bug needs.
SurrealDB versions from 2.0.0 before 3.3.1 Requires --deny-funcs to be configured; deployments with no deny rules are not affected Method-style invocation on the streaming engine (the default engine in 3.x)Upgrade to a fixed version: 3.3.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- surrealdb surrealdb
From 2.0.0 · fixed in 3.3.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121416
Is CVE-2026-121416 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
SurrealDB's --deny-funcs option is meant to block certain functions an operator has chosen to restrict. A method-style invocation path on the streaming engine skips that check, so denied functions can still run. The verified impact includes reading and writing file bucket data when file::* is denied.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-121416?
surrealdb: from 2.0.0 before 3.3.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 2.0.0 before 3.3.1 are in scope, and the bypass applies only where --deny-funcs is configured. The streaming engine, which is the default in 3.x, is the path involved. To check a setup, look at the SurrealDB version and whether the server was started with --deny-funcs.Source: vulncheck.com, github.com
How do I fix CVE-2026-121416?
Upgrade to SurrealDB 3.3.1 or later, which contains the fix. No workaround is listed in the facts, so the upgrade is the stated remedy.Source: vulncheck.com, github.com