CVE-2026-92569

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

Hippo4j through 1.5.0 SSRF via clientAddress Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hippo4j-through-1.5.0-ssrf-via-clientaddress-parameter
generic

[Bug] SSRF via unvalidated `clientAddress` parameter in thread pool monitoring endpoints · Issue #1621 · opengoofy/hippo4j · GitHub

https://github.com/opengoofy/hippo4j/issues/1621
generic

hippo4j/hippo4j-server/hippo4j-console/src/main/java/cn/hippo4j/console/controller/ThreadPoolController.java at 73124de92e269940bdf44f4534b37a13a36ffd49 · opengoofy/hippo4j · GitHub

https://github.com/opengoofy/hippo4j/blob/73124de92e269940bdf44f4534b37a13a36ffd49/hippo4j-server/hippo4j-console/src/main/java/cn/hippo4j/console/controller/ThreadPoolController.java#L123-L179
generic

hippo4j/hippo4j-server/hippo4j-auth/src/main/java/cn/hippo4j/auth/config/GlobalSecurityConfig.java at 73124de92e269940bdf44f4534b37a13a36ffd49 · opengoofy/hippo4j · GitHub

https://github.com/opengoofy/hippo4j/blob/73124de92e269940bdf44f4534b37a13a36ffd49/hippo4j-server/hippo4j-auth/src/main/java/cn/hippo4j/auth/config/GlobalSecurityConfig.java#L95-L107
generic

GitHub - opengoofy/hippo4j: 📌 异步线程池框架，支持线程池动态变更&监控&报警，无需修改代码轻松引入。Asynchronous thread pool framework, support Thread Pool Dynamic Change & monitoring & Alarm, no need to modify the code easily introduced. · GitHub

https://github.com/opengoofy/hippo4j

Vendor Advisories for CVE-2026-92569(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 23:15 UTCEG score recompute
  2. 2026-09-20 23:15 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-19 21:37 UTCEG score recompute
  5. 2026-09-19 21:37 UTCGHSA enrichment
  6. 2026-09-18 19:58 UTCEG score recompute
  7. 2026-09-18 19:58 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-17 18:19 UTCEG score recompute
  11. 2026-09-17 18:19 UTCGHSA enrichment
  12. 2026-09-16 15:23 UTCEG score recompute
  13. 2026-09-16 14:46 UTCEG score recompute
  14. 2026-09-16 14:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92569?
CVE-2026-92569 is a medium vulnerability published on September 16, 2026. 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…
When was CVE-2026-92569 disclosed?
CVE-2026-92569 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92569 actively exploited?
CVE-2026-92569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.2% of all scored CVEs.
What is the CVSS score of CVE-2026-92569?
CVE-2026-92569 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-92569?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92569, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92569

Explore →

Is Your Infrastructure Affected by CVE-2026-92569?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs