Credential disclosure via embedded source-code secrets
Published May 27, 2025 · Updated Aug 26, 2025
Credential exposure in IBM Controller 11.0.0, 11.0.1, and 11.1.0 allows remote authenticated users to obtain sensitive credentials. IBM states that credentials can be inadvertently included in application source code but does not identify the file, component, or retrieval path. A valid account and network access are required, and the reported consequence is credential disclosure without integrity or availability impact.
Summary
What happened
Credential exposure in IBM Controller 11.0.0, 11.0.1, and 11.1.0 allows remote authenticated users to obtain sensitive credentials. IBM states that credentials can be inadvertently included in application source code but does not identify the file, component, or retrieval path. A valid account and network access are required, and the reported consequence is credential disclosure without integrity or availability impact.
The record
- CVE
- CVE-2025-33079
- Published
- May 27, 2025
- Updated
- Aug 26, 2025
- Vendor
- IBM
- Product
- IBM Controller
- Classifications
- CWE-522, CWE-256, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 2025Record 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=11.0.0, 11.0.1
- Affected versionversion=11.1.0
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