Public dashboards bypass organization data segregation in OpenCTI
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-vmcw-q4pv-3548. Fix status from GitHub. Impact type from CWE-863.
Summary
OpenCTI from 6.8.10 before 7.260811.0 and OpenCTI LTS 7.260309.0 before 7.260309.0-lts.7 are affected. Public dashboards do not apply organization-based data segregation to widget queries on deployments with a platform organization (CWE-863). A user allowed to publish public dashboards can expose STIX data from other tenant organizations, and anyone with the public dashboard URL can read that data without authentication.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the GitHub advisory
### Summary Public dashboards did not apply organization-based data segregation when running widget queries. On multi-tenant deployments using a platform organization, a public dashboard could therefore return data from organizations that its creator has no access to. ### Impact On deployments where a platform organization is configured, any user allowed to publish a public dashboard (the `EXPLORE_EXUPDATE_PUBLISH` capability) could unintentionally expose STIX data from other tenant organizations. Anyone who can reach the public dashboard URL could read this data, without authentication. The exposed data is whatever matches the widget's own filters, and it extends beyond what the dashboard's creator is allowed to see. This breaks the data segregation guarantee between organizations. Single-tenant deployments, and deployments without a platform organization, are not affected. ### Patches The issue is fixed in OpenCTI **7.260811.0** and in the LTS release **7.260309.0-lts.7**. Public dashboard queries now evaluate organization membership for the dashboard's creator, as the other public-facing features already do. Users are advised to upgrade to a fixed version. ### Workarounds If upgrading is not immediately possible: - Disable or unpublish public dashboards on instances that use a platform organization. - Restrict the `EXPLORE_EXUPDATE_PUBLISH` capability to trusted users who are inside the platform organization.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | OpenCTI | >= 6.8.10, < 7.260811.0 | >= 7.260811.0 | Patch available | GHSA-vmcw-q4pv-3548 |
| — | OpenCTI LTS 7.260309.0 | < 7.260309.0-lts.7 | >= 7.260309.0-lts.7 | Patch available | GHSA-vmcw-q4pv-3548 |
- OpenCTI Vendor— Affected >= 6.8.10, < 7.260811.0 Fixed in >= 7.260811.0 Patch available GHSA-vmcw-q4pv-3548
- OpenCTI LTS 7.260309.0 Vendor— Affected < 7.260309.0-lts.7 Fixed in >= 7.260309.0-lts.7 Patch available GHSA-vmcw-q4pv-3548
Remediation
Upgrade OpenCTI to version 7.260811.0 or later, and upgrade OpenCTI LTS 7.260309.0 to 7.260309.0-lts.7 or later. If upgrading is not immediately possible, disable or unpublish public dashboards on instances that use a platform organization, or restrict the EXPLORE_EXUPDATE_PUBLISH capability to trusted users inside the platform organization.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · GHSA-vmcw-q4pv-3548 OpenCTI Fixed in >= 7.260811.0 Advisory →
- Fix · GHSA-vmcw-q4pv-3548 OpenCTI LTS 7.260309.0 Fixed in >= 7.260309.0-lts.7 Advisory →
Timeline
- 2026-11-13 Threatist record created from GHSA-vmcw-q4pv-3548
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences