CVE-2026-100708 Froxlor before 2.3.13 Private Key Disclosure via Certificates API
Authenticated users can retrieve TLS private keys via API responses, enabling domain impersonation and traffic decryption.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-100708?
CVE-2026-100708 is a high-severity vulnerability in froxlor, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2026-100708?
How do I fix CVE-2026-100708?
No fix has been published for CVE-2026-100708 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-100708 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100708 exists.
Sources
Also known as GHSA-6q2v-jjq5-m2c8, GHSA-wq4p-x9fv-rhvg.