# CVE-2026-10759: BUG-000171040 Portal for ArcGIS has a security vulnerability

> An authenticated administrator can perform LDAP injection in Portal for ArcGIS to manipulate directory queries and execute unintended operations.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-pgcr-99wx-x435

## What is CVE-2026-10759?

CVE-2026-10759 is a medium-severity vulnerability in Esri Portal for ArcGIS, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw in Portal for ArcGIS could allow LDAP injection through administrative functionality that constructs Active Directory or LDAP search queries without sufficient input neutralization. An authenticated administrator could supply crafted input that modifies the intended LDAP query and causes unintended directory operations.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

## Which versions are affected by CVE-2026-10759?


## How do I fix CVE-2026-10759?

No fix has been published for CVE-2026-10759 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10759 being exploited?

There is no known exploitation of CVE-2026-10759 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10759 and fix it if it is affected.

What it is: CVE-2026-10759 is a medium-severity vulnerability in Esri Portal for ArcGIS, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10759 in the wild and no public exploit code.

Affected product: Esri Portal for ArcGIS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10759/ (Markdown: https://insights.sbomify.com/CVE-2026-10759/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10759
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10759
- OSV: https://osv.dev/vulnerability/CVE-2026-10759

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10759/
Summaries are generated and may contain mistakes; the official description above is the record.