CVE-2026-33519
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 · uneditedAn incorrect authorization vulnerability exists in Esri Portal for ArcGIS 11.4, 11.5 and 12.0 on Windows, Linux and Kubernetes that did not correctly check permissions assigned to developer credentials.
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 Portal for ArcGIS 11.4, 11.5, and 12.0 contains an incorrect authorization vulnerability where permission checks for developer credentials are not properly enforced, allowing unauthorized access to resources or functionality that should be restricted based on assigned permissions.
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= 11.4= 11.5= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Esri Portal for ArcGIS is installedIdentify whether Esri Portal for ArcGIS is present in your environment using system inventory tools, software listings, or by checking for the ArcGIS Portal installation directoryAffected if Esri Portal for ArcGIS is installed and running
-
Check the installed versionDetermine the exact version of Esri Portal for ArcGIS installed by accessing the product about page, version information in the administrator directory, or using the arcgisportaladmin APIAffected if The installed version is 11.4, 11.5, or 12.0
-
Determine if developer credentials are configuredCheck if developer credentials, API keys, or developer app registrations are configured in the Portal administrator settings or through the ArcGIS Portal DirectoryAffected if Developer credentials or developer API access is enabled in the Portal configuration
-
Review permission assignments for developer accountsInspect the permission model for developer credentials in the Portal administrator console or through thesharing API to verify which resources and operations developer accounts are authorized to accessAffected if Developer credentials have been assigned permissions that should be restricted but may be improperly enforced due to the vulnerability
-
Audit access control configurationReview the access control policies and sharing settings in the Portal administrator to identify any resources accessible to developer accounts that should be restricted based on assigned permissionsAffected if Resources or functionality accessible to developer accounts exceed what their assigned permissions should allow
A user is affected if they are running Esri Portal for ArcGIS version 11.4, 11.5, or 12.0 with developer credentials configured, where those credentials can access resources or functionality that should be restricted based on their assigned permissions.
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 the vendor-provided security patch from Esri for the affected versions. Prior to deployment, verify developer credential permission configurations and validate access controls in a staging environment.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.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 $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33519 — 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-33519 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