Quick answers
- Is CVE-2026-113359 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113359 being exploited in the wild.
- How severe is CVE-2026-113359?
- Medium severity, with a CVSS score of 4.3, published 20 October 2026.
- Which products and versions are affected?
- Baserow before 2.3.0.
- Is there a fix for CVE-2026-113359?
- Yes: fixed in Baserow 2.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113359 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113359?
- Check whether you run Baserow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Baserow 2.3.0
Technical details
The unique_row_values API endpoint in Baserow before 2.3.0 lacks proper authorization validation, allowing an authenticated attacker to retrieve up to 100 distinct cell values per field from workspaces they do not belong to. By sequentially enumerating field IDs, attackers can extract sensitive information from tables across the application. The vulnerability requires network access and valid authentication credentials.
Affected products
- Baserow Baserow before 2.3.0
Timeline
- 2026-10-20: disclosed