CVE-2026-100717

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-87690 (ENISA EUVD) · GHSA-qjpj-j6j4-mcpf (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.9Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

froxlor is a server administration panel. In versions 2.3.10 and earlier, Validate::validateUrl rejects carriage return and line feed characters only in the path, query and fragment components returned by parse_url, and never inspects the userinfo (user:pass@) components. This is an incomplete fix for GHSA-c3p2. An authenticated low-privilege customer with subdomain-create rights (no admin or change_serversettings privilege required) can supply a subdomain redirect URL that carries a CR/LF payload in the userinfo portion (e.g. http://user%0areturn 200 "pwned";%[email protected]/). The value passes validation, survives IDNA encoding, and is written verbatim into the generated nginx or Apache vhost configuration, allowing the attacker to break out of the emitted directive and inject arbitrary web-server configuration lines. froxlor regenerates and reloads the web-server configuration as root, so the injected directives take effect server-wide and can hijack responses or read local files. The issue is fixed in version 2.3.12.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Nov 6, 2026
Fix named in the CVE record. Sources: github.
Web pageMentions a patch (unverified)

froxlor before 2.3.12 CRLF Injection via validateUrl userinfo | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.12-crlf-injection-via-validateurl-userinfo
GitHub advisoryMentions a patch (unverified)

Incomplete fix of GHSA-c3p2 - validateUrl rejects CR/LF only in path/query/fragment, not in the userinfo · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-gxx3-hwjc-h2gp

Vendor Advisories for CVE-2026-100717(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 14× in last 7d / 61× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 236 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:49 UTCEchelonGraph re-scored
  2. 2026-11-12 16:49 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  3. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-11-11 18:06 UTCEchelonGraph re-scored
  5. 2026-11-11 18:06 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  6. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-10 19:23 UTCEchelonGraph re-scored
  8. 2026-11-10 19:23 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  9. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-09 20:37 UTCEchelonGraph re-scored
  11. 2026-11-09 20:37 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  12. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-11-08 21:54 UTCEchelonGraph re-scored
  14. 2026-11-08 21:54 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  15. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-11-07 23:12 UTCEchelonGraph re-scored
  17. 2026-11-07 23:12 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  18. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-11-07 00:26 UTCEchelonGraph re-scored
  20. 2026-11-07 00:26 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  21. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-11-06 01:44 UTCEchelonGraph re-scored
  23. 2026-11-06 01:44 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  24. 2026-11-05 21:25 UTCOSV refresh
  25. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 75 more
  1. 2026-11-05 03:02 UTCEchelonGraph re-scored
  2. 2026-11-05 03:02 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  3. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-11-04 04:19 UTCEchelonGraph re-scored
  5. 2026-11-04 04:19 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  6. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-03 05:30 UTCEchelonGraph re-scored
  8. 2026-11-03 05:30 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  9. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-02 06:47 UTCEchelonGraph re-scored
  11. 2026-11-02 06:47 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  12. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-11-01 08:04 UTCEchelonGraph re-scored
  14. 2026-11-01 08:04 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  15. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-31 09:20 UTCEchelonGraph re-scored
  17. 2026-10-31 09:20 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-30 10:38 UTCEchelonGraph re-scored
  20. 2026-10-30 10:37 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  21. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-29 11:55 UTCEchelonGraph re-scored
  23. 2026-10-29 11:55 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  24. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-28 13:08 UTCEchelonGraph re-scored
  26. 2026-10-28 13:08 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  27. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-10-27 14:23 UTCEchelonGraph re-scored
  29. 2026-10-27 14:23 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  30. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  31. 2026-10-26 15:32 UTCEchelonGraph re-scored
  32. 2026-10-26 15:32 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  33. 2026-10-26 03:26 UTCEchelonGraph re-scored
  34. 2026-10-26 03:25 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  35. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  36. 2026-10-25 15:58 UTCEchelonGraph re-scored
  37. 2026-10-25 04:39 UTCEchelonGraph re-scored
  38. 2026-10-25 04:39 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  39. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  40. 2026-10-24 05:56 UTCEchelonGraph re-scored
  41. 2026-10-24 05:56 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  42. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-10-23 07:13 UTCEchelonGraph re-scored
  44. 2026-10-23 07:13 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  45. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-10-22 08:26 UTCEchelonGraph re-scored
  47. 2026-10-22 08:26 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  48. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-10-21 09:43 UTCEchelonGraph re-scored
  50. 2026-10-21 09:42 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  51. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-10-20 11:00 UTCEchelonGraph re-scored
  53. 2026-10-20 11:00 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  54. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-10-19 12:15 UTCEchelonGraph re-scored
  56. 2026-10-19 12:15 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  57. 2026-10-18 10:26 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  58. 2026-10-18 05:11 UTCEchelonGraph re-scored
  59. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-10-17 06:53 UTCEchelonGraph re-scored
  61. 2026-10-17 06:52 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  62. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-10-16 08:08 UTCEchelonGraph re-scored
  64. 2026-10-16 08:08 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  65. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-10-15 07:12 UTCEchelonGraph re-scored
  67. 2026-10-15 07:11 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  68. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  69. 2026-10-14 03:08 UTCEchelonGraph re-scored
  70. 2026-10-14 03:07 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  71. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  72. 2026-10-12 23:10 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9
  73. 2026-10-12 16:41 UTCEchelonGraph re-scored
  74. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  75. 2026-10-12 04:35 UTCGHSA enrichmentGHSA-qjpj-j6j4-mcpf · GitHub severity HIGH · GitHub CVSS 9.9

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100717?
CVE-2026-100717 is a critical-severity vulnerability; its CVE record was published on September 26, 2026. froxlor is a server administration panel. In versions 2.3.10 and earlier, Validate::validateUrl rejects carriage return and line feed characters only in the path, query and fragment components returned by parse_url, and never inspects the userinfo (user:pass@) components. This is an incomplete fix…
When was CVE-2026-100717 made public?
CVE-2026-100717 was made public on September 6, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-100717 actively exploited?
CVE-2026-100717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100717?
CVE-2026-100717 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100717?
The CVE record for CVE-2026-100717 names the fix: "The issue is fixed in version 2.3.12." The vendor advisories EchelonGraph has for CVE-2026-100717 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100717?

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

Book a Demo →Browse All CVEs