CVE-2026-35036 | lin-snow Ech0 up to 4.2.7 Response Body /api/website/title server-side request forgery (GHSA-wc4h-2348-jc3p)

VDB-355613 · CVE-2026-35036 · GHSA-WC4H-2348-JC3P LIN-SNOW ECH0 UP TO 4.2.7 RESPONSE BODY /API/WEBSITE/TITLE SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.2 $0-$5k 2.71+ Summaryinfo A vulnerability classified as critical has been found in lin-snow Ech0 up to 4.2.7. Impacted is an unknown function of the file /api/website/title of the component Response Body Handler. The manipulation leads to server-side request forgery. This vulnerability is listed as CVE-2026-35036. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component. Detailsinfo A vulnerability was found in lin-snow Ech0 up to 4.2.7 and classified as critical. This issue affects some unknown processing of the file /api/website/title of the component Response Body Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is: Ech0 is an open-source, self-hosted publishing platform for personal idea sharing. Prior to 4.2.8, Ech0 implements link preview (editor fetches a page title) through GET /api/website/title. That is legitimate product behavior, but the implementation is unsafe: the route is unauthenticated, accepts a fully attacker-controlled URL, performs a server-side GET, reads the entire response body into memory (io.ReadAll). There is no host allowlist, no SSRF filter, and InsecureSkipVerify: true on the outbound client. Anyone who can reach the instance can force the Ech0 server to open HTTP/HTTPS URLs of their choice as seen from the server’s network position (Docker bridge, VPC, localhost from the process view). This vulnerability is fixed in 4.2.8. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-35036 since 03/31/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. Upgrading to version 4.2.8 eliminates this vulnerability. Productinfo Vendor lin-snow Name Ech0 Version 4.2.0 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 Website Product: https://github.com/lin-snow/Ech0/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.4 VulDB Meta Temp Score: 7.2 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Ech0 4.2.8 Timelineinfo 03/31/2026 CVE reserved 04/06/2026 +6 days Advisory disclosed 04/06/2026 +0 days VulDB entry created 04/06/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-wc4h-2348-jc3p Status: Confirmed CVE: CVE-2026-35036 (🔒) GCVE (CVE): GCVE-0-2026-35036 GCVE (VulDB): GCVE-100-355613 Entryinfo Created: 04/06/2026 19:34 Changes: 04/06/2026 19:34 (66) Complete: 🔍 Cache ID: 99:A6F:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸