Skip to main content

GeoServer EUVDEUVD-2025-210277

| CVE-2025-52465 HIGH
External Control of File Name or Path (CWE-73)
2026-06-12 https://github.com/geoserver/geoserver GHSA-7qmg-grcp-qf25
7.2
CVSS 3.1 · Vendor: https://github.com/geoserver/geoserver
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain GeoServer admin credentials
  2. Delivery
    Set master password to JSP webshell payload
  3. Exploit
    Submit absolute path under Tomcat webapps to Master Password Dump page
  4. Execution
    GeoServer writes JSP file to disk
  5. Persist
    Tomcat auto-deploys JSP webshell
  6. Impact
    Request shell URL to execute commands as service user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
Exploitation Conditions

Requires an authenticated GeoServer account holding administrator rights over the security subsystem (PR:H), network reachability to the GeoServer web administration interface, and the web admin UI must not be disabled or stripped from the deployment. For full RCE the host must auto-execute JSPs from a directory writable by the GeoServer process - the canonical case called out by the vendor is geoserver.war dropped into a default Apache Tomcat webapps directory; the target JSP path must not already exist and all parent directories must exist. For the NTLM-leak variant GeoServer must run on Windows and the supplied path must be a UNC reachable to the attacker. Exploitation is blocked entirely on installations where the web UI is disabled or removed.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (7.2 High) accurately reflects that the bug needs an authenticated GeoServer administrator but, once that bar is met, the attack is fully remote, scriptable, and yields full CIA impact via RCE. No EPSS score, KEV listing, or public PoC was provided, so this is not currently a mass-exploitation candidate - the real risk profile is post-compromise privilege escalation (admin → host RCE) or malicious-insider scenarios rather than internet-wide drive-by exploitation. A secondary, environment-conditional risk applies on Windows hosts where the admin can coerce GeoServer into making an outbound SMB/UNC fetch to leak the service account's NTLM hash, useful for lateral movement. The PR:H requirement materially limits widespread exploitation, but any deployment that treats the GeoServer admin role as lower-trust than the underlying OS account should treat this as critical.

Exploit ScenarioDerived

A malicious or compromised GeoServer administrator logs into the web admin UI, sets the master password to a small JSP webshell payload, then visits the Master Password Dump page and supplies an absolute path such as /var/lib/tomcat/webapps/ROOT/shell.jsp; Tomcat auto-deploys the new JSP and the attacker requests it to execute OS commands as the Tomcat user. On Windows, the same primitive can target a UNC path like \\attacker.example.com\share\dump to coerce an outbound NTLM authentication and capture the service account's hash for offline cracking or relay.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 12, 2026

Arbitrary file write in GeoServer's Master Password Dump web page allows an authenticated administrator to write attacker-controlled content to any absolute filesystem path the GeoServer process can write to, including JSP files in a Tomcat webapps directory. Because GeoServer enforces no maximum master password length, an admin can embed malicious JSP code into the master password and dump it to an executable location, escalating to remote code execution on the host. No public exploit identified at time of analysis and the issue is not in CISA KEV.

RemediationAI

Vendor-released patch: upgrade to GeoServer 2.27.3 or 2.26.4 (or later) per the GitHub Security Advisory at https://github.com/geoserver/geoserver/security/advisories/GHSA-7qmg-grcp-qf25 and PR https://github.com/geoserver/geoserver/pull/8584. Where immediate patching is not possible, mitigate by disabling or removing the GeoServer web administration interface entirely (the vulnerable code path is only reachable through the web UI), which eliminates the bug at the cost of losing browser-based administration and forcing all configuration through application properties or REST. As compensating controls, tightly restrict membership of the GeoServer ROLE_ADMINISTRATOR group, deploy GeoServer behind a hardened reverse proxy that ACL-restricts the /web/ and security endpoints to trusted admin networks, run the servlet container as an unprivileged user whose write access does not include any auto-deploy directory (move geoserver.war out of Tomcat's default webapps autodeploy path and disable autoDeploy/unpackWARs), and on Windows run the GeoServer service under a dedicated low-privilege local account and egress-block outbound SMB (TCP/445) to deny NTLM-relay coercion.

Affected VersionsENISA

org.geoserver.web:gs-web-sec-core 2.27.0, < 2.27.3
org.geoserver.web:gs-web-app < 2.26.4
org.geoserver.web:gs-web-app 2.27.0, < 2.27.3
org.geoserver.web:gs-web-sec-core < 2.26.4

Affected Packages

maven org.geoserver.web:gs-web-app fix: 2.26.4, 2.27.3
maven org.geoserver.web:gs-web-sec-core fix: 2.26.4, 2.27.3
euvd org_geoserver_web_gs_web_app fix: 2.26.4, 2.27.3
euvd org_geoserver_web_gs_web_sec_core fix: 2.26.4, 2.27.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

GeoServer is an open-source Java/Servlet GIS server (Maven artifacts org.geoserver.web:gs-web-app and gs-web-sec-core) typically deployed as a WAR file inside Apache Tomcat. The Master Password Dump page in the security web UI accepts a user-supplied filename and writes the cleartext master password to it using java.io.File with only minimal validation; a prior path-traversal fix blocks relative traversal but not absolute paths, which is the root cause class captured by CWE-73 (External Control of File Name or Path). Because the master password field has no length cap, the 'password' value itself becomes attacker-controlled file content, turning a write-primitive into JSP code execution under standard Tomcat auto-deployment.

Know when Tomcat gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (https://github.com/geoserver/geoserver) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

Network-reachable admin UI (AV:N), deterministic write primitive (AC:L), requires GeoServer security-admin role (PR:H), no user interaction, and JSP-drop yields full host CIA impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/geoserver/geoserver).

CVSS VectorVendor: https://github.com/geoserver/geoserver

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Summary

A vulnerability exists that allows an authenticated administrator with access to GeoServer's security system to pass arbitrary file names to the Master Password Dump web page and create files containing the master password in plaintext. The provided file name must be an absolute path to the target file, the target file can not already exist and all parent directories must already exist.

Details

When dumping the master password, GeoServer will use the provided file name with minimal validation as long as it is a java.io.File path. The only limitation is that the fix for a previous, unrelated vulnerability prevents relative path traversal here but absolute paths can be used to access arbitrary files. GeoServer does not enforce a maximum password length by default which allows an administrator to place malicious code into their password which could then be dumped into a JSP file.

Impact

Remote Code Execution (High severity)

This vulnerability can lead to executing arbitrary code if GeoServer is deployed in an environment where an attacker can dynamically deploy and execute a JSP file. This is possible if the geoserver.war file is simply placed into the webapps directory of a default Tomcat installation.

NTLM Hash Disclosure (Moderate severity)

If GeoServer is deployed in a Windows operating system and the GeoServer administrator does not already have access to the Windows account running the GeoServer process, it may be possible for the administrator to make GeoServer trigger an outbound NTLM request to a remote, attacker-controlled server and gain access to the NTLM hash or user password for use in future attacks.

Denial of Service (Low severity)

This vulnerability allows writing a file to any location where the GeoServer process has write permissions which could still potentially cause some kind of denial of service.

Mitigation

GeoServer installations where the web interface is either disabled or completely removed are not affected since the vulnerability exists in one of the web pages.

Resources

https://osgeo-org.atlassian.net/browse/GEOS-11852 https://github.com/geoserver/geoserver/pull/8584

Executive ViewAI

Why It Matters

GeoServer deployments are vulnerable to file write attacks that enable remote code execution through authenticated administrator accounts. No public exploit has been identified at the time of analysis, though the vulnerability poses significant risk if admin credentials are compromised or misused. Vendor patches are available and should be deployed immediately across all GeoServer systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 65% exploitable
Threat Intel
1
1 source
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in Tomcat

View all
CVE-2017-12617 HIGH POC
8.1 Oct 04

When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTT

CVE-2020-1938 CRITICAL POC
9.8 Feb 24

When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Rate

CVE-2023-47246 CRITICAL POC
9.8 Nov 10

In SysAid On-Premise before 23.3.36, a path traversal vulnerability leads to code execution after an attacker writes a f

CVE-2016-8735 CRITICAL POC
9.8 Apr 06

Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8

CVE-2017-12615 HIGH POC
8.1 Sep 19

When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. Rated high severity (CVSS 8.1), this

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2014-0050 HIGH POC
7.5 Apr 01

MultipartStream.java in Apache Commons FileUpload before 1.3.1, as used in Apache Tomcat, JBoss Web, and other products,

CVE-2020-13935 HIGH POC
7.5 Jul 14

The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to

CVE-2018-11784 MEDIUM POC
4.3 Oct 04

When the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a r

CVE-2022-29885 HIGH POC
7.5 May 12

The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78

CVE-2017-12616 HIGH
7.5 Sep 19

When using a VirtualDirContext with Apache Tomcat 7.0.0 to 7.0.80 it was possible to bypass security constraints and/or

CVE-2020-9484 HIGH POC
7.0 May 20

When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a)

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy