CVE-2026-100714

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-26. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Froxlor before 2.3.12 does not restrict or escape the system.letsencryptchallengepath setting: unlike sibling settings hardened in GHSA-33mp, the field has no string_regexp or required_otp guard, and its value is concatenated unescaped into the acme.sh command line built in lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php and executed by the root cron via FileDir::safe_exec. Because safe_exec only blacklists shell metacharacters such as ; | & > < \ $ ~ ?, spaces and quotes survive and the value is word-split into additional acme.sh arguments. An administrator, or any actor able to write settings (for example through the settings-import API), can therefore inject acme.sh options such as --renew-hook, --pre-hook or --post-hook to obtain arbitrary command execution as root at the next Let's Encrypt cron run, or use --config-home/--cert-home for arbitrary file writes. Versions up to and including 2.3.10 are affected; the issue is fixed in 2.3.12.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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
Severity91% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 26, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Froxlor before 2.3.12 Command Injection via letsencryptchallengepath | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-command-injection-via-letsencryptchallengepath
github Patch Available🟡 PoC Available

`system.letsencryptchallengepath` setting is concatenated unescaped into the root cron's acme.sh command line (admin→root argument injection) · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-3w4g-cmpj-rj42

Vendor Advisories for CVE-2026-100714(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 56× in last 7d / 67× 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.

  1. 2026-10-04 08:31 UTCGHSA enrichment
  2. 2026-10-04 04:38 UTCGHSA enrichment
  3. 2026-10-04 00:46 UTCGHSA enrichment
  4. 2026-10-03 20:54 UTCGHSA enrichment
  5. 2026-10-03 17:03 UTCEG score recompute
  6. 2026-10-03 17:03 UTCGHSA enrichment
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-03 13:11 UTCGHSA enrichment
  9. 2026-10-03 09:19 UTCGHSA enrichment
  10. 2026-10-03 05:27 UTCGHSA enrichment
  11. 2026-10-03 01:35 UTCGHSA enrichment
  12. 2026-10-02 21:43 UTCGHSA enrichment
  13. 2026-10-02 17:50 UTCEG score recompute
  14. 2026-10-02 17:50 UTCGHSA enrichment
  15. 2026-10-02 13:59 UTCGHSA enrichment
  16. 2026-10-02 10:07 UTCGHSA enrichment
  17. 2026-10-02 06:15 UTCGHSA enrichment
  18. 2026-10-02 02:23 UTCGHSA enrichment
  19. 2026-10-01 22:23 UTCEG score recompute
  20. 2026-10-01 22:23 UTCGHSA enrichment
  21. 2026-10-01 19:49 UTCEPSS rescore
  22. 2026-10-01 18:27 UTCGHSA enrichment
  23. 2026-10-01 14:34 UTCGHSA enrichment
  24. 2026-10-01 10:42 UTCGHSA enrichment
  25. 2026-10-01 06:51 UTCGHSA enrichment
Show 42 more
  1. 2026-10-01 02:57 UTCGHSA enrichment
  2. 2026-09-30 23:03 UTCGHSA enrichment
  3. 2026-09-30 19:10 UTCGHSA enrichment
  4. 2026-09-30 15:18 UTCEG score recompute
  5. 2026-09-30 15:18 UTCGHSA enrichment
  6. 2026-09-30 15:02 UTCEPSS rescore
  7. 2026-09-30 11:26 UTCGHSA enrichment
  8. 2026-09-30 07:34 UTCGHSA enrichment
  9. 2026-09-30 03:42 UTCGHSA enrichment
  10. 2026-09-29 23:47 UTCGHSA enrichment
  11. 2026-09-29 17:15 UTCEG score recompute
  12. 2026-09-29 17:15 UTCGHSA enrichment
  13. 2026-09-29 15:20 UTCEPSS rescore
  14. 2026-09-29 13:21 UTCGHSA enrichment
  15. 2026-09-29 09:26 UTCGHSA enrichment
  16. 2026-09-29 05:34 UTCGHSA enrichment
  17. 2026-09-29 01:41 UTCGHSA enrichment
  18. 2026-09-28 21:50 UTCEG score recompute
  19. 2026-09-28 21:50 UTCGHSA enrichment
  20. 2026-09-28 17:58 UTCGHSA enrichment
  21. 2026-09-28 13:59 UTCEG score recompute
  22. 2026-09-28 13:59 UTCGHSA enrichment
  23. 2026-09-28 13:50 UTCEPSS rescore
  24. 2026-09-28 10:07 UTCGHSA enrichment
  25. 2026-09-28 06:16 UTCGHSA enrichment
  26. 2026-09-28 02:24 UTCGHSA enrichment
  27. 2026-09-27 22:32 UTCGHSA enrichment
  28. 2026-09-27 18:40 UTCGHSA enrichment
  29. 2026-09-27 14:47 UTCEG score recompute
  30. 2026-09-27 14:47 UTCGHSA enrichment
  31. 2026-09-27 10:55 UTCGHSA enrichment
  32. 2026-09-27 07:03 UTCGHSA enrichment
  33. 2026-09-27 03:12 UTCEG score recompute
  34. 2026-09-27 03:11 UTCGHSA enrichment
  35. 2026-09-26 23:17 UTCEG score recompute
  36. 2026-09-26 23:17 UTCGHSA enrichment
  37. 2026-09-26 22:10 UTCGHSA enrichment
  38. 2026-09-26 18:18 UTCEG score recompute
  39. 2026-09-26 18:18 UTCGHSA enrichment
  40. 2026-09-26 14:25 UTCEG score recompute
  41. 2026-09-26 13:33 UTCEG score recompute
  42. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100714?
CVE-2026-100714 is a critical vulnerability published on September 26, 2026. Froxlor before 2.3.12 does not restrict or escape the system.letsencryptchallengepath setting: unlike sibling settings hardened in GHSA-33mp, the field has no stringregexp or requiredotp guard, and its value is concatenated unescaped into the acme.sh command line built in…
When was CVE-2026-100714 disclosed?
CVE-2026-100714 was first published on September 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100714 actively exploited?
CVE-2026-100714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100714?
CVE-2026-100714 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100714?
A fix for CVE-2026-100714 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100714 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100714?

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

Book a Demo →Browse All CVEs