# CVE-2026-7778: runZero Platform dashboard configuration exposure

> An attacker with low privileges can view dashboard configurations outside their authorized scope, exposing sensitive data.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A: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:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-v9q7-47h2-cg7c

## What is CVE-2026-7778?

CVE-2026-7778 is a medium-severity missing authorization vulnerability in runZero Platform, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue that could allow a dashboard configuration to be viewed from outside of the authorized organization scope has been resolved. This is an instance of CWE-269: Improper Privilege Management, and has an estimated CVSS score of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N (5.0, Medium). This issue was fixed in version v4.0.260416.0 of the runZero Platform.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-7778 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7778 is a medium-severity missing authorization vulnerability in runZero Platform, published on 5 May 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-7778 in the wild and no public exploit code.

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

## Sources

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

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