CVE-2026-5374
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 MCP agents to access remediation and asset information from outside of the 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:H/I:N/A:N (5.8 Medium). This issue was fixed in version 4.0.260202.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 confidenceMCP agents in runZero Platform could access remediation and asset information outside their authorized organization scope due to incorrect authorization checks (CWE-863). This allowed privilege escalation through the API where agents with high privileges but limited scope could view sensitive asset data across organizational boundaries.
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.260202.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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine runZero Platform versionCheck the installed version of the runZero Platform server or console. This is typically visible in the product UI footer, about page, or administrative settings panel.Affected if The installed version is below 4.0.260202.0 (e.g., 4.0.250100.0, 3.x.x.x, etc.)
-
Verify MCP agent configurationInspect whether MCP (Model Context Protocol) agents are enabled or configured in the runZero Platform. This is found in the integrations, automation, or agent settings section of the administrative interface.Affected if MCP agents are enabled and configured in the environment
-
Review organization scope assignmentsCheck the access control settings for MCP agents to determine whether they have been assigned permissions spanning multiple organizations or broader scope than intended.Affected if Any MCP agent has permissions that grant access across organizational boundaries or to multiple organizations
-
Inspect API audit logs for cross-org data accessReview runZero Platform API audit logs or access logs for any MCP agent API calls that retrieved remediation or asset data from organizations outside the agent's assigned scope.
A user is affected if they run runZero Platform version below 4.0.260202.0 with MCP agents enabled and have not yet verified that organization-scoped access controls are properly restricting MCP agent access to only their authorized organization resources.
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.260202.0
Upgrade runZero Platform to version 4.0.260202.0 or later. After upgrading, verify that organization-scoped access controls properly restrict MCP agent access to only authorized organization resources.
4.0.260202.0
- Identify the current version of the runZero Platform in use
- Plan for an upgrade during a maintenance window
- Upgrade the runZero Platform to version 4.0.260202.0 or later
- After upgrade, verify that MCP agents can only access data within their authorized organization scope
- Confirm the fix by testing cross-organization data access attempts from MCP agents
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5374 — 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-5374 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