CVE-2026-100711

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 weekElevated
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: Elevated riskExposed services: Not assessed

A fix is available — apply it.

froxlor versions before 2.3.12 fail to invalidate existing panel sessions, API keys, and 2FA trust cookies when a user password is changed. Attackers holding hijacked sessions, valid API keys, or 2FA trust tokens retain full account access after password rotation, bypassing incident response actions.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/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%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 28, 2026

Advisory Details (2)

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

froxlor before 2.3.12 Authentication Bypass via Session Persistence | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-authentication-bypass-via-session-persistence
github Patch Available🟡 PoC Available

Password change does not invalidate existing panel sessions, API keys, or 2FA trust cookies · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-57wv-g7m3-hmff

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

Frequently asked(5)

What is CVE-2026-100711?
CVE-2026-100711 is a high vulnerability published on September 26, 2026. froxlor versions before 2.3.12 fail to invalidate existing panel sessions, API keys, and 2FA trust cookies when a user password is changed. Attackers holding hijacked sessions, valid API keys, or 2FA trust tokens retain full account access after password rotation, bypassing incident response…
When was CVE-2026-100711 disclosed?
CVE-2026-100711 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100711 actively exploited?
CVE-2026-100711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100711?
CVE-2026-100711 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-100711?
A fix for CVE-2026-100711 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100711 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100711?

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