Froxlor before 2.3.13 Private Key Disclosure via Certificates API (CVE-2026-100708) | HOL Guard CVE

High · CVSS 7.1CVE-2026-100708

Froxlor before 2.3.13 Private Key Disclosure via Certificates API

Answer in brief

CVE-2026-100708 records a High severity (CVSS 7.1) vulnerability in Froxlor before 2.3.13 Private Key Disclosure via Certificates API. The current sources do not mark it as known exploited. The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
froxlor/froxlorgeneric	>=0 <2.3.13	2.3.13

Recommended response

Check inventory. Check lockfiles and deployed manifests for froxlor/froxlor.
Review the reported fix. Update froxlor/froxlor to 2.3.13 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.