CVE-2026-10303
In ServerCo getssl version 2.49 and prior, the ACME challenge token …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/srvrco/getssl/pull/896
- github.com/srvrco/getssl/releases/tag/v2.50
- remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
- www.cve.org/CVERecord?id=CVE-2023-38198
- www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/
- nvd.nist.gov/vuln/detail/CVE-2026-10303
- cve.org/CVERecord?id=CVE-2026-10303
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.