Skip to main content
VulnerabilityPublished

CVE-2026-70557: diboot-core · Insecure Direct Object Reference

Affects diboot-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
dibootdiboot-coreAffected
  • <=3.9.0
Fixed in–

AI-suggested

Until a fix is available, restrict access to the vulnerable endpoint or disable the diboot-admin-ui frontend that relies on it. Monitor vendor communications for updates and apply official patches once released. Avoid exposing this endpoint to untrusted users.

Description

diboot-core contains an authorization bypass vulnerability in its POST /common/load-related-data endpoint. This endpoint allows any authenticated user, including those with minimal privileges, to read sensitive fields from any entity without proper access control. The vulnerability arises because the security check always returns true, exposing secret fields such as admin password hashes. These hashes use a weak MD5-based scheme that can be cracked offline, potentially leading to full administrative takeover. The vulnerable endpoint is used by the official diboot-admin-ui frontend, making this a significant risk in standard deployments.

References

Community reviews

Loading reviews…