CVE-2026-9181
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEsri ArcGIS Server contains a directory traversal vulnerability. ArcGIS Enterprise on Kubernetes is not impacted. An unauthenticated attacker could exploit this issue by sending crafted path parameters. Successful exploitation could allow overwriting sensitive files on the system. Abuse of this issue can allow full administrative access to ArcGIS Server, with high impact to confidentiality, integrity, and availability. This issue impacts all versions of ArcGIS Server on Windows and Linux 12.0 and prior. This issue does not impact ArcGIS Enterprise for Kubernetes.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEsri ArcGIS Server contains a directory traversal vulnerability that allows unauthenticated attackers to send crafted path parameters to overwrite sensitive files on the system. Successful exploitation grants full administrative access to ArcGIS Server, with high impact to confidentiality, integrity, and availability. This vulnerability affects all versions of ArcGIS Server on Windows and Linux 12.0 and prior.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm ArcGIS Server is installedCheck for ArcGIS Server installation directory (typically C:\Program Files\ArcGIS\Server on Windows or /arcgis/server on Linux) or query running processes for 'ArcGIS Server' or 'ArcGIS' servicesAffected if ArcGIS Server is found running or installed on the system
-
Identify installed ArcGIS Server versionCheck the version file or use the ArcGIS Server Administrator Directory: navigate to <server-url>/portal/portaladmin/firmware/versions or check the 'About' page in ArcGIS Server Manager; also check the installation directory for a version manifest or about.html fileAffected if Installed version is 12.0 or any version prior to 12.0 (e.g., 11.x, 10.x)
-
Verify the server is network-accessibleAttempt to reach the ArcGIS Server REST endpoints (typically ports 6080 or 6443) from an external host or verify the listener is bound to a non-localhost interface using netstat or ss commandsAffected if ArcGIS Server endpoints are accessible from untrusted networks without authentication
-
Check for suspicious file modificationsReview web server logs and file system for unexpected changes to sensitive files in the ArcGIS installation directory (config-store, directories, etc.) or look for new/unknown files in system directoriesAffected if Evidence of unauthorized file writes or new files in restricted directories
-
Audit for creation of unexpected administrative accountsQuery the ArcGIS Server Administrator API at /admin/users or review user stores for new accounts with administrative privileges added after the software installation dateAffected if Unexpected administrator accounts exist in ArcGIS Server that were not created by authorized personnel
If ArcGIS Server version 12.0 or earlier is installed and its endpoints are network-accessible, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches when available; until then, restrict network access to ArcGIS Server endpoints and implement strict input validation on path parameters to block traversal sequences.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9181 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9181 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data