CVE-2026-100709

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

Froxlor through 2.3.10 stores only a numeric user ID in remembered-2FA tokens (panel_2fa_tokens) without recording the account namespace, and the remembered-token lookup during login is not constrained to the customer or administrator account type. Because customer and administrator IDs are allocated from separate namespaces, a remembered-2FA token legitimately issued to a customer with a given ID also matches an administrator with the same ID. An attacker who controls a customer account with a colliding ID, holds a valid remembered-2FA cookie for it, and already knows the target administrator's password can bypass the administrator's TOTP second factor and obtain an authenticated administrator session. This is a second-factor bypass only; it does not defeat password authentication. Fixed in 2.3.12.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
34
EG Risk 34/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
Severity75% × 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.3%
EPSS %ILE
19th
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 2FA Bypass via Namespace Confusion | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-2fa-bypass-via-namespace-confusion
github Patch Available🟡 PoC Available

Froxlor remembered-2FA account namespace confusion · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-9fq7-9w8p-c3qh

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100709?
CVE-2026-100709 is a high vulnerability published on September 26, 2026. Froxlor through 2.3.10 stores only a numeric user ID in remembered-2FA tokens (panel2fatokens) without recording the account namespace, and the remembered-token lookup during login is not constrained to the customer or administrator account type. Because customer and administrator IDs are allocated…
When was CVE-2026-100709 disclosed?
CVE-2026-100709 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-100709 actively exploited?
CVE-2026-100709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100709?
CVE-2026-100709 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100709?
A fix for CVE-2026-100709 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100709 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100709?

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

Book a Demo →Browse All CVEs