Vulnerability in Serverco Getssl
CVE-2026-10303
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
EPSS 0.008, 55.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Serverco Getssl — versions 0
Weakness classification (CWE)
References
- github.com/srvrco/getssl/pull/896 (mitigation)
- remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/ (related)
- www.cve.org/CVERecord (related)
- www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/ (third-party-advisory)
- github.com/srvrco/getssl/releases/tag/v2.50 (release-notes)