CVE-2026-70557: diboot-core Authenticated Arbitrary Field Read via loadRelatedData Discloses Password Hashes and Salts

Published Aug 6, 2026
·
Updated

diboot-core's POST /common/load-related-data endpoint resolves caller-supplied field names to any @TableField column of any entity and returns those values for all rows, with no field or entity allowlist. The only guard, relatedDataSecurityCheck(), returns true unconditionally, so any authenticated user (including a zero-role account) can read @JsonIgnore-annotated secret fields such as IamAccount.authSecret and IamAccount.secretSalt for every account, or arbitrary secret fields of any other entity. Shiro's two-iteration MD5 with an 8-character salt is trivially crackable offline, so the disclosed admin password hashes convert to full administrative takeover. The endpoint is not example code; the official diboot-admin-ui frontend requires it, so deployments following the vendor's recommended integration expose it. The mechanism was renamed relatedData to attachMore on the development branch, but attachMoreSecurityCheck() also returns true unconditionally.

Affected Software

1 affected component
diboot-core

Event History

Aug 6, 2026
CVE Published
via MITRE·07:16 PM
Data Sourced
via MITRE·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:18 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-70557?

CVE-2026-70557 has a medium severity rating of 6.5.

2

How do I fix CVE-2026-70557?

To fix CVE-2026-70557, implement a proper field and entity allowlist for the /common/load-related-data endpoint.

3

What risk does CVE-2026-70557 pose?

CVE-2026-70557 poses a risk level of 38, indicating a significant potential impact if exploited.

4

What kind of data does CVE-2026-70557 disclose?

CVE-2026-70557 discloses sensitive information such as password hashes and salts.

5

Is user authentication a factor in CVE-2026-70557?

Yes, CVE-2026-70557 requires user authentication to exploit the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203