Server-side request forgery in Boruta OAuth request_uri and OpenID jwks_uri fetching

Description

Server-Side Request Forgery vulnerability in malach-it Boruta allows an unauthenticated remote attacker to cause the OAuth/OpenID authorization server to issue outbound HTTP requests to attacker-chosen URIs, including internal services and cloud metadata endpoints. Three code paths fetch remote URIs supplied by the requester without sufficient validation of the target. Boruta.Oauth.Request.Base.fetch_unsigned_request/1 in lib/boruta/oauth/request/base.ex dereferences the OAuth request_uri parameter from the authorization request via Finch.build(:get, request_uri) |> Finch.request(OpenIDHttpClient). Boruta.Openid.parse_registration_params/2 in lib/boruta/openid.ex dereferences the jwks_uri supplied in an OpenID Connect dynamic client registration request. Boruta.Ecto.Clients.refresh_jwk_from_jwks_uri/1 in lib/boruta/adapters/ecto/clients.ex later refreshes the stored jwks_uri for an existing client. In all three paths the only validation is that the URI parses with a scheme (and one of the two request_uri clauses does not even restrict the scheme to http or https). The implementations do not require HTTPS, do not enforce a host or IP allowlist, do not reject loopback, private, link-local, or other non-public ranges after DNS resolution, do not cap response size, and do not constrain redirects. An attacker can therefore steer the server's HTTP client at arbitrary network targets reachable from the Boruta host. This issue affects boruta: from 2.3.2 before 2.3.7.

Timeline

Scores

EPSS (exploitation in 30 days)

0.47% · top 59% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: poc · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Weakness

• CWE-918 Server-Side Request Forgery (SSRF) (opens in a new tab)All about CWE-918 and its CVEs

Affected products

• malach-it · boruta

  • affected 2.3.2 – < 2.3.7

• malach-it · boruta

  • affected 15455b86206e0370eabd64c1856a5c996b436455 – < *

What to do

Workaround: Restrict the network egress of the Boruta host so that the OAuth/OpenID authorization server cannot reach loopback, private, link-local, multicast, or cloud metadata addresses. Where possible, disable application routes for OAuth request_uri dereferencing and OpenID Connect dynamic client registration, or restrict OpenID Connect dynamic client registration to trusted callers, until a patched release is deployed.

References (5)

• https://github.com/malach-it/boruta_auth/security/advisories/GHSA-5q9h-vf5j-fr2g (opens in a new tab)vendor-advisoryrelatedexploit
• https://cna.erlef.org/cves/CVE-2026-54885.html (opens in a new tab)related
• https://osv.dev/vulnerability/EEF-CVE-2026-54885 (opens in a new tab)related
• https://github.com/malach-it/boruta_auth/commit/001e3dc5c259e67c6f907e98867eda4141c96d0d (opens in a new tab)patch
• https://github.com/malach-it/boruta_auth/commit/95fb10b78129355e475681f324c9a01ef0af2be5 (opens in a new tab)patch

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-54885](https://trackcve.app/badge/CVE-2026-54885.svg)](https://trackcve.app/cve/CVE-2026-54885)

Record last updated 31 Jul 2026, 04:20 UTC.