# CVE-2026-121422: SurrealDB from 3.1.0 before 3.3.0 SSRF via JWKS Implicit Default Port Bypass


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-7wm7-v445-mpw3, GHSA-h3mp-7wcg-p6vj

## What is CVE-2026-121422?

CVE-2026-121422 is a medium-severity vulnerability in surrealdb, published on 3 Nov 2026. 

### Official description

SurrealDB from 3.1.0 before 3.3.0 contains a server-side request forgery vulnerability that allows database Owners to bypass port-specific deny-net rules by using JWKS URLs with implicit default ports. Attackers can configure a JWT or record access method whose JWKS URL omits port 80 or 443, causing blind GET requests to explicitly denied internal services.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-121422?

1 open source package ship an affected version, including surrealdb.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `surrealdb` | crates.io | `pkg:cargo/surrealdb` | From 3.1.0 | 3.3.0 |

## How do I fix CVE-2026-121422?

Upgrade surrealdb to 3.3.0 or later.

## Is CVE-2026-121422 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121422 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121422 and fix it if it is affected.

What it is: CVE-2026-121422 is a medium-severity vulnerability in surrealdb, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121422 exists.

Affected packages and fixed versions:
- surrealdb (crates.io): affected from 3.1.0; fixed in 3.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121422/ (Markdown: https://insights.sbomify.com/CVE-2026-121422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121422
- OSV: https://osv.dev/vulnerability/CVE-2026-121422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121422/
Summaries are generated and may contain mistakes; the official description above is the record.
