CVE-2026-9182 arcgis server vulnerability
Esri ArcGIS Server contains an unrestricted file upload vulnerability. An unauthenticated attacker could exploit this issue by uploading a crafted file to the affected endpoint. Successful exploitation could allow arbitrary file upload, potentially allowing for other attacks. 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.
Quick answer
esri arcgis server should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- -
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Esri ArcGIS Server is affected by CVE-2026-9182, a unauthenticated arbitrary file upload risk. Esri ArcGIS Server contains an unrestricted file upload vulnerability. The recommended remediation is to update to the Esri ArcGIS Server security update from the May 2026 ArcGIS Security Bulletin, or a vendor-supported release newer than affected ArcGIS Server 12.0 and prior builds. Until the update is complete, block unauthenticated upload endpoints and restrict ArcGIS Server exposure until patched, review logs, and reduce exposure of the affected service, library, appliance, or trusted firmware path.
- Inventory every deployment, package, appliance, service, application dependency, trusted firmware image, and managed environment that uses Esri ArcGIS Server.
- Confirm the installed version/build and compare it with the affected versions listed in the source advisory and the source advisory for CVE-2026-9182.
- Apply the vendor-supported fix: update to the Esri ArcGIS Server security update from the May 2026 ArcGIS Security Bulletin, or a vendor-supported release newer than affected ArcGIS Server 12.0 and prior builds.
- If the update cannot be applied immediately, block unauthenticated upload endpoints and restrict ArcGIS Server exposure until patched; disable unnecessary public access, file processing, authentication integrations, upload endpoints, or high-risk features until patched.
- Review application, appliance, reverse-proxy, WAF, package manager, authentication, trusted firmware, and audit logs for activity related to CVE-2026-9182.
- Rotate sessions, API tokens, service credentials, integration keys, signing keys, and administrator passwords if logs or affected data indicate compromise, code execution, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or firmware images when appropriate, and remove temporary files, uploaded artifacts, stored payloads, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Esri ArcGIS Server now reports the Esri ArcGIS Server security update from the May 2026 ArcGIS Security Bulletin, or a vendor-supported release newer than affected ArcGIS Server 12.0 and prior builds or a later vendor-supported fixed release/build for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-9182, using a safe regression test, vendor validation method, dependency inventory, or appliance health check.
- Review logs after remediation for continued exploit attempts, authentication anomalies, denial-of-service symptoms, suspicious uploads, file access, deserialization attempts, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, firmware inventory, appliance health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup, rebuild, or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-9182?
esri arcgis server versions listed as affected should be reviewed: -.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.