A vulnerability was found in Studio-Saelix Sencho up to 0.94.1. This affects an unknown part of the file /api/auth/login of the component Login Endpoint. Performing a manipulation of the argument X-Forwarded-For results in improper authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The patch is named 79b86ddcd4aefdd6941f098e35990ab397b13c72. To fix this issue, it is recommended to deploy a patch. The vendor confirms: "The login limiter relied on client-supplied X-Forwarded-For data without an explicit trusted-proxy boundary, allowing an attacker to rotate the apparent client address. The remediation now ignores forwarding headers by default, accepts them only from explicitly configured proxy CIDRs, and adds a separate failed-attempt limit keyed by normalized account identity."
CVE-2026-108522
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.3 from GitHub Security Advisory published 2026-10-11. A secondary CVSS source baseline 8.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 8.3
- EG Score
- 8.3HIGHhigh confidence
- EG Risk
- 38EG Risk 38/100
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 (value × EchelonGraph’s weight)Severity83% × 45%The EG Score, 8.3 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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
October 11, 2026
Last Modified
October 11, 2026
Advisory Details (4)
Auto-updated Oct 11, 2026GitHub - Studio-Saelix/sencho: Self-hosted Docker Compose management platform. For single or multi-host compose-first workflow. · GitHub
https://github.com/Studio-Saelix/sencho/commit 79b86ddcd4ae (Studio-Saelix/sencho)
Fix landed in Studio-Saelix/sencho commit 79b86ddcd4ae — awaiting tagged release
https://github.com/Studio-Saelix/sencho/commit/79b86ddcd4aefdd6941f098e35990ab397b13c72fix(security): harden authentication and outbound targets
Fix merged in Studio-Saelix/sencho PR #1877 on 2026-09-01 — awaiting tagged release
https://github.com/Studio-Saelix/sencho/pull/1877Sencho — Login rate-limit bypass via spoofed X-Forwarded-For header (CWE-290 / CWE-307) · GitHub
https://gist.github.com/jovair1994/839c8aaca1f37567cdd02e107a389f6aVendor Advisories for CVE-2026-108522(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 11× in last 7d / 11× 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 it from the CNA feed. 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). Most recent first.
- 2026-10-12 03:46 UTCGHSA enrichmentGHSA-5mq8-98f7-6q76 · GitHub CVSS 8.3
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 16:05 UTCEG score recompute
- 2026-10-11 16:05 UTCGHSA enrichmentGHSA-5mq8-98f7-6q76 · GitHub CVSS 8.3
- 2026-10-11 14:59 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 04:24 UTCEG score recompute
- 2026-10-11 04:22 UTCNVD updateCVSS v4 → 5.5
- 2026-10-11 04:08 UTCEG score recomputeFirst assessed: 8.3 HIGH
- 2026-10-11 04:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108522?
When was the CVE record for CVE-2026-108522 published?
Is CVE-2026-108522 actively exploited?
What is the CVSS score of CVE-2026-108522?
How do I remediate CVE-2026-108522?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108522
Is Your Infrastructure Affected by CVE-2026-108522?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.