Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to git-sources Browse API
-
ExploitSubmit crafted repo_url to internal/metadata target
-
ExecutionServer issues outbound request (SSRF)
-
ImpactReceive internal service response
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated session with access to the git-sources Browse API endpoint (CVSS PR:L; the vendor characterizes this as a privileged administrative function), plus the ability to control the repo_url argument processed in outboundTarget.ts. On pre-patch builds the server would resolve and connect to attacker-supplied internal targets including loopback, link-local, multicast, cloud-metadata and other special-use addresses, and would follow redirects and inherited proxy routing. Limiting factors: exploitation is NOT possible unauthenticated - the attacker must already possess credentials privileged enough to configure git sources; impact is limited to Low confidentiality (internal request issuance/response exposure) with no integrity or availability impact; and the vendor disputes that reaching private networks constitutes a boundary bypass since that reach is an intentional, documented feature. |
| Impact | Signals are mixed and lean toward moderate, targeted risk rather than a widespread emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity attack but explicitly requires privileges (PR:L) - so this is an authenticated SSRF, not an unauthenticated internet-facing bug, and confidentiality impact is only Low (VC:L) with no integrity or availability impact. A public exploit exists (VulDB gist) and the vector carries E:P (proof-of-concept), but there is no CISA KEV listing and no EPSS score was supplied, so there is no evidence of active or automated exploitation. Crucially, the vendor formally disputes the CVE, arguing that git-repository access is an intentional privileged administrative function that is designed to reach private LAN/VPC/VPN/CGNAT/IPv6-ULA targets, and that no privilege-boundary bypass by an unprivileged user was demonstrated - this directly conflicts with treating the behavior as a vulnerability and should be verified. The description itself states 'the presence of this vulnerability remains uncertain at this time,' reinforcing low confidence. Net: a legitimate defense-in-depth hardening target (the vendor shipped SSRF guards), but for most defenders this is a lower-priority, authenticated, low-impact issue rather than a critical exposure. |
| Exploit ScenarioDerived | An attacker who already holds low-privilege (operator/admin) credentials on a Sencho instance calls the git-sources Browse API endpoint and supplies a repo_url pointing at an internal address (e.g., a cloud metadata endpoint, loopback, or an internal-only service). The server dereferences the URL and issues an outbound request on the attacker's behalf, potentially returning internal data. A public proof-of-concept exists (VulDB gist), and the attack is performable remotely, but it is gated behind valid authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Server-side request forgery in Studio-Saelix Sencho up to 0.94.1 allows an authenticated user who can configure git sources to make the backend issue outbound HTTP/HTTPS connections to attacker-chosen internal addresses by manipulating the repo_url argument handled by outboundTarget.ts in the git-sources Browse API endpoint. Exploitation requires a valid session with git-source administration rights (CVSS 3.1 PR:L), and impact is limited to low confidentiality - internal request issuance and response exposure - with no integrity or availability effect; publicly available exploit code exists, though no confirmed in-the-wild activity has been reported. The vendor disputes the CVE characterization, arguing repository access to private LAN, VPC, VPN, CGNAT and IPv6 ULA ranges is an intentional administrative feature rather than a privilege-boundary bypass, while nonetheless shipping defense-in-depth hardening.
RemediationAI
Apply the upstream hardening: the fix is delivered as PR/commit 79b86ddcd4aefdd6941f098e35990ab397b13c72 (https://github.com/Studio-Saelix/sencho/pull/1877); no tagged patched release version was confirmed from the available data, so deployments should track the repository and validate that their build includes the undici-based DNS-pinning outbound client and the SSRF block list. Because the vendor disputes the issue, treat the fix as defense-in-depth rather than a fatal flaw: additionally restrict who can create or edit git sources to fully trusted administrators, since exploitation requires the PR:L privileged session, and monitor git-source configuration changes and unusual backend egress attempts. Network-level compensating controls include egress filtering/firewalling from the Sencho backend to loopback, link-local (169.254.0.0/16 and fe80::/10), CGNAT (100.64.0.0/10), IPv6 ULA (fc00::/7) and cloud metadata endpoints (169.254.169.254), though this will break the intentional private-LAN/VPN repository feature the vendor supports and must be scoped to the subnets that are genuinely untrusted; unsetting or ignoring HTTP_PROXY/HTTPS_PROXY environment variables and disabling redirect following at any intermediary reverse proxy limits pivot paths, with the trade-off of reduced operational flexibility. If the upstream change cannot be applied immediately, the most targeted interim mitigation is to block the git-sources Browse API for non-administrative users and to remove proxy-related environment variables from the Sencho process, accepting that legitimate internal repository browsing will be affected until the patched build is deployed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-918 server-side request forgery in Sencho's Node.js/TypeScript backend, where the git-sources Browse API endpoint passes a user-controllable repo_url into the outbound target construction logic in outboundTarget.ts without validating the destination host. On vulnerable builds the server would resolve and connect to loopback, link-local, multicast, cloud-metadata and other special-use addresses, and would also follow redirects and inherit proxy routing, letting the request be bounced to additional internal targets. The upstream fix (PR #1877, commit 79b86ddcd4aefdd6941f098e35990ab397b13c72) adds the undici HTTP client, validates and pins DNS resolution for both Git HTTPS and SSH connections, rejects loopback, link-local, multicast, selected special-use and metadata endpoints, disables redirects and inherited proxy routing, retains strict SSH host-key verification, and introduces a SENCHO_TRUSTED_PROXY_CIDRS setting plus an SENCHO_E2E_ALLOW_LOOPBACK_OUTBOUND test escape hatch. The affected product is tracked by CPE cpe:2.3:a:studio-saelix:sencho:*:*:*:*:*:*:*:*, indicating all catalogued Sencho releases; per the vendor, internal/LAN git hosting is a documented design feature, which is the basis for the disputed severity.
Know when Sencho gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Network-reachable, low-complexity SSRF requiring authenticated access to a privileged git-source feature (PR:L), yielding only limited internal-response confidentiality exposure (C:L) with no integrity or availability impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
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."
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
EUVD-2026-96730
GHSA-96p4-3cxg-89hc
NVD
CVE.org
EPSS
VulDB
Exploit-DB