CVE-2026-10303

Published: Giu 16, 2026 Last Modified: Giu 16, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,4
Source: 44488dab-36db-4358-99f9-bc116477f914
Attack Vector: network
Attack Complexity: high
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: none

Description

AI Translation Available

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.

73

External Control of File Name or Path

Draft
Common Consequences
Security Scopes Affected:
Integrity Confidentiality Availability
Potential Impacts:
Read Files Or Directories Modify Files Or Directories Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Other)
Applicable Platforms
Operating Systems: Unix, Windows, macOS
View CWE Details
https://github.com/srvrco/getssl/pull/896
https://github.com/srvrco/getssl/releases/tag/v2.50
https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
https://www.cve.org/CVERecord?id=CVE-2023-38198
https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-…