VulnerabilityPublished 29 May 2025Updated 15 Dec 2025

CVE-2025-4967: Esri Portal for ArcGIS · Server-Side Request Forgery (SSRF)SSRF

Affects Esri Portal for ArcGISSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

9.1Critical

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

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

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

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 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

Affected software

Product	Affected	Fixed in
Esri Portal for ArcGIS	Affected =0	Fixed in–

AI-suggested

Until an official patch is released by Esri, European organizations should implement several targeted mitigations: 1) Restrict outbound HTTP/HTTPS requests from the Portal for ArcGIS server to only trusted destinations using firewall rules or proxy controls to limit SSRF exploitation scope. 2) Employ network segmentation to isolate the Portal server from sensitive internal systems and data repositories. 3) Monitor server logs and network traffic for unusual or unexpected outbound requests indicative of SSRF attempts. 4) Disable or tightly control any features or plugins in Portal for ArcGIS that perform server-side HTTP requests if not essential. 5) Conduct internal vulnerability assessments and penetration testing focused on SSRF vectors to identify potential exploitation paths. 6) Prepare for rapid deployment of patches by maintaining close communication with Esri support and subscribing to security advisories. 7) Educate IT and security teams about SSRF risks and detection techniques specific to GIS environments. These steps go beyond generic advice by focusing on network-level controls and operational readiness tailored to the Portal for ArcGIS context.

Description

Esri Portal for ArcGIS 11.4 and prior allows a remote, unauthenticated attacker to bypass the Portal’s SSRF protections.

Impact

For European organizations, the impact of CVE-2025-4967 can be substantial. Esri Portal for ArcGIS is commonly used by government agencies, urban planners, environmental organizations, and enterprises managing geospatial data. Exploitation could allow attackers to access internal networks, bypass firewalls, and retrieve sensitive geographic or operational data. This could compromise confidentiality of critical infrastructure information and integrity of GIS data, potentially disrupting decision-making processes. The vulnerability’s unauthenticated nature increases risk of widespread exploitation, especially in environments where Portal for ArcGIS is exposed to the internet. Additionally, SSRF can be a stepping stone for lateral movement within networks, increasing the risk of broader compromise. European organizations involved in smart city initiatives, transportation, defense, and utilities are particularly vulnerable due to their reliance on GIS technologies. The lack of known exploits currently provides a window for proactive defense, but the critical severity demands urgent attention to prevent potential future attacks.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

esri.com/arcgis-blog/products/trust-arcgis/administration/portal-for-arcgis-security-2025-update-3-patch (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Dec 2025, 04:13 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats