dbcve.org
Portal For ArcgisApplication · Esri

CVE-2026-13019

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-07
Fix available
A fix is available. Upgrade to after 12.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

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 · unedited
Esri Portal for ArcGIS versions 12.1 and earlier on Windows, Linux and Kubernetes have a missing authentication for critical function vulnerability allows a remote, unauthenticated attacker to access an unprotected API.

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 confidence

Esri Portal for ArcGIS versions 12.1 and earlier contain a critical authentication bypass vulnerability where certain API endpoints lack proper authentication checks. This allows remote, unauthenticated attackers to directly access sensitive API functions that should require valid credentials. The vulnerability affects Windows, Linux, and Kubernetes deployments.

MitigationImplement authentication requirements on all vulnerable API endpoints, or apply vendor-supplied patches/updates when available. Restrict network access to API endpoints as an interim measure until proper authentication is enforced.

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
Portal For ArcgisApplication
Affected:<= 12.1

CVSS 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
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Esri Portal for ArcGIS version
    Access the ArcGIS Portal Administrator Directory (typically at https://<hostname>:7443/arcgis/portal/admin) and navigate to System > Properties > Update Properties, or check the installed software via the system package manager or installation directory. On Windows, check 'Programs and Features' or the installation logs. On Linux, check /opt/arcgis/portal or the response file. On Kubernetes, check the container image tags or deployment configuration.
    Affected if The installed version is 12.1 or any version lower than 12.1 (e.g., 12.0, 11.3, 11.2, etc.)
  2. Verify if the ArcGIS Portal web adapter is configured
    Check the web server configuration (IIS for Windows, Apache/Nginx for Linux) or Kubernetes ingress controller to see if a web adapter is configured. The web adapter typically handles authentication proxying. Inspect the configuration files for the portal URL mapping.
    Affected if A web adapter is not configured, meaning direct access to the portal API endpoints is possible without authentication layer enforcement
  3. Review API endpoint authentication configuration
    Access the ArcGIS Portal Administrator Directory and navigate to Security > Settings > Authentication. Examine whether all API endpoints under the 'resources' path require authentication. Check if any endpoints under /arcgis/sharing/rest/portals/<portalID> are accessible without a token.
    Affected if Authentication is set to 'Not Organized' or specific API endpoints are configured to allow anonymous access when they should require credentials
  4. Test API endpoint access without credentials
    Using a tool like curl or a browser (incognito mode), attempt to access known API endpoints such as: https://<host>:7443/arcgis/sharing/rest/portals/<portalID>/self?f=json. Also test administrative endpoints like /arcgis/portal/admin/. Observe whether the system returns valid JSON data without requiring an OAuth token or login.
    Affected if The API returns sensitive portal configuration data, user information, or administrative functionality without providing any credentials or token
  5. Check network exposure of API ports
    Review firewall rules, security groups, and network ACLs to determine if port 7443 (default HTTPS for Portal) or the web adapter port is exposed to untrusted networks. Use 'netstat -an' or equivalent to list listening ports on the server.
    Affected if Port 7443 or the web adapter port is accessible from untrusted/external networks without network-level restrictions

You are affected if your Esri Portal for ArcGIS version is 12.1 or earlier AND your API endpoints are accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 12.1
Interim mitigation

Implement authentication requirements on all vulnerable API endpoints, or apply vendor-supplied patches/updates when available. Restrict network access to API endpoints as an interim measure until proper authentication is enforced.

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13019 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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