CVE-2026-121708 · Package
NO FIX YET · SEE WHAT TO DO
OpenCTI, a cyber threat intelligence platform, does not check that a user can access a draft workspace ID before serving it. Any authenticated user can read another user's unpublished intelligence and inject entities and relationships into that private workspace.
first public Aug 26, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any OpenCTI deployment before 7.260513.0 where more than one person has an account can expose draft workspace content across users. Single-user or fully trusted-account instances carry less risk but should still be upgraded.
Not affected if single-trusted-user, version-7.260513.0-or-later
Who cares opencti, self-hosted, threat-intel
7.260513.0 are affected.7.260513.0.OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260513.0, Draft Workspace identifiers are accepted without verifying that the authenticated user can access the referenced draft. Any authenticated user can enumerate draftWorkspaces, use a disclosed DRAFT_ID with draftWorkspaceEntities to read unpublished reports, descriptions, observables, and other staged intelligence, or place the identifier in the opencti-draft-id header and run mutations that inject entities and relationships into another user's private workspace. The flaw permits cross-user disclosure and tampering but does not cause a denial of service. This issue is fixed in version 7.260513.0.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.