CVE-2026-108521
Received Received - Intake

Server-Side Request Forgery in Studio-Saelix Sencho

Publication date: 2026-10-11

Last updated on: 2026-10-11

Assigner: VulDB

Description
A vulnerability has been found in Studio-Saelix Sencho up to 0.97.1. Affected by this issue is the function isValidRemoteUrl of the file backend/src/utils/validation.ts of the component Add Remote Node API Endpoint. Such manipulation leads to server-side request forgery. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor confirms: "The node API URL could be configured by an authenticated user with node-management permission and used to initiate server-side requests. [T]he report demonstrates server-side request capability but not arbitrary internal response exfiltration."

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-11
Last Modified
2026-10-11
Generated
2026-10-11
AI Q&A
2026-10-11
EPSS Evaluated
N/A
NVD
CVE-2026-108521
EUVD
EUVD-2026-96728

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Studio-Saelix Sencho 0.97.0
Studio-Saelix Sencho 0.97.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-108521 is a Server-Side Request Forgery (SSRF) vulnerability in Studio-Saelix Sencho versions up to 0.97.1. It affects the isValidRemoteUrl function in backend/src/utils/validation.ts, allowing authenticated users with node-management permissions to manipulate the node API URL. This can force Sencho to initiate server-side requests to arbitrary internal hosts and ports, bypassing intended protections.

Detection Guidance

To detect this SSRF vulnerability in Sencho, monitor network traffic for outbound connections to localhost, internal IPs, or cloud metadata endpoints (e.g., 169.254.169.254). Check logs for POST requests to /api/nodes with URLs containing nip.io, IPv4-mapped IPv6 literals, or unusual hostnames. Use tools like tcpdump or Wireshark to inspect traffic from the Sencho container.

Impact Analysis

An attacker could exploit this to access internal services, exfiltrate sensitive data like IAM credentials, or interact with cloud metadata services (e.g., AWS, Azure). The impact includes unauthorized data access, potential service disruption, and increased risk of further attacks within the internal network.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating GDPR's data protection principles and HIPAA's security requirements for safeguarding protected health information. Non-compliance may result in legal penalties, reputational damage, and loss of trust.

Mitigation Strategies

Immediately disable the 'add remote node' feature in Sencho if not critical. Update to the latest version if a patch is available. Restrict node:manage permissions to trusted users only. Implement network-level controls to block outbound connections to localhost, internal IPs, and cloud metadata endpoints. Review and sanitize all URL inputs in the isValidRemoteUrl function.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-108521. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart