# CVE-2026-54885: Server-side request forgery in Boruta OAuth request_uri and OpenID jwks_uri fetching

> Unauthenticated attackers can force the Boruta OAuth server to make arbitrary HTTP requests, potentially accessing internal services or cloud metadata.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** EEF-CVE-2026-54885, GHSA-5q9h-vf5j-fr2g

## What is CVE-2026-54885?

CVE-2026-54885 is a medium-severity server-side request forgery vulnerability in malach-it boruta, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-54885?

1 open source package ship an affected version, including boruta.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `boruta` | Hex | From 2.3.2 | 2.3.7 |

## How do I fix CVE-2026-54885?

Upgrade boruta to 2.3.7 or later.

## Is CVE-2026-54885 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54885 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54885 and fix it if it is affected.

What it is: CVE-2026-54885 is a medium-severity server-side request forgery vulnerability in malach-it boruta, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54885 exists.

Affected packages and fixed versions:
- boruta (Hex): affected from 2.3.2; fixed in 2.3.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54885/ (Markdown: https://insights.sbomify.com/CVE-2026-54885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54885
- OSV: https://osv.dev/vulnerability/CVE-2026-54885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54885/
Summaries are generated and may contain mistakes; the official description above is the record.