ServerCo getssl ACME shell script path injection
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-10303
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 16:42 UTC · Revision 1
Source evidence
ServerCo getssl ACME shell script path injection
core-osv · Original sourcePublished 16 Jun 2026, 18:24 UTC
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.
osv:CVE-2026-10303
Complete source record
{
"id": "5ed150af2301e22894efe98a50e6067e9af85e9726becbef784197932ac9bd96",
"url": "https://osv.dev/vulnerability/CVE-2026-10303",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ServerCo getssl ACME shell script path injection",
"summary": "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.",
"evidence": "osv:CVE-2026-10303",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-10303",
"aliases": [
"CVE-2026-10303"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/srvrco/getssl",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "b0b856df1eb1265ce56785eb1d2af880669b8788"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "2.49"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "b0b856df1eb1265ce56785eb1d2af880669b8788"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v2.50"
}
]
}
}
],
"versions": [
"2.50",
"v2.49",
"2.49",
"2.48",
"v2.47",
"v2.46",
"v2.45",
"v2.44",
"v2.43",
"v2.41",
"v2.39",
"v2.38",
"v2.37",
"push",
"v2.36",
"v2.35",
"v2.34",
"v2.33",
"v2.32",
"v2.31",
"v2.30",
"v2.29",
"2.29",
"v2.28",
"v2.27",
"v2.26",
"v2.24",
"v2.22",
"v2.21",
"v2.20",
"v2.19",
"v2.18",
"v2.17",
"v2.16",
"v2.15",
"v2.14",
"v2.13",
"v2.12",
"v2.11",
"v2.10",
"v2.09",
"v2.03",
"v2.00",
"v1.92",
"v1.87",
"v1.85",
"v1.84",
"v1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-10303.json"
}
}
],
"modified": "2026-10-28T02:30:44.379697019Z",
"provider": "osv",
"references": [
"https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/",
"https://www.cve.org/CVERecord?id=CVE-2023-38198",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/10xxx/CVE-2026-10303.json",
"https://github.com/srvrco/getssl/releases/tag/v2.50",
"https://nvd.nist.gov/vuln/detail/CVE-2026-10303",
"https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/",
"https://github.com/srvrco/getssl/pull/896",
"https://github.com/srvrco/getssl"
],
"provider_metadata": {
"cwe_ids": [
"CWE-73"
],
"cna_assigner": "runZero",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/10xxx/CVE-2026-10303.json"
}
},
"related_cves": [
{
"value": "CVE-2026-10303",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 512437,
"published_at": "2026-06-16T18:24:43.712+00:00"
}