# CVE-2026-92569: Hippo4j through 1.5.0 SSRF via clientAddress Parameter

> Authenticated attackers can exploit unvalidated clientAddress parameters in Hippo4j to trigger SSRF attacks against internal networks and cloud metadata services.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-9vwf-fv6w-mmfr

## What is CVE-2026-92569?

CVE-2026-92569 is a medium-severity server-side request forgery vulnerability in opengoofy hippo4j, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hippo4j through 1.5.0 contains a server-side request forgery vulnerability in four ThreadPoolController endpoints that fail to validate the clientAddress parameter. Authenticated attackers can supply arbitrary hostnames and ports to trigger outbound GET requests to internal networks and cloud metadata services.

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

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


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

No fix has been published for CVE-2026-92569 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92569 is a medium-severity server-side request forgery vulnerability in opengoofy hippo4j, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92569 exists.

Affected product: opengoofy hippo4j. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-92569/ (Markdown: https://insights.sbomify.com/CVE-2026-92569/index.md)
```

## Sources

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

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