Authenticated key disclosure via hardcoded obfuscation constants
Published Sep 4, 2026 · Updated Sep 4, 2026
Cryptographic weakness in IBM's DCM component in releases 7.3 through 7.6 allows remote authenticated users to obtain sensitive information. DCM protects encryption keys with hardcoded cryptographic constants, making the obfuscation reproducible rather than secret. IBM does not identify the affected routine or key store; the published prose describes remote authenticated access, while the CVSS assessment requires local high privileges.
Summary
What happened
Cryptographic weakness in IBM's DCM component in releases 7.3 through 7.6 allows remote authenticated users to obtain sensitive information. DCM protects encryption keys with hardcoded cryptographic constants, making the obfuscation reproducible rather than secret. IBM does not identify the affected routine or key store; the published prose describes remote authenticated access, while the CVSS assessment requires local high privileges.
The record
- CVE
- CVE-2026-16693
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- IBM
- Product
- IBM i
- Classifications
- CWE-327, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.3
- Affected versionversion=7.4
- Affected versionversion=7.5
- Affected versionversion=7.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo