CVE-2026-47381

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a user in one workspace could exercise another workspace's integration through the testConnection endpoint by supplying its ID, because the integration was fetched in a bypass scope and the caller's permission check matched any base in any workspace. This vulnerability is fixed in 2026.05.1.

CVSS v3
6.9
EG Score
6.9(medium)
EPSS
23.2%
KEV
Not listed

Published

June 5, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
Patch available. Sources: github.
github Patch Available

Cross-Workspace Integration Use in Connection Test · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-96fh-m4r8-6v9v

Vendor Advisories for CVE-2026-47381(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
nocodb—2026.05.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 19:58 UTCEG score recompute
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 20:38 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-03 17:29 UTCEG score recompute
  8. 2026-07-02 18:13 UTCEG score recompute
  9. 2026-07-01 18:09 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 18:10 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 10:51 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 11:35 UTCEG score recompute
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 12:20 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 13:03 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 11:20 UTCEG score recompute
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 7 more
  1. 2026-06-24 12:05 UTCEG score recompute▲ 6.90
  2. 2026-06-24 12:01 UTCNVD updateCVSS v3 → 6.9 · CVSS v4 → 6.9
  3. 2026-06-15 12:16 UTCEG score recompute
  4. 2026-06-14 23:18 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-12 23:12 UTCEPSS rescore
  7. 2026-06-05 16:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47381?
CVE-2026-47381 is a medium vulnerability published on June 5, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a user in one workspace could exercise another workspace's integration through the testConnection endpoint by supplying its ID, because the integration was fetched in a bypass scope and the caller's permission check…
When was CVE-2026-47381 disclosed?
CVE-2026-47381 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47381 actively exploited?
CVE-2026-47381 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47381?
CVE-2026-47381 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-47381?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47381, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47381

Explore →

Is Your Infrastructure Affected by CVE-2026-47381?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs