CVE-2026-10303
Last modified
CVE-2026-10303 is a high-severity vulnerability rated 7.4/10 on the CVSS scale. 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. EPSS estimates a 0.76% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| ServerCo | getssl | <= 2.49 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-10303?
How severe is CVE-2026-10303?
How do I fix CVE-2026-10303?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-10297A vulnerability was identified in itsourcecode Fees Manageme…6.3
- CVE-2026-10298A security flaw has been discovered in ggml-org whisper.cpp …3.3
- CVE-2026-10299A weakness has been identified in code-projects Online Hospi…3.8
- CVE-2026-10300A security vulnerability has been detected in SGLang 0.5.10.…3.7
- CVE-2026-10301A vulnerability was detected in itsourcecode Fees Management…4.3
- CVE-2026-10302A flaw has been found in itsourcecode Fees Management System…6.3
- CVE-2026-10305Out-of-bounds read vulnerability in Samsung Open Source rlot…6.1
- CVE-2026-1032The Conditional Menus plugin for WordPress is vulnerable to …4.3
- CVE-2026-1035A flaw was found in the Keycloak server during refresh token…3.1
- CVE-2026-1036The Photo Gallery by 10Web – Mobile-Friendly Image Gallery p…5.3
- CVE-2026-1042The WP Hello Bar plugin for WordPress is vulnerable to Store…4.4
- CVE-2026-1043The PostmarkApp Email Integrator plugin for WordPress is vul…4.4
Are you affected by CVE-2026-10303?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
