CVE-2026-100713

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

Froxlor 2.3.10 and earlier contain a time-of-check time-of-use (TOCTOU) race condition in the SSH key synchronization cron (lib/Froxlor/Cron/System/SshKeys.php, SshKeys::generateFiles). The containment/symlink validation performed by FileDir::makeCorrectDir()/makeCorrectFile() is done only at check time; the live filesystem path is re-resolved as root at write time (file_put_contents with FILE_APPEND|LOCK_EX, followed by chmod/chown/chgrp), with a database round-trip and file reads in between, and no path or file-descriptor pinning (no O_NOFOLLOW or openat2(RESOLVE_NO_SYMLINKS)). On installations where the non-default setting system.allow_customer_shell=1 grants customers local shell access, a customer can atomically swap their ~/.ssh directory for a symlink after the check and before the write, causing the root-run cron to append the customer's public key to /root/.ssh/authorized_keys and to chown /root/.ssh to the customer, resulting in full root compromise of the panel host. The cron re-runs on every interval, allowing unlimited attempts. This is a residual race that bypasses the check-time fix introduced for GHSA-mq5v-... . The issue is fixed in Froxlor 2.3.12.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
35
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 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.2%
EPSS %ILE
4th
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 26, 2026

Advisory Details (2)

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

Froxlor before 2.3.12 Privilege Escalation via SSH Key Sync | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-privilege-escalation-via-ssh-key-sync
github Patch Available🟡 PoC Available

SSH-key sync cron re-resolves the authorized_keys path at write time — customer wins a race to append their key to root's authorized_keys (residual of GHSA-mq5v) · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-927x-9jfh-mq42

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100713?
CVE-2026-100713 is a high vulnerability published on September 26, 2026. Froxlor 2.3.10 and earlier contain a time-of-check time-of-use (TOCTOU) race condition in the SSH key synchronization cron (lib/Froxlor/Cron/System/SshKeys.php, SshKeys::generateFiles). The containment/symlink validation performed by FileDir::makeCorrectDir()/makeCorrectFile() is done only at check…
When was CVE-2026-100713 disclosed?
CVE-2026-100713 was first published on September 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100713 actively exploited?
CVE-2026-100713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100713?
CVE-2026-100713 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100713?
A fix for CVE-2026-100713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100713 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100713?

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

Book a Demo →Browse All CVEs