CVE-2026-100708

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

Froxlor before 2.3.13 returns the ssl_key_file column — which stores the raw PEM TLS private-key content — verbatim in the JSON responses of the Certificates.get and Certificates.listing API commands, because the results of the underlying domain_ssl_settings queries are passed through ApiCommand::response() without any field stripping or allowlist. A low-privileged authenticated customer API caller can retrieve the private keys of their own domains' certificates, including Let's Encrypt keys that Froxlor generates server-side and stores root-only (0600) and to which the customer otherwise has no filesystem access; reseller and customers_see_all admin accounts can dump the private keys of other principals through the same sink. Disclosed keys enable domain impersonation, passive decryption of captured TLS traffic, and active machine-in-the-middle attacks.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
48
EG Risk 48/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
Severity71% × 45%
Exploitation40% × 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.1%
EPSS %ILE
2nd
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 28, 2026

Advisory Details (2)

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

Froxlor before 2.3.13 Private Key Disclosure via Certificates API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.13-private-key-disclosure-via-certificates-api
github Patch Available🟡 PoC Available

TLS private key disclosure via Certificates.get/listing API (ssl_key_file returned unfiltered) · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-6q2v-jjq5-m2c8

Vendor Advisories for CVE-2026-100708(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 31× in last 7d / 37× 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 12:31 UTCGHSA enrichment
  2. 2026-10-04 01:41 UTCGHSA enrichment
  3. 2026-10-03 14:50 UTCEG score recompute
  4. 2026-10-03 14:50 UTCGHSA enrichment
  5. 2026-10-03 14:25 UTCEPSS rescore
  6. 2026-10-03 04:00 UTCGHSA enrichment
  7. 2026-10-02 17:09 UTCEG score recompute
  8. 2026-10-02 17:09 UTCGHSA enrichment
  9. 2026-10-02 06:19 UTCEG score recompute
  10. 2026-10-02 06:19 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 19:29 UTCGHSA enrichment
  13. 2026-10-01 08:39 UTCGHSA enrichment
  14. 2026-09-30 21:49 UTCEG score recompute
  15. 2026-09-30 21:49 UTCGHSA enrichment
  16. 2026-09-30 15:02 UTCEPSS rescore
  17. 2026-09-30 10:59 UTCGHSA enrichment
  18. 2026-09-30 00:06 UTCEG score recompute
  19. 2026-09-30 00:06 UTCGHSA enrichment
  20. 2026-09-29 15:20 UTCEPSS rescore
  21. 2026-09-29 13:13 UTCGHSA enrichment
  22. 2026-09-29 02:18 UTCEG score recompute
  23. 2026-09-29 02:18 UTCGHSA enrichment
  24. 2026-09-28 15:27 UTCEG score recompute
  25. 2026-09-28 15:26 UTCGHSA enrichment
Show 12 more
  1. 2026-09-28 14:57 UTCEG score recompute
  2. 2026-09-28 14:57 UTCGHSA enrichment
  3. 2026-09-28 13:50 UTCEPSS rescore
  4. 2026-09-28 09:49 UTCGHSA enrichment
  5. 2026-09-27 22:59 UTCEG score recompute
  6. 2026-09-27 22:59 UTCGHSA enrichment
  7. 2026-09-27 12:09 UTCGHSA enrichment
  8. 2026-09-27 01:19 UTCEG score recompute
  9. 2026-09-27 01:18 UTCGHSA enrichment
  10. 2026-09-26 14:26 UTCEG score recompute
  11. 2026-09-26 13:33 UTCEG score recompute
  12. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100708?
CVE-2026-100708 is a high vulnerability published on September 26, 2026. Froxlor before 2.3.13 returns the sslkeyfile column — which stores the raw PEM TLS private-key content — verbatim in the JSON responses of the Certificates.get and Certificates.listing API commands, because the results of the underlying domainsslsettings queries are passed through…
When was CVE-2026-100708 disclosed?
CVE-2026-100708 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100708 actively exploited?
CVE-2026-100708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100708?
CVE-2026-100708 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100708?
A fix for CVE-2026-100708 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100708 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100708?

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

Book a Demo →Browse All CVEs