SurrealDB: SSRF via JWKS URL — Redirect Following in JWT Key Fetch

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-63744: 0.32% estimated exploitation activity in the next 30 days; percentile 25.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

SurrealDB fetches the JWKS document for a JWT or record access method using a bare `reqwest` client that follows HTTP redirects by default. The network capability check in `core/src/iam/jwks.rs` (`check_capabilities_url`) is applied only to the originally configured URL; redirect targets are not re-validated. An `--allow-net`-permitted JWKS host that returns a `3xx Location` can therefore redirect the request to an address the allowlist was meant to block, resulting in a server-side request forgery (SSRF). The protected `HttpClient` used by `http::*` functions re-checks every redirect hop and was hardened in 3.1.0, but the JWKS fetcher uses its own client and was not covered.

Impact What an attacker can do: - With the Owner role at database level or above (the minimum required to run `DEFINE ACCESS ... TYPE JWT URL` or `TYPE RECORD ... WITH JWT URL`), point an access method at an allowlisted host they control and redirect the server's GET to an otherwise-blocked target —…

Published by the source

19 Jun 2026, 22:10 UTC

Last modified by the source

4 Nov 2026, 02:56 UTC

Source last checked

4 Nov 2026, 06:30 UTC

1. Revision 2 · amended · 4 Nov 2026

   Amended from osv record GHSA-h5rg-8p7f-47g2

2. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h5rg-8p7f-47g2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63744

Advisory: SurrealDB: SSRF via JWKS URL — Redirect Following in JWT Key Fetch
IDs: CVE-2026-63744, GHSA-h5rg-8p7f-47g2
Record: https://patchnext.com/advisories/ghsa-h5rg-8p7f-47g2 (revision 2, source checked 4 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: surrealdb 3.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io surrealdb: affected < 3.1.5; fixed in 3.1.5

## Suggested inspection (read-only)
- crates.io surrealdb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on surrealdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h5rg-8p7f-47g2 (GitHub-reviewed advisory GHSA-h5rg-8p7f-47g2 lists affected ranges: crates.io surrealdb >=0 <3.1.5)
- Verified: https://osv.dev/vulnerability/GHSA-h5rg-8p7f-47g2 (OSV record GHSA-h5rg-8p7f-47g2 lists affected ranges: crates.io surrealdb >=0 <3.1.5 (fixed))

Commands are suggestions: review each one before running it.