External risk intelligence

Eclipse GlassFish DownloadServlet Vulnerability Allows Unauthenticated Domain Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-12605

The vulnerability exists in the Eclipse GlassFish Admin Console. Administration interfaces for application servers are commonly deployed as web-based management portals that are frequently exposed to the network or internet to allow for remote management, making them likely to be reachable in real-world deployment scenarios.

Server-Side Request Forgery

Eclipse Glassfish

8.0.0 to before 8.0.4

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in Eclipse GlassFish, a Java application server. This issue, if exploited, could allow an unauthenticated attacker to gain full control of the administrative console. The primary concern is to determine if this technology is in use and if it is exposed in a way that could be targeted.

  • Attackers can take over admin access.
  • Critical systems may be at risk.
  • Confirm relevance and any exposure.

Attack Path

How an attacker could exploit the issue

An attacker could trick a logged-in administrator into visiting a malicious website, which then makes a request to the GlassFish Admin Console. This request exploits a flaw in the DownloadServlet to send the administrator's session token to a server controlled by the attacker, enabling them to take over the GlassFish domain.

  • Victim must be authenticated to Admin Console.
  • Malicious request to DownloadServlet.
  • Unauthenticated domain takeover possible.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an authenticated user interacting with the GlassFish Admin Console could trigger a Cross-Site Request Forgery (CSRF) and Server-Side Request Forgery (SSRF) vulnerability. This could lead to the leakage of an administrator's authentication token, potentially allowing an attacker to gain full control of the GlassFish domain until the token expires.

  • Admin console access token.
  • Victim visits malicious site.
  • Full domain takeover possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The critical vulnerability in Eclipse GlassFish affects the Admin Console, suggesting that platform or infrastructure teams managing application servers are likely responsible for remediation. The first practical step is to locate all GlassFish instances, confirm their reachability and business criticality, and identify the accountable owners before planning mitigation.

  • Platform/infrastructure teams own this.
  • Verify GlassFish instance reachability.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Eclipse GlassFish?

Eclipse GlassFish is a Java application server used to deploy and manage enterprise-grade web applications. It provides the runtime environment for Java EE and Jakarta EE services. It includes an Admin Console, which is a web-based interface that allows administrators to configure the server, monitor performance, and manage deployments remotely.

How does CVE-2026-12605 work?

This vulnerability involves a combination of Cross-Site Request Forgery (CSRF) and Server-Side Request Forgery (SSRF) within the DownloadServlet. This weakness class (CWE-918) allows an attacker to manipulate the server into making unauthorized requests. By tricking an authenticated administrator, the flaw leaks a specific security token used for managing the domain to an external server controlled by the attacker.

What triggers this GlassFish vulnerability?

An attacker triggers this by luring an administrator—who is already logged into the GlassFish Admin Console—to visit a malicious website. The attack requires the victim to have an active session in the console. Simply accessing the server without an active admin session or navigating to the site without being authenticated to the console will not trigger this specific issue.

Is my instance at risk according to Halo Surface Signal?

Halo Surface Signal notes that this vulnerability exists specifically in the Admin Console. Because these management portals are often deployed with network or internet access to facilitate remote administration, they are frequently reachable by attackers. You should evaluate whether your instance is reachable from untrusted networks, as this increases the likelihood of the vulnerability being targeted.

What should I do first to address this?

Start by identifying all instances of Eclipse GlassFish running within your environment. Verify who owns these systems and confirm their network reachability. Once you have a clear inventory, prioritize the most critical servers for updates or access restrictions while coordinating with the teams responsible for platform and infrastructure management.

References