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

Published Sep 16, 2026
·
Updated

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.

Affected Software

1 affected component
Hippo4j Hippo4j<=1.5.0

Event History

Sep 16, 2026
CVE Published
via MITRE·02:40 PM
Data Sourced
via MITRE·02:40 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs authenticated access to the affected Hippo4j application. The published vector requires only low privileges and no user interaction.

2

What systems can be reached through the vulnerable requests?

The attacker can provide arbitrary hostnames and ports in the clientAddress parameter, causing outbound GET requests. This can expose internal network services and cloud metadata services that are reachable from the Hippo4j server.

3

Which deployments are affected?

Hippo4j versions through 1.5.0 are identified as affected. The issue is in four ThreadPoolController endpoints that do not validate clientAddress.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203