{"api_version":"1","generated_at":"2026-06-19T22:29:39+00:00","cve":"CVE-2026-10303","urls":{"html":"https://cve.report/CVE-2026-10303","api":"https://cve.report/api/cve/CVE-2026-10303.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-10303","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-10303"},"summary":{"title":"ServerCo getssl ACME shell script path injection","description":"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.","state":"PUBLISHED","assigner":"runZero","published_at":"2026-06-16 20:16:26","updated_at":"2026-06-17 17:16:41"},"problem_types":["CWE-73","CWE-73 CWE-73 External control of file name or path"],"metrics":[{"version":"3.1","source":"44488dab-36db-4358-99f9-bc116477f914","type":"Secondary","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"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","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://www.cve.org/CVERecord?id=CVE-2023-38198","name":"https://www.cve.org/CVERecord?id=CVE-2023-38198","refsource":"44488dab-36db-4358-99f9-bc116477f914","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/","name":"https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/","refsource":"44488dab-36db-4358-99f9-bc116477f914","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/","name":"https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/","refsource":"44488dab-36db-4358-99f9-bc116477f914","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/srvrco/getssl/releases/tag/v2.50","name":"https://github.com/srvrco/getssl/releases/tag/v2.50","refsource":"44488dab-36db-4358-99f9-bc116477f914","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/srvrco/getssl/pull/896","name":"https://github.com/srvrco/getssl/pull/896","refsource":"44488dab-36db-4358-99f9-bc116477f914","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-10303","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-10303","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"ServerCo","product":"getssl","version":"affected 2.49 custom","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"remy","lang":"en"},{"source":"CNA","value":"Tod Beardsley of runZero","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"10303","cve":"CVE-2026-10303","epss":"0.007570000","percentile":"0.503180000","score_date":"2026-06-18","updated_at":"2026-06-19 00:08:11"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-10303","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-06-17T15:17:32.277126Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-06-17T15:18:11.930Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unaffected","product":"getssl","repo":"https://github.com/srvrco/getssl","vendor":"ServerCo","versions":[{"lessThanOrEqual":"2.49","status":"affected","version":"0","versionType":"custom"}]}],"credits":[{"lang":"en","type":"finder","value":"remy"},{"lang":"en","type":"coordinator","value":"Tod Beardsley of runZero"}],"datePublic":"2026-06-16T18:20:00.000Z","descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"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."}],"value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-73","description":"CWE-73 External control of file name or path","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-06-16T18:24:43.712Z","orgId":"44488dab-36db-4358-99f9-bc116477f914","shortName":"runZero"},"references":[{"tags":["mitigation"],"url":"https://github.com/srvrco/getssl/pull/896"},{"tags":["related"],"url":"https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/"},{"tags":["related"],"url":"https://www.cve.org/CVERecord?id=CVE-2023-38198"},{"tags":["third-party-advisory"],"url":"https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/"},{"tags":["release-notes"],"url":"https://github.com/srvrco/getssl/releases/tag/v2.50"}],"source":{"discovery":"EXTERNAL"},"title":"ServerCo getssl ACME shell script path injection","x_generator":{"engine":"Vulnogram 1.0.2"}}},"cveMetadata":{"assignerOrgId":"44488dab-36db-4358-99f9-bc116477f914","assignerShortName":"runZero","cveId":"CVE-2026-10303","datePublished":"2026-06-16T18:24:43.712Z","dateReserved":"2026-05-31T21:05:04.476Z","dateUpdated":"2026-06-17T15:18:11.930Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-16 20:16:26","lastModifiedDate":"2026-06-17 17:16:41","problem_types":["CWE-73","CWE-73 CWE-73 External control of file name or path"],"metrics":{"cvssMetricV31":[{"source":"44488dab-36db-4358-99f9-bc116477f914","type":"Secondary","cvssData":{"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","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":2.2,"impactScore":5.2}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-06-17T15:17:32.277126Z","id":"CVE-2026-10303","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"10303","Ordinal":"1","Title":"ServerCo getssl ACME shell script path injection","CVE":"CVE-2026-10303","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"10303","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"ServerCo getssl ACME shell script path injection"}]}}}