CVE-2026-40346 | nocobase up to 2.0.36 server-side request forgery (GHSA-mvvv-v22x-xqwp)

VDB-358187 · CVE-2026-40346 · GHSA-MVVV-V22X-XQWP NOCOBASE UP TO 2.0.36 SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.0 $0-$5k 0.76+ Summaryinfo A vulnerability marked as critical has been reported in nocobase up to 2.0.36. Impacted is an unknown function. The manipulation leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2026-40346. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component. Detailsinfo A vulnerability was found in nocobase up to 2.0.36 and classified as critical. This issue affects an unknown code. 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: NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.37, NocoBase's workflow HTTP request plugin and custom request action plugin make server-side HTTP requests to user-provided URLs without any SSRF protection. An authenticated user can access internal network services, cloud metadata endpoints, and localhost. Version 2.0.37 contains a patch. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-40346 since 04/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. Upgrading to version 2.0.37 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 2853368243ed07339c62c548b7d475f4eeaada59 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name nocobase Version 2.0.0 2.0.1 2.0.2 2.0.3 2.0.4 2.0.5 2.0.6 2.0.7 2.0.8 2.0.9 2.0.10 2.0.11 2.0.12 2.0.13 2.0.14 2.0.15 2.0.16 2.0.17 2.0.18 2.0.19 2.0.20 2.0.21 2.0.22 2.0.23 2.0.24 2.0.25 2.0.26 2.0.27 2.0.28 2.0.29 2.0.30 2.0.31 2.0.32 2.0.33 2.0.34 2.0.35 2.0.36 License open-source Website Product: https://github.com/nocobase/nocobase/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.0 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 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: nocobase 2.0.37 Patch: 2853368243ed07339c62c548b7d475f4eeaada59 Timelineinfo 04/11/2026 CVE reserved 04/18/2026 +7 days Advisory disclosed 04/18/2026 +0 days VulDB entry created 04/18/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-mvvv-v22x-xqwp Status: Confirmed CVE: CVE-2026-40346 (🔒) GCVE (CVE): GCVE-0-2026-40346 GCVE (VulDB): GCVE-100-358187 Entryinfo Created: 04/18/2026 09:26 Changes: 04/18/2026 09:26 (69) Complete: 🔍 Cache ID: 99:A88:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸