VU#382143: Lowcoder Query Library API contains cross-tenant authorization bypass allowing for data exfiltration
Affects lowcoderSource CERT/CC
Not known to be exploited · CVSS 8.8 High.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmlowcoderpkg:npm/lowcoderOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Administrators should restrict access to the vulnerable Query Library API endpoints until a security update is released. Limiting application access to trusted users and reviewing admin and dev role assignments can reduce exposure. Organizations should consider isolating tenants into separate Lowcoder instances to prevent cross-organization data access. Where possible, source code modifications should be made to enforce organization-level authorization checks on metadata retrieval and query execution endpoints.
Description
Lowcoder version 2.4.10 contains an authorization bypass vulnerability in its Query Library API that allows authenticated users with admin or dev roles to access and execute query data belonging to other organizations in a multi-tenant environment. The API lacks organization-level scope checks on metadata retrieval and query execution endpoints, enabling cross-tenant data exposure and potential misuse. No official patch or vendor statement is available. Administrators are advised to restrict access to the affected API endpoints and consider tenant isolation until a fix is released.