A vulnerability was determined in Studio-Saelix Sencho up to 0.94.1. This vulnerability affects unknown code of the file outboundTarget.ts of the component git-sources Browse API Endpoint. Executing a manipulation of the argument repo_url can lead to server-side request forgery. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The presence of this vulnerability remains uncertain at this time. This patch is called 79b86ddcd4aefdd6941f098e35990ab397b13c72. It is advisable to implement a patch to correct this issue. The vendor explains: "Git repository access is an intentional, privileged administrative function. Sencho explicitly supports repositories hosted on private LAN, VPC, VPN, CGNAT, and IPv6 ULA networks. The report does not demonstrate a privilege-boundary bypass or access by an unprivileged user. We therefore dispute the CVE characterization of this behavior. As defense in depth, we have nevertheless hardened repository access. Git HTTPS and SSH connections now validate and pin DNS resolution, reject loopback, link-local, multicast, selected special-use and metadata targets, disable redirects and inherited proxy routing, and retain strict SSH host-key verification."
CVE-2026-108523
“—” beside the score: it is equal to the CVSS score beside it.
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-10-11. A secondary CVSS source baseline 4.3; sources differ by 0.0.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMhigh confidence
- EG Risk
- 35EG Risk 35/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)Severity43% × 45%The EG Score, 4.3 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (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: 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.3%
- EPSS %ILE
- 16th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
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 public PoC (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.
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
October 11, 2026
Last Modified
October 13, 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 — SSRF via POST /api/git-sources/browse due to missing host/IP validation (CWE-918) · GitHub
https://gist.github.com/jovair1994/93446c14d30a16313e830490d71bbd1dVendor Advisories for CVE-2026-108523(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 17× in last 7d / 17× 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-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-13 13:56 UTCGHSA enrichmentGHSA-96p4-3cxg-89hc · GitHub severity LOW · GitHub CVSS 4.3
- 2026-10-13 13:25 UTCEG score recompute
- 2026-10-13 13:25 UTCGHSA enrichmentGHSA-96p4-3cxg-89hc · GitHub severity LOW · GitHub CVSS 4.3
- 2026-10-13 13:24 UTCNVD updateCVSS v4 → 2.1
- 2026-10-13 13:10 UTCEG score recompute
- 2026-10-13 13:10 UTCGHSA enrichmentGHSA-96p4-3cxg-89hc · GitHub severity LOW · GitHub CVSS 4.3
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 14:59 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-11 05:22 UTCEG score recompute
- 2026-10-11 05:22 UTCNVD updateCVSS v4 → 2.1
- 2026-10-11 04:34 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
- 2026-10-11 04:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108523?
When was the CVE record for CVE-2026-108523 published?
Is CVE-2026-108523 actively exploited?
What is the CVSS score of CVE-2026-108523?
How do I remediate CVE-2026-108523?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108523
Is Your Infrastructure Affected by CVE-2026-108523?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.