CVE
OpenCTI authorization bypass in draft workspaces
Affects OpenCTI Platform versions below 7.260513.0 on deployments that use Draft Workspaces. Fixed in 7.260513.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 7.260513.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected OpenCTI Platform versions below 7.260513.0 Deployments that use Draft Workspaces
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenCTI, an open source platform for managing cyber threat intelligence, has a broken authorization flaw in its draft workspaces. A remote attacker with a low-privilege authenticated account can read unpublished reports and other staged intelligence in another user's draft workspace, or inject entities and relationships into it.
Original description
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.
Who should check
Teams running OpenCTI Platform before 7.260513.0 where users share the instance and use Draft Workspaces for unpublished threat intelligence.
“< 7.260513.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected OpenCTI Platform versions below 7.260513.0 Deployments that use Draft WorkspacesUpgrade to a fixed version: 7.260513.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-121708 (OpenCTI: Broken Object Level Authorization (BOLA) for draft workspaces), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-121708 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260513.0
Fixed versions: 7.260513.0.
Conditions (all must be true for the bug to be hit):
- Affected OpenCTI Platform versions below 7.260513.0 (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-8jgr-3543-vfvv)
- Deployments that use Draft Workspaces (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-8jgr-3543-vfvv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-121708 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121708 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-8jgr-3543-vfvv
- https://github.com/OpenCTI-Platform/opencti/issues/15800
- https://github.com/OpenCTI-Platform/opencti/commit/eb173e7b428e16044ceb63fa8975d4616bdc5c3b
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260513.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-121708
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121708"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenCTI-Platform opencti
fixed in 7.260513.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121708
Is CVE-2026-121708 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can list other users' drafts, read their unpublished reports, descriptions and observables, and inject entities and relationships into another user's private draft workspace.Source: github.com
Which versions are affected by CVE-2026-121708?
opencti: before 7.260513.0.Source: cve.now feed data
Am I affected, and how do I check?
The issue affects OpenCTI Platform versions below 7.260513.0 in deployments that use Draft Workspaces. Compare the running platform version with 7.260513.0 and check whether Draft Workspaces are in use.Source: github.com
How do I fix CVE-2026-121708?
Upgrade the OpenCTI Platform to version 7.260513.0 or later, which is the listed fixed version.Source: github.com