CVE-2026-5378
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 · uneditedAn issue that allowed administrators to create and update users outside of their authorized organization scope has been resolved. This is an instance of CWE-863: Incorrect Authorization, and has an estimated CVSS score of CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N (5.8 Medium). This issue was fixed in version 4.0.260203.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 · high confidenceThis is an Incorrect Authorization (CWE-863) vulnerability in the runZero Platform where administrators could create or update user accounts outside their assigned organization scope. The flaw allows privilege escalation by enabling high-privileged users to modify organizational boundaries they should not have access to, impacting system integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.0.260203.0CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed runZero Platform versionAccess the runZero Platform administration interface or use the platform's built-in version check command (typically found in System Settings > About or via CLI if available). Note the exact version number displayed.Affected if The installed version is less than 4.0.260203.0 (e.g., 4.0.250000.0 or earlier). Compare your version string numerically to 4.0.260203.0.
-
Review user management audit logs for cross-organization modificationsIn the runZero Platform, navigate to the Audit Logs or Activity Log section. Filter for events related to user creation or modification. Look for entries where an administrator account modified users in an organization different from their assigned scope.Affected if Audit logs show user creation or modification events where the target user's organization differs from the performing administrator's assigned organization scope.
-
Verify administrative user scope assignmentsAs an administrator with appropriate privileges, review the list of admin users and their organization assignments in the Platform. Check each admin account to confirm their assigned organization matches their actual scope of user management capabilities.Affected if Any administrator account has the ability to manage users in organizations beyond what is explicitly assigned to them in the system configuration.
-
Examine user account organizational affiliationsReview the full list of user accounts in the system. For each user, note their assigned organization. Cross-reference this with which administrator last modified each account by checking the account modification history or audit trail.Affected if Users exist whose organizational affiliation was changed by an administrator who, according to their role scope, should not have had permission to modify users in that organization.
You are affected if your runZero Platform version is below 4.0.260203.0 AND audit logs or user modification records show administrators creating or updating users outside their assigned organization scope.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.0.260203.0
Upgrade runZero Platform to version 4.0.260203.0 or later to remediate this authorization bypass. Organizations should verify that user administrative boundaries are correctly enforced post-upgrade.
4.0.260203.0
- Review the runZero Platform release notes for version 4.0.260203.0 to understand changes and any prerequisites
- Schedule a maintenance window for the upgrade
- Create a backup of the current runZero Platform configuration and database
- Download version 4.0.260203.0 from the official runZero distribution channels
- Follow the standard runZero upgrade procedure: stop services, apply the upgrade, verify database migrations complete successfully
- Restart runZero Platform services
- Verify the upgrade was successful by logging in and confirming the version number
- Test user management functionality to confirm the authorization fix is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5378 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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