{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-10303: ServerCo getssl ACME shell script path injection","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-10303","status":"final","version":"1","initial_release_date":"2026-06-16T18:24:43.712Z","current_release_date":"2026-06-16T18:24:43.712Z","revision_history":[{"date":"2026-06-16T18:24:43.712Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-10303 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-10303"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-10303"},{"category":"external","summary":"github.com","url":"https://github.com/srvrco/getssl/pull/896"},{"category":"external","summary":"remyhax.xyz","url":"https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/"},{"category":"external","summary":"cve.org","url":"https://www.cve.org/CVERecord?id=CVE-2023-38198"},{"category":"external","summary":"runzero.com","url":"https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/"},{"category":"external","summary":"github.com","url":"https://github.com/srvrco/getssl/releases/tag/v2.50"}]},"product_tree":{"branches":[{"category":"vendor","name":"ServerCo","branches":[{"category":"product_name","name":"getssl","branches":[{"category":"product_version_range","name":"<=2.49","product":{"name":"ServerCo getssl <=2.49","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:serverco:getssl:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-10303","title":"ServerCo getssl ACME shell script path injection","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":7.4,"baseSeverity":"HIGH"},"products":["CSAFPID-1"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1"]}]}]}