CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-2586 remediation guide

Eclipse Foundation Eclipse Glassfish, glassfish

An authenticated Remote Code Execution (RCE) vulnerability was identified in GlassFish's Administration Console. A user with access to the panel can send crafted requests that allow the execution of arbitrary operating system commands with the privileges of the application service user. This issue affects Eclipse GlassFish: from 8.0.0 to 8.0.1, fixed in 8.0.2; 7.1.0, fixed in 7.1.1; from 7.0.0 to 7.0.25, fixed in 7.0.26. Impact on versions from 5.1.0 to 6.2.5 is unknown.

Open CVE record
ProductEclipse Foundation Eclipse Glassfish, glassfish
Affected versions>= 7.0.0 < 7.0.26, >= 7.1.0 < 7.1.1, >= 8.0.0 < 8.0.2, < 8.0.2
Fixed versions8.0.2
Priority basisReview · CVSS 9.1 · EPSS 0.84%
01

Identify the affected asset

Confirm whether Eclipse Foundation Eclipse Glassfish, glassfish is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 7.0.0 < 7.0.26, >= 7.1.0 < 7.1.1, >= 8.0.0 < 8.0.2, < 8.0.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 8.0.2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.