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

Advisory record · `GHSA-h5rg-8p7f-47g2`

- **Identifiers:** `GHSA-h5rg-8p7f-47g2` · `CVE-2026-63744`
- **State:** Confirmed
- **Severity:** CVSS 5.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 19 Jun 2026
- **Updated:** 4 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2026, 22:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `surrealdb` (crates.io): affected `<3.1.5`; fixed in `3.1.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SurrealDB versions before 3.1.5 are vulnerable to server-side request forgery through the JWKS fetch used by JWT and record access methods. An attacker with the Owner role at database level or above can point an access method at an allowlisted host that redirects the request to a blocked internal target, bypassing network capability limits; the response cannot be read. Upgrade to SurrealDB 3.1.5 or later. Until then, restrict the Owner role to trusted operators and use only JWKS hosts that do not redirect, or use locally defined keys.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.1 Medium, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 25th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h5rg-8p7f-47g2)

## Sources

- [GitHub Advisory Database: GHSA-h5rg-8p7f-47g2](https://github.com/advisories/GHSA-h5rg-8p7f-47g2)
- [OSV: GHSA-h5rg-8p7f-47g2](https://osv.dev/vulnerability/GHSA-h5rg-8p7f-47g2)
- <https://github.com/surrealdb/surrealdb/security/advisories/GHSA-h5rg-8p7f-47g2>
- <https://github.com/surrealdb/surrealdb>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h5rg-8p7f-47g2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h5rg-8p7f-47g2/>. Everything for agents: <https://agentprime.io/llms.txt>.