GHSA-h5rg-8p7f-47g2
MEDIUMGHSA-h5rg-8p7f-47g2 is a medium-severity (CVSS 4.1) vulnerability in surrealdb. O3 Security confirms whether GHSA-h5rg-8p7f-47g2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SurrealDB: SSRF via JWKS URL — Redirect Following in JWT Key Fetch
Blast Radius
surrealdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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 URLorTYPE 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 — cloud metadata, loopback, internal services — bypassing--allow-net/--deny-net. - Infer the existence and liveness of internal hosts and ports from response-timing differences (bounded by the 1-second fetch timeout).
What it can't do:
- Read the response: the fetch is blind — the body is only parsed as a JWKS, and a non-JWKS response surfaces as an opaque
InvalidAutherror. Nothing is returned to the caller. - Modify data or affect availability (a single GET request).
Patches
The JWKS fetcher now applies a redirect policy that re-validates every redirect target against the configured network capabilities (mirroring check_capabilities_url) and caps redirects at max_http_redirects.
- Versions prior to 3.1.5 are vulnerable.
Workarounds
- Restrict the Owner role to trusted operators.
- Enforce egress filtering at the network layer (block link-local
169.254.0.0/16and internal ranges) so redirect targets are unreachable regardless of in-process checks. - Configure access methods to use only trusted JWKS hosts that do not redirect, or use locally defined keys instead of a remote JWKS.
References
- SurrealDB Documentation — Capabilities
- SurrealQL Documentation — DEFINE ACCESS
fix(iam): prevent SSRF in JWKS fetch by re-validating redirect targets
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | surrealdb | all versions | 3.1.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for surrealdb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update surrealdb to 3.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5rg-8p7f-47g2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h5rg-8p7f-47g2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-h5rg-8p7f-47g2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-h5rg-8p7f-47g2 in your dependencies?
O3 detects GHSA-h5rg-8p7f-47g2 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.