dbcve.org
Runzero PlatformApplication · Runzero

CVE-2026-5376

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 4.0.260203.0 or later.
See remediation →
65/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 prevent session inactivity timeouts from triggering due to automatic page reloading has been resolved. This is an instance of CWE-613: Insufficient Control of Resources After Expiration or Release, and has an estimated CVSS score of CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N (5.9 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 confidence

The runZero Platform had a session management flaw where automatic page reloading prevented the inactivity timeout from triggering, allowing authenticated sessions to persist beyond their intended expiration. This is CWE-613 (Insufficient Control of Resources After Expiration), enabling potential session hijacking or unauthorized access if a user's session is left active after they walk away.

MitigationUpgrade runZero Platform to version 4.0.260203.0 or later to receive the session timeout fix.

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
Runzero PlatformApplication
Affected:< 4.0.260203.0

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/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 checks

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

  1. Identify runZero Platform installation
    Locate the runZero Platform installation directory or check for running services/processes named 'runzero' or similar
    Affected if The runZero Platform software is present on the system
  2. Determine installed version
    Check the installed version of runZero Platform (typically via CLI command, web interface footer, or version file in installation directory)
    Affected if The installed version is earlier than 4.0.260203.0
  3. Verify auto-refresh is enabled
    Check if the automatic page refresh or auto-reload feature is enabled in the platform settings or user preferences
    Affected if Auto-refresh is enabled and the version is vulnerable
  4. Confirm session timeout configuration
    Inspect the session timeout settings in the platform configuration to understand the intended expiration window
    Affected if Session timeouts are configured but auto-refresh bypasses them

A user is affected if runZero Platform version is earlier than 4.0.260203.0 and automatic page reloading is enabled, causing sessions to persist beyond their configured timeout.

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
Upgrade available Upgrade to 4.0.260203.0 or later
Fixed in 4.0.260203.0
Interim mitigation

Upgrade runZero Platform to version 4.0.260203.0 or later to receive the session timeout fix.

Recommended fix High confidence

Upgrade to runZero Platform version 4.0.260203.0 or later

  1. Check current version of runZero Platform by accessing the admin console or system settings
  2. If the current version is below 4.0.260203.0, initiate an upgrade to version 4.0.260203.0 or later
  3. Follow standard runZero Platform upgrade procedures (backup configuration, schedule maintenance window, etc.)
  4. After upgrade, verify the version has been updated to 4.0.260203.0 or higher
  5. Confirm session inactivity timeouts are now functioning correctly by testing logout behavior after the configured timeout period

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

Fix this in Runzero Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5376 — 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-5376 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