LTPA key exposure via default password
Published Mar 25, 2026 · Updated Mar 25, 2026
Use of a default password in IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.3 allows local users to decrypt LTPA keys. When application security is enabled, Liberty encrypts generated LTPA keys with a default password unless server.xml or server.env supplies an explicit password. Exploitation requires local administrative privileges and an enabled appSecurity feature; exposed keys undermine authentication confidentiality and integrity.
Summary
What happened
Use of a default password in IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.3 allows local users to decrypt LTPA keys. When application security is enabled, Liberty encrypts generated LTPA keys with a default password unless server.xml or server.env supplies an explicit password. Exploitation requires local administrative privileges and an enabled appSecurity feature; exposed keys undermine authentication confidentiality and integrity.
The record
- CVE
- CVE-2025-14917
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- IBM
- Product
- IBM WebSphere Application Server Liberty
- Classifications
- CWE-1393, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 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=17.0.0.3 <=26.0.0.3
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