CVE Alert: CVE-2026-121416 – surrealdb

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.

**Risk verdict:** Prioritise remediation wherever untrusted or lower-privileged users can submit queries; KEV, SSVC and EPSS status were not supplied, so exploitation urgency cannot be confirmed.

**Why this matters:** An authenticated attacker may bypass restrictions intended to prevent access to sensitive functions, potentially exposing stored file data or making unauthorised changes. This is most concerning where query access is broadly granted or file buckets contain sensitive records; the supplied impact does not indicate direct service disruption.

**Most likely attack path:** A network-reachable attacker needs valid, low-level query access, but no further preconditions or victim interaction are indicated. They submit method-style calls that evade function restrictions; the stated scope is unchanged, so direct impact on separate systems is not established, though exposed data or credentials could support follow-on activity.

**Who is most exposed:** Internet-facing or partner-accessible database deployments, especially those offering query access to application users or tenants and relying on denied functions to constrain file access.

Review query audit logs for method-style calls to restricted functions.

Correlate query activity with unexpected file-bucket reads or writes.

Alert on unusual access by low-privilege accounts and investigate source, tenant and timing.

Check whether query logging captures the invocation syntax needed to identify bypass attempts.

Mitigation and prioritisation

Upgrade to the vendor-fixed release; prioritise promptly for exposed or multi-tenant deployments.

Until patched, restrict query access and disable or tightly limit affected file capabilities.

Review bucket permissions and audit recent access for unauthorised reads or changes.

Test query behaviour and dependent workloads in staging; coordinate production changes to avoid service disruption.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.