CVE-2026-100708

published 26 Sep 2026 · updated 28 Sep 2026

Froxlor before 2.3.13 Private Key Disclosure via Certificates API

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.13.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
froxlor<2.3.132.3.13

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100708 severity on Zeptric[![CVE-2026-100708](https://zeptric.io/badge/cve/CVE-2026-100708.svg)](https://zeptric.io/cve/CVE-2026-100708)