Vulnerability · Published Jun 16, 2026 · Assigned by runZero
CVE-2026-10303ServerCo getssl ACME shell script path injection
High 7.4
In plain English
A high-severity security flaw in getssl from ServerCo. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.8% (higher than 55% of all known vulnerabilities).
Official description
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.
Affected products (as reported)
Weakness: CWE-73 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
References
- https://github.com/srvrco/getssl/pull/896 mitigation
- https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/ related
- https://www.cve.org/CVERecord?id=CVE-2023-38198 related
- https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/ third-party-advisory
- https://github.com/srvrco/getssl/releases/tag/v2.50 release-notes