Domain credential exposure via sensitive log entries
Published Nov 19, 2025 · Updated Nov 19, 2025
Sensitive-data logging in upKeeper Solutions upKeeper Manager 5.2.0 through 5.2.11 allows attackers to obtain domain credentials. The vendor identifies log-file insertion but has not disclosed the affected component, the specific log entries, or the operation that writes the credentials. The vendor's assessment requires local access, high privileges, and active user interaction; exposed credentials can then be used to authenticate within the domain.
Summary
What happened
Sensitive-data logging in upKeeper Solutions upKeeper Manager 5.2.0 through 5.2.11 allows attackers to obtain domain credentials. The vendor identifies log-file insertion but has not disclosed the affected component, the specific log entries, or the operation that writes the credentials. The vendor's assessment requires local access, high privileges, and active user interaction; exposed credentials can then be used to authenticate within the domain.
The record
- CVE
- CVE-2025-11446
- Published
- Nov 19, 2025
- Updated
- Nov 19, 2025
- Vendor
- upKeeper Solutions AB
- Product
- upKeeper Manager
- Classifications
- CWE-532, CAPEC-560, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 19, 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=5.2.0 <5.2.12
What conditions does exploitation require?
What is affected?
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