CVE-2026-10303
HighCVSS 7.4Exploitation Probability (EPSS)
Elevated risk50th percentile — higher than 50% of all known CVEs
Summary
In getssl version 2.49 and prior, the ACME challenge token was not strictly validated against RFC 8555, allowing a maliciously crafted token to influence local path/filename usage during validation.
Risk Assessment
Attackers could exploit this vulnerability to achieve unauthorized file write/path traversal effects, potentially leading to remote command injection with elevated privileges.
Recommendation
It is recommended to update getssl to the latest version to ensure proper validation of ACME tokens and minimize the risk of attacks.
Original NVD description (English source)
In ServerCo getssl version 2.49 and prior, the ACME challenge token returned to the client was not strictly validated against RFC 8555 before being used in challenge-file handling, allowing a maliciously crafted token to influence local path/filename usage during validation. An attacker who can supply ACME challenge responses to getssl (for example, a malicious or compromised CA endpoint, or an on-path adversary able to tamper with that response path) could exploit this to achieve unauthorized file write/path traversal effects, usually with elevated privileges, ultimately allowing for remote command injection. This issue appears related in spirit to CVE-2023-38198, and is an instance of CWE-73, "External control of file name or path." Other ACME shell script handlers may be affected by similar issues.