Is CVE-2026-121421 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-121421 being exploited in the wild.

How severe is CVE-2026-121421?

Medium severity, with a CVSS score of 4.3, published 3 November 2026.

Is there a fix for CVE-2026-121421?

Yes: fixed in 3.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-121421 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-121421?

Check whether you run Surrealdb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-121421: SurrealDB server-side request forgery in network deny rules

CVE-2026-121421 · Severity: medium · CVSS 4.3 · Published 2026-11-03

SurrealDB is a database server that enforces network access controls to block connections to internal services. A vulnerability in the network-policy matching logic allows authenticated database users to bypass port-specific deny rules by using alternate names (hostnames or IP addresses) that resolve to the same target, enabling them to reach blocked internal services via HTTP functions.

Technologies: Surrealdb. Vendors: SurrealDB.

Quick answers

Is CVE-2026-121421 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-121421 being exploited in the wild.
How severe is CVE-2026-121421?: Medium severity, with a CVSS score of 4.3, published 3 November 2026.
Which products and versions are affected?: Surrealdb 3.1.0 before 3.3.0.
Is there a fix for CVE-2026-121421?: Yes: fixed in 3.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-121421 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-121421?: Check whether you run Surrealdb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.3.0

Technical details

Port-specific deny rules (HOST:PORT or IP:PORT) match only a literal hostname string, while the resolved-IP check discards the port and compares only IP addresses. This mismatch allows an attacker to reference a denied target using a different name that resolves to the same IP. An authenticated user calling http::* functions can bypass the deny and reach blocked services. The vulnerability affects versions 3.1.0 through 3.2.x; bare IP deny rules without ports remain robust.

Affected products

SurrealDB SurrealDB 3.1.0 before 3.3.0

Timeline

2026-10-19: disclosed
2026-11-03: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.