{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5376 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5376 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5376 is a medium-severity vulnerability in runZero Platform, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5376 and fix it if it is affected.\n\nWhat it is: CVE-2026-5376 is a medium-severity vulnerability in runZero Platform, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5376 in the wild and no public exploit code.\n\nAffected product: runZero Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5376/ (Markdown: https://insights.sbomify.com/CVE-2026-5376/index.md)","id":"CVE-2026-5376","markdown":"https://insights.sbomify.com/CVE-2026-5376/index.md","name":"CVE-2026-5376","record":{"aliases":["GHSA-gf6w-7f3p-cmx4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"runZero Platform","requires_auth":"high_privilege","summary":"Attackers can bypass session inactivity timeouts via automatic page reloading, maintaining unauthorized access to the runZero Platform.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"runZero","cpe":[{"product":"runzero_platform","vendor":"runzero"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"runZero Platform session timeout failure","id":"CVE-2026-5376","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Incorrect Authorization in GitLab","id":"CVE-2026-5377"},"packages":[],"prev":{"headline":"runZero Platform API credential information leak","id":"CVE-2026-5375"},"products":["Platform"],"published":"2026-04-07","related":[{"cvss_score":8.1,"headline":"runZero Platform superuser privilege escalation","id":"CVE-2026-5373","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":6.4,"headline":"runZero Platform SQL injection in saved queries","id":"CVE-2026-5372","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.8,"headline":"runZero Platform MCP information leak","id":"CVE-2026-5374","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.8,"headline":"runZero Platform user creation leak","id":"CVE-2026-5378","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.8,"headline":"runZero Platform incorrect credential scope","id":"CVE-2026-5384","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.3,"headline":"runZero Platform cleartext secret exposure","id":"CVE-2026-5380","kev_date_added":null,"published":"2026-04-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["runZero"]},"summary":"Attackers can bypass session inactivity timeouts via automatic page reloading, maintaining unauthorized access to the runZero Platform.","url":"https://insights.sbomify.com/CVE-2026-5376/"}