CERT/CC Warns of Cross-Tenant Lowcoder Query Access

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

CERT/CC published VU#382143 for Lowcoder 2.4.10 Query Library API in multi-tenant deployments. CERT/CC documented missing organization-scope checks that permit cross-tenant query metadata access and query execution with another tenant's data source. Match the exact preconditions, follow the record-specific remediation, validate affected workflows, and retain evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory Lowcoder 2.4.10 multi-tenant systems, Query Library APIs, self-signup settings, admin and dev roles, and data-source credentials; restrict the affected endpoints; isolate tenants; review access; and track a supported vendor fix.

Open the authoritative advisory

Last verified: 2026-10-15 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeLowcoder 2.4.10 Query Library API in multi-tenant deployments
AdvisoryVU#382143
CVECVE-2026-16753
Authoritative release date2026-10-13 00:00:00 UTC
Authority revision date2026-10-14 16:02:00 UTC
Affected versionsLowcoder 2.4.10 where authenticated admin or dev users can reach Query Library metadata and execution endpoints across organizations; self-signup defaults can increase exposure.
Fixed versionNo official security update was available; restrict the affected Query Library endpoints, limit trusted users and roles, isolate tenants, or add organization-level authorization checks
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

CERT/CC documented missing organization-scope checks that permit cross-tenant query metadata access and query execution with another tenant's data source.

What To Validate Now

  1. Inventory. Locate Lowcoder 2.4.10 Query Library API in multi-tenant deployments deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: Lowcoder 2.4.10 where authenticated admin or dev users can reach Query Library metadata and execution endpoints across organizations; self-signup defaults can increase exposure. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply No official security update was available; restrict the affected Query Library endpoints, limit trusted users and roles, isolate tenants, or add organization-level authorization checks through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The compensating controls are not a patch. Source-code changes create a locally maintained fork and require independent authorization, regression, upgrade, and rollback testing. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.