# 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.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-6q2v-jjq5-m2c8, GHSA-wq4p-x9fv-rhvg

## 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 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100708 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100708 exists.

Affected product: froxlor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100708/ (Markdown: https://insights.sbomify.com/CVE-2026-100708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100708
- OSV: https://osv.dev/vulnerability/CVE-2026-100708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100708/
Summaries are generated and may contain mistakes; the official description above is the record.