Quick answers
- Is CVE-2026-47383 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47383 being exploited in the wild.
- How severe is CVE-2026-47383?
- High severity, with a CVSS score of 4, published 23 June 2026.
- Which products and versions are affected?
- nocodb (npm) <= 2026.05.0, ECOSYSTEM:introduced=0,fixed=2026.05.1.
- Is there a fix for CVE-2026-47383?
- Yes. nocodb (npm): upgrade to 2026.05.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47383 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47383?
- Check whether you run nocodb (npm) 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
- nocodb (npm): upgrade to 2026.05.1 or later
npm install nocodb@2026.05.1
Technical details
A stored Cross-Site Scripting (XSS) vulnerability existed in NocoDB's row comment feature due to a lack of server-side sanitization. While the client-side editor attempted to strip script tags, the raw comment body was persisted and later rendered in the expanded-form sidebar. Specifically, the application passed the comment data to the Tippy library's 'data-tooltip' attribute with 'allowHTML: true' enabled. An authenticated attacker with comment permissions could inject attribute-level payloads that execute when a victim hovers over the comment. This allows for the theft of authentication JWTs from localStorage. The issue is resolved in version 2026.05.1.
Affected products
- nocodb nocodb < 2026.05.1
Identifiers
- CVE-2026-47383
- GHSA-jf3g-4gwg-4h66
Timeline
- 2026-06-04: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: CVE published to NVD
- 2026-05-01: patched: Approximate date based on version number 2026.05.1