# CVE-2026-11889: SALTO ProAccess Space Authorization Bypass Through User-Controlled Key

> An authorized attacker can bypass authorization controls to access any space in SALTO ProAccess Space when the tenancy feature is enabled.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-4g4j-8g2w-gqh9

## What is CVE-2026-11889?

CVE-2026-11889 is a high-severity authentication bypass vulnerability in SALTO ProAccess Space, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SALTO ProAccess Space software using the tenancy feature / logical 
partition is vulnerable to a privilege escalation attack that could 
allow an authorized attacker to access any space managed by the affected
 product.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-11889 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11889 is a high-severity authentication bypass vulnerability in SALTO ProAccess Space, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11889 in the wild and no public exploit code.

Affected product: SALTO ProAccess Space. 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-11889/ (Markdown: https://insights.sbomify.com/CVE-2026-11889/index.md)
```

## Sources

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

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