# CVE-2026-9152: Unauthenticated SOAP Endpoint in Altium 365 SearchService Allows Cross-Tenant Data Exfiltration and Index Destruction

> Unauthenticated attackers can read and modify search index data across tenants in Altium 365, exposing sensitive workspace information.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-g63v-r3mf-m22g

## What is CVE-2026-9152?

CVE-2026-9152 is a critical missing authorization vulnerability in Altium 365, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication vulnerability exists in the Altium 365 SearchService. A legacy SOAP endpoint exposes search index operations without requiring authentication, session tokens, or any form of identity verification. An unauthenticated network attacker who can reference a target workspace's identifier can interact with that workspace's search index, crossing tenant boundaries.

Successful exploitation allows reading a workspace's indexed contents (such as component data, project and folder names, and user metadata) and injecting, modifying, or deleting search index entries. These operations affect the search index only, not the underlying vault data, but they can disclose sensitive workspace information and compromise the integrity and availability of search results. Altium 365 cloud deployments are affected; on-premise Altium Enterprise Server is not affected.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-9152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9152 is a critical missing authorization vulnerability in Altium 365, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9152 in the wild and no public exploit code.

Affected product: Altium 365. 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-9152/ (Markdown: https://insights.sbomify.com/CVE-2026-9152/index.md)
```

## Sources

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

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