CVE-2026-10303

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-16. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
51.3%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_pr, github_release.
generic🔴 Active Exploitation

ServerCo getssl ACME shell script path injection

https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/
generic
https://www.cve.org/CVERecord?id=CVE-2023-38198
generic🟡 PoC Available

Parallel Reconstruction of Lawful TLS Wiretapping | REMY HAX

https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
github_release Patch Available

Release 2.50

Patch available: srvrco/getssl v2.50

https://github.com/srvrco/getssl/releases/tag/v2.50
github_pr Patch Available

RFC 8555 validation and security improvements

Patch available: srvrco/getssl v2.50 (PR #896 merged 2026-06-03)

https://github.com/srvrco/getssl/pull/896

Vendor Advisories for CVE-2026-10303(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 79× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:04 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 22:37 UTCGHSA enrichment
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-16 03:28 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 15:28 UTCGHSA enrichment
  14. 2026-07-15 03:29 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 15:32 UTCGHSA enrichment
  17. 2026-07-14 03:35 UTCGHSA enrichment
  18. 2026-07-13 22:30 UTCEPSS rescore
  19. 2026-07-13 15:38 UTCGHSA enrichment
  20. 2026-07-13 06:12 UTCEPSS rescore
  21. 2026-07-13 03:35 UTCGHSA enrichment
  22. 2026-07-12 15:15 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 03:17 UTCGHSA enrichment
  25. 2026-07-11 15:18 UTCGHSA enrichment
Show 75 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 03:21 UTCGHSA enrichment
  3. 2026-07-10 15:02 UTCGHSA enrichment
  4. 2026-07-10 01:50 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 13:14 UTCGHSA enrichment
  7. 2026-07-09 01:15 UTCGHSA enrichment
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-08 13:17 UTCGHSA enrichment
  11. 2026-07-07 23:33 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 11:35 UTCGHSA enrichment
  14. 2026-07-06 22:59 UTCGHSA enrichment
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:08 UTCGHSA enrichment
  18. 2026-07-05 14:11 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:02 UTCGHSA enrichment
  22. 2026-07-04 14:04 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 01:54 UTCGHSA enrichment
  25. 2026-07-03 13:45 UTCGHSA enrichment
  26. 2026-07-03 00:08 UTCGHSA enrichment
  27. 2026-07-02 12:10 UTCGHSA enrichment
  28. 2026-07-02 00:09 UTCGHSA enrichment
  29. 2026-07-01 15:06 UTCEPSS rescore
  30. 2026-07-01 15:06 UTCEPSS rescore
  31. 2026-07-01 12:11 UTCGHSA enrichment
  32. 2026-07-01 00:13 UTCGHSA enrichment
  33. 2026-06-30 23:22 UTCEPSS rescore
  34. 2026-06-30 12:07 UTCGHSA enrichment
  35. 2026-06-29 23:35 UTCGHSA enrichment
  36. 2026-06-29 11:36 UTCGHSA enrichment
  37. 2026-06-28 23:39 UTCGHSA enrichment
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 11:41 UTCGHSA enrichment
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-27 23:43 UTCGHSA enrichment
  43. 2026-06-27 11:44 UTCGHSA enrichment
  44. 2026-06-27 03:08 UTCEPSS rescore
  45. 2026-06-26 23:46 UTCGHSA enrichment
  46. 2026-06-26 11:49 UTCGHSA enrichment
  47. 2026-06-25 22:13 UTCGHSA enrichment
  48. 2026-06-25 13:49 UTCEPSS rescore
  49. 2026-06-25 10:16 UTCGHSA enrichment
  50. 2026-06-24 22:19 UTCGHSA enrichment
  51. 2026-06-24 14:05 UTCEPSS rescore
  52. 2026-06-24 10:19 UTCGHSA enrichment
  53. 2026-06-23 22:14 UTCGHSA enrichment
  54. 2026-06-23 21:32 UTCEPSS rescore
  55. 2026-06-23 09:48 UTCGHSA enrichment
  56. 2026-06-22 21:44 UTCGHSA enrichment
  57. 2026-06-22 14:25 UTCEPSS rescore
  58. 2026-06-22 14:25 UTCEPSS rescore
  59. 2026-06-22 09:40 UTCGHSA enrichment
  60. 2026-06-21 21:40 UTCGHSA enrichment
  61. 2026-06-21 14:56 UTCEPSS rescore
  62. 2026-06-21 14:56 UTCEPSS rescore
  63. 2026-06-21 09:34 UTCGHSA enrichment
  64. 2026-06-21 01:59 UTCEPSS rescore
  65. 2026-06-21 01:59 UTCEPSS rescore
  66. 2026-06-20 21:23 UTCGHSA enrichment
  67. 2026-06-20 09:26 UTCGHSA enrichment
  68. 2026-06-19 21:04 UTCGHSA enrichment
  69. 2026-06-19 19:25 UTCEPSS rescore
  70. 2026-06-19 09:05 UTCGHSA enrichment
  71. 2026-06-18 21:05 UTCGHSA enrichment
  72. 2026-06-18 17:52 UTCEPSS rescore
  73. 2026-06-18 09:03 UTCGHSA enrichment
  74. 2026-06-17 21:03 UTCGHSA enrichment
  75. 2026-06-17 17:53 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-10303?
CVE-2026-10303 is a high vulnerability published on June 16, 2026. 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…
When was CVE-2026-10303 disclosed?
CVE-2026-10303 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10303 actively exploited?
CVE-2026-10303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10303?
CVE-2026-10303 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-10303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10303, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10303

Explore →

Is Your Infrastructure Affected by CVE-2026-10303?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs