dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-7778

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a cross-tenant authorization vulnerability in the runZero Platform where dashboard configurations could be accessed by users outside their authorized organization scope. The vulnerability stems from improper privilege management (CWE-269) allowing low-privileged users to view sensitive dashboard configuration data from other organizations due to insufficient access control checks.

MitigationUpgrade to runZero Platform version v4.0.260416.0 or later. After upgrading, verify that organization-scoped access controls properly restrict dashboard configuration access to only authorized users within each organization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify runZero Platform installation and version
    Locate the runZero Platform installation and determine the installed version number. This is typically found in the platform's about page, administrative console, or by querying the platform's API endpoint for version information.
    Affected if The installed version is lower than v4.0.260416.0
  2. Verify multi-tenant organization configuration
    Check if the runZero Platform instance has multiple organizations or tenants configured. This can be done by accessing the administrative settings and reviewing the organization/tenant management section.
    Affected if Multiple organizations are configured in the platform and the version is below v4.0.260416.0
  3. Review dashboard configuration access controls
    Examine the access control settings for dashboard configurations. Attempt to access dashboard configurations from a low-privileged user account in one organization while another organization exists, to verify if cross-organization data leakage occurs.
    Affected if Low-privileged users can view dashboard configurations from organizations other than their own
  4. Audit user role permissions for cross-organization access
    Review the permission model for user roles, specifically checking if there are any role assignments that permit users to access resources outside their assigned organization scope.
    Affected if Users have role permissions that allow access to dashboard configurations across organization boundaries

A user is affected if they are running a runZero Platform version below v4.0.260416.0 with multiple organizations configured, where low-privileged users can access dashboard configurations from other organizations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to runZero Platform version v4.0.260416.0 or later. After upgrading, verify that organization-scoped access controls properly restrict dashboard configuration access to only authorized users within each organization.

Recommended fix Moderate confidence

v4.0.260416.0

  1. 1. Identify the current version of the runZero Platform instance by accessing the administration or settings area
  2. 2. If the current version is earlier than v4.0.260416.0, plan for an upgrade to v4.0.260416.0 or later
  3. 3. Review the runZero upgrade documentation at help.runzero.com or www.runzero.com for version-specific upgrade procedures
  4. 4. Perform a backup of the current configuration and data as a precautionary measure
  5. 5. Execute the upgrade to version v4.0.260416.0 following the documented upgrade path
  6. 6. After upgrade, verify that the fix for the unauthorized dashboard configuration viewing issue (CWE-269) is applied by testing cross-organization scope restrictions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7778 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data