Lucene search
+L

6 matches found

CVE
CVE
added 2026/07/20 12:4 p.m.10 views

CVE-2026-63744

SurrealDB prior to 3.1.5 contains a server-side request forgery in the JWKS fetcher that follows HTTP redirects without re-validating targets against network capabilities. With Owner privileges, an attacker can configure a JWKS URL that redirects to blocked internal addresses, bypassing network a...

5.1CVSS5.4AI score0.00233EPSS
SaveExploits0References2Affected Software1
CVE
CVE
added 2026/07/20 12:4 p.m.11 views

CVE-2026-63736

SurrealDB

5.1CVSS5.4AI score0.00226EPSS
SaveExploits0References2Affected Software1
EUVD
EUVD
added 2026/07/20 12:4 p.m.7 views

EUVD-2026-45907

SurrealDB before 3.2.0 contains a server-side request forgery vulnerability in the JWKS fetcher that validates only the URL hostname string against allow-lists without checking resolved IP addresses. An Owner role attacker can point an access method at an allow-listed hostname resolving to privat...

5.1CVSS5.4AI score0.00226EPSS
SaveExploits0References2
Github Security Blog
Github Security Blog
added 2026/06/19 10:10 p.m.20 views

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

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 checkcapabilitiesurl is applied only to the originally configured URL; redirect targets are not...

6AI score
SaveExploits0References2Affected Software1
CVE
CVE
added 2026/02/25 11:48 p.m.17 views

CVE-2026-27804

Parse Server versions prior to 8.6.3 and 9.1.1-alpha.4 are vulnerable to unauthenticated login via forged Google tokens (alg: none). The root cause is trusting the JWT header for algorithm selection; the fix hardcodes RS256 and shifts key validation to jwks-rsa, rejecting unknown key IDs. Affecte...

9.3CVSS5.5AI score0.00176EPSS
SaveExploits0References5Affected Software1
OSV
OSV
added 2026/02/25 11:0 p.m.8 views

GHSA-4Q3H-VP4R-PRV2 Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter

Impact An unauthenticated attacker can forge a Google authentication token with alg: "none" to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. Patches The fix hardcodes the expected RS256 algorithm...

9.3CVSS5.6AI score0.00176EPSS
SaveExploits0References7
Rows per page
Query Builder