CVE-2026-45221: Konga < 2.1.0 Privilege Escalation via Hardcoded OpenSSL Path
Konga before 2.1.0 contains a privilege escalation vulnerability that allows low-privileged local attackers to execute arbitrary code by planting attacker-controlled OpenSSL configuration or library files in a hardcoded filesystem path absent from default installations. On Windows, the missing directory resides in a location writable by any authenticated local user, enabling attackers to create the directory and place malicious files that execute at the privilege level of the user or service account that launches Konga, facilitating privilege escalation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kongato a version that resolves this vulnerability.Fixed in 2.1.0
Event History
Frequently Asked Questions
Which systems are realistically exposed to this issue?
Windows installations are exposed when the hardcoded OpenSSL path is absent, because any authenticated local user can create the missing directory and place attacker-controlled files there. The issue affects Konga versions before 2.1.0.
What access does an attacker need to exploit it?
An attacker needs authenticated, low-privileged local access to the Windows system. No user interaction is required once malicious OpenSSL configuration or library files have been planted in the writable path.
What privileges can the attacker obtain?
The planted code executes with the privileges of the user or service account that launches Konga. This can allow escalation from a low-privileged local account when Konga is launched by a more privileged account.
What can be done if upgrading is not immediately possible?
Prevent untrusted local users from creating or modifying the hardcoded OpenSSL directory and files, and review the directory for unexpected OpenSSL configuration or library files. Restricting local access also reduces the opportunity to plant malicious files.