VulnerabilityPublished 10 Jun 2025

CVE-2025-30145: geoserver · Infinite Loop

Affects geoserverSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.25.7 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.25.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade geoserver/geoserver to 2.25.7.

Affected software

Product	Affected	Fixed in
GitHubgeoserver/geoserver`pkg:github/geoserver/geoserver`Other threats	Affected <2.25.7	Fixed in 2.25.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should promptly upgrade GeoServer installations to versions 2.27.0, 2.26.3, or 2.25.7 where the vulnerability is fixed. If immediate upgrading is not feasible, disabling WMS dynamic styling and the Jiffle process is recommended to prevent execution of malicious scripts. Network-level protections such as firewall rules restricting access to GeoServer management interfaces and WMS/WPS endpoints to trusted IPs can reduce exposure. Monitoring GeoServer logs for unusual or repeated Jiffle script executions can help detect attempted exploitation. Additionally, implementing rate limiting and anomaly detection on GeoServer services may help mitigate denial of service attempts. Organizations should also review and harden access controls and ensure GeoServer instances are not unnecessarily exposed to the public internet. Regular vulnerability scanning and patch management processes should be enforced to promptly identify and remediate such issues.

Description

GeoServer is an open source server that allows users to share and edit geospatial data. Malicious Jiffle scripts can be executed by GeoServer, either as a rendering transformation in WMS dynamic styles or as a WPS process, that can enter an infinite loop to trigger denial of service. This vulnerability is fixed in 2.27.0, 2.26.3, and 2.25.7. This vulnerability can be mitigated by disabling WMS dynamic styling and the Jiffle process.

Impact

For European organizations, the impact of this vulnerability can be significant, especially for government agencies, urban planning departments, environmental monitoring organizations, and private companies that rely heavily on geospatial data services provided by GeoServer. A successful exploitation leads to denial of service, potentially disrupting critical geospatial data access and processing workflows. This can affect decision-making processes, emergency response coordination, and public services that depend on real-time or near-real-time geospatial information. The lack of confidentiality or integrity impact limits data breach concerns, but availability disruption can cause operational downtime and loss of trust. Given the remote and unauthenticated nature of the exploit, attackers can easily target exposed GeoServer instances, amplifying the risk. The disruption could also have cascading effects on dependent systems and services that consume GeoServer outputs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 04:19 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats