# CVE-2026-75480: OpenViking Debug Vector Endpoints Multi-tenant Data Exposure

> Authenticated users can access private data of other users in the same account via debug endpoints lacking user-level access controls.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 17 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-gpqq-qx8w-x7gh

## What is CVE-2026-75480?

CVE-2026-75480 is a high-severity missing authorization vulnerability in volcengine OpenViking, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenViking debug vector scroll and count endpoints apply only account-level scoping without user-level access controls, allowing authenticated users to read all co-tenant records. Attackers can query these endpoints to retrieve private memories, resources, skills, and secret material belonging to other users in the same account without administrative privileges.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-75480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75480 is a high-severity missing authorization vulnerability in volcengine OpenViking, published on 17 Aug 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-75480 in the wild and no public exploit code.

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

## Sources

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

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