Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112029 Overview
CVE-2026-112029 affects diem-project diem versions up to 5.1.3. The flaw resides in the lib/model/doctrine/PluginDmUser.class.php file within the SHA1 Handler component. Manipulation of the salt/password arguments produces password hashes with insufficient computational effort, categorized as [CWE-326] Inadequate Encryption Strength.
The weakness allows an attacker with local access to recover plaintext credentials from stored hashes more efficiently than a modern password hashing scheme would permit. The exploit has been publicly disclosed. The diem-project maintainers were notified through an issue report but have not responded.
Critical Impact
Stored user password hashes rely on a fast, unsalted-style SHA1 construction, enabling offline credential recovery if an attacker obtains the user table.
Affected Products
- diem-project diem versions up to and including 5.1.3
- Component: SHA1 Handler in lib/model/doctrine/PluginDmUser.class.php
- Deployments relying on the default diem user authentication model
Discovery Timeline
- 2026-10-18 - CVE-2026-112029 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-112029
Vulnerability Analysis
The diem framework stores user credentials using a SHA1-based hashing routine implemented in PluginDmUser.class.php. SHA1 is a fast, general-purpose cryptographic hash function designed for speed, not for password storage. Modern password hashing requires computationally expensive, memory-hard functions such as bcrypt, scrypt, or Argon2.
Because the handler uses a single SHA1 pass over the salt and password arguments, an attacker with access to the hash database can compute billions of candidate hashes per second on commodity GPU hardware. This drastically reduces the cost of brute-force and dictionary attacks against the stored credentials.
Exploitation requires local access to the hash store and a high level of attacker skill to pivot the recovered credentials. The direct confidentiality impact is limited, but recovered credentials often enable follow-on account takeover against the affected diem installation or any system where users reused the same password.
Root Cause
The root cause is the use of a cryptographic primitive that is unsuitable for password storage. SHA1 lacks the adjustable work factor and memory hardness required by [CWE-326]. Even when combined with a per-user salt, a single SHA1 invocation does not meaningfully slow down offline cracking.
Attack Vector
An attacker must first obtain the stored hashes through a separate exposure, such as a database backup, a SQL injection, or local file access. With the hashes in hand, the attacker performs offline cracking against the SHA1 output using tools such as hashcat or john. Network-only attackers cannot exploit this weakness directly.
No verified public code example is available. See the GitHub Issue #452 Discussion and VulDB CVE-2026-112029 entries for the maintainer-facing report.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112029
Indicators of Compromise
- Unexpected read access to the diem user table or database backup files containing dm_user records
- Successful authentications from unusual IP addresses or geolocations shortly after a suspected data exposure
- Presence of SHA1-formatted password values in exported database artifacts stored outside protected locations
Detection Strategies
- Audit the lib/model/doctrine/PluginDmUser.class.php file for calls to sha1() used in password generation or verification
- Review database access logs for queries targeting the user table from service accounts that do not normally require credential data
- Correlate failed login spikes with recent file access to configuration or backup directories to identify credential-stuffing follow-on activity
Monitoring Recommendations
- Enable query-level auditing on the diem database and alert on bulk reads of the user table
- Monitor web server and shell access logs for enumeration of lib/model/doctrine/ paths
- Track authentication anomalies such as logins to dormant accounts, which may indicate successful offline hash recovery
How to Mitigate CVE-2026-112029
Immediate Actions Required
- Restrict file system and database access to the diem user table to the minimum set of service accounts
- Replace the SHA1-based hashing routine with a password-specific function such as bcrypt, scrypt, or argon2id
- Force a password reset for all diem users once a stronger hashing scheme is deployed
- Rotate any shared or administrative credentials that may have been stored using the weak hash
Patch Information
No vendor patch is available at the time of publication. The maintainers of the diem-project repository have not responded to the issue report tracked in GitHub Issue #452. Operators should treat this as an unpatched flaw and apply compensating controls.
Workarounds
- Fork the project and migrate PluginDmUser.class.php to use password_hash() with PASSWORD_BCRYPT or PASSWORD_ARGON2ID, re-hashing on next successful login
- Enforce multi-factor authentication at the application or reverse-proxy layer to limit the value of recovered passwords
- Encrypt database backups at rest and restrict backup access to a short list of administrators
- Implement account lockout and rate limiting to blunt credential-stuffing attempts that follow offline cracking
# Example PHP replacement for the vulnerable SHA1 handler
# Replace: $hash = sha1($salt.$password);
# With:
# $hash = password_hash($password, PASSWORD_ARGON2ID);
# And verify with:
# password_verify($password, $hash);
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

