CVE-2026-4158

7.3

KeePassXC · KeePassXC

KeePassXC is vulnerable to a local privilege escalation flaw due to an uncontrolled search path element during OpenSSL configuration loading.

Executive summary

KeePassXC version 2.7.11 contains an uncontrolled search path element vulnerability that allows local attackers to escalate privileges and execute arbitrary code.

Vulnerability

This vulnerability is caused by an uncontrolled search path element (CWE-427) within the OpenSSL configuration loading process. An attacker who has already obtained the ability to execute low-privileged code on the target system can exploit this to execute arbitrary code with the privileges of the user running the KeePassXC application.

Business impact

The exploitation of this vulnerability poses a significant risk to the integrity and confidentiality of sensitive data managed by KeePassXC. Because the application is a password manager, a successful privilege escalation could allow an attacker to gain unauthorized access to all stored credentials, leading to full compromise of the user's digital identity and potential lateral movement within the environment. With a CVSS score of 7.3, this flaw is categorized as High severity, reflecting the critical nature of the compromised asset.

Remediation

Immediate Action: Monitor the KeePassXC GitHub security advisories for the release of a patched version and apply the update immediately upon availability.

Proactive Monitoring: Audit system logs for unauthorized file access or suspicious process execution occurring within the context of the KeePassXC application.

Compensating Controls: Ensure that the host system is configured with the principle of least privilege, restricting the ability of low-privileged users to modify system paths or configuration files used by applications.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the sensitivity of the data managed by KeePassXC, this vulnerability represents a high-risk scenario for any environment relying on this password manager. Security teams should prioritize tracking the vendor's patch release and apply the update to all affected installations as soon as it is published to prevent potential local privilege escalation attacks.

Sources