SSRF (Server-Side Request Forgery) in Eclipse GlassFish (CVE-2026-12605)
Summary
SSRF in Eclipse GlassFish (CVE-2026-12605). Successful exploitation can lead to full system takeover. Exploitable via gfresttoken.
Original description
The description as published by the source.
In Eclipse GlassFish versions 8.0.x before 8.0.4, CSRF + SSRF in DownloadServlet ContentSources leaks the admin gfresttoken to attacker-controlled host if the victim is authenticated into the Admin Console -> full unauthenticated takeover of Eclipse GlassFish domain until the token expires.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-12605 has been found in Eclipse GlassFish.
Attackers can target a specific entry point like gfresttoken over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Eclipse GlassFish CVE-2026-12605" on the vendor's site.
CVE-2026-12605 (Eclipse GlassFish) — CWE-918 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: gfresttoken
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Eclipse GlassFish. Attackers reach the vulnerable code path via gfresttoken without authentication.
Check the vendor advisory for the affected versions of Eclipse GlassFish. Attack surface: gfresttoken.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Eclipse GlassFish を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory github.com
- web gitlab.eclipse.org
- web gitlab.eclipse.org
- web github.com