Stream events in OpenCTI leak data through reverse_patch context
Key facts
- Attack vector
- Network
- Privileges required
- Low
- 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-692v-rpmx-72c8. Fix status from GitHub. Impact type from CWE-284.
Summary
OpenCTI before 7.260811.0 and OpenCTI LTS 7.260309.0 before 7.260309.0-lts.7 send the patch and reverse_patch context of live stream update events even after an edit changes an entity's visibility to the user. This is an improper access control flaw (CWE-284). A user with low privileges who can consume a live stream can read confidential data from previous or post-update states, bypassing marking-based restrictions. CISA KEV and public exploit data are not listed for this flaw.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the GitHub advisory
## Summary OpenCTI live streams decide whether a user can see an event by checking the user’s access rights (markings, organizations) against the entity’s current state. Update events also carry a patch and reverse_patch (the event context), which describe the entity’s previous state and the changes made. When an edit changes the visibility of an entity (for example, a marking change combined with a modification of the content), this context was still sent to the user. The user could therefore receive information from a state they were not allowed to see, such as previous values protected by the previous markings, or the post-update state of an entity they could no longer access. ## Impact A user with access to a live stream could obtain confidential data through the context of stream events, bypassing marking-based restrictions. The exposure is limited to data carried by the events of streams the user is allowed to consume. ## Patches The event context is now restricted according to the user’s access: - When an entity stops being visible to the user, the stream sends only the previous (already visible) state and no context. - When an entity becomes visible to the user, the event no longer includes the update context. - Update events are only sent if the user can access the markings related to the update. Fixed in: 7.260811.0 ([#17585](https://github.com/OpenCTI-Platform/opencti/pull/17585)) 7.260309.0-lts.7 for the 7.260309.0 LTS line ([#17637](https://github.com/OpenCTI-Platform/opencti/pull/17637)) The 7.260811.0 LTS line is not affected. Users should upgrade to one of these versions or later. ## Workarounds If you cannot upgrade immediately, limit stream access (the “Accessible for” setting of live streams and the associated users or service accounts) to trusted users only.
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 | < 7.260811.0 | >= 7.260811.0 | Patch available | GHSA-692v-rpmx-72c8 |
| — | OpenCTI LTS 7.260309.0 | < 7.260309.0-lts.7 | >= 7.260309.0-lts.7 | Patch available | GHSA-692v-rpmx-72c8 |
- OpenCTI Vendor— Affected < 7.260811.0 Fixed in >= 7.260811.0 Patch available GHSA-692v-rpmx-72c8
- OpenCTI LTS 7.260309.0 Vendor— Affected < 7.260309.0-lts.7 Fixed in >= 7.260309.0-lts.7 Patch available GHSA-692v-rpmx-72c8
Remediation
Upgrade OpenCTI to 7.260811.0 or later, or OpenCTI LTS 7.260309.0 to 7.260309.0-lts.7 or later. The 7.260811.0 LTS line is not affected. If you cannot upgrade immediately, limit stream access through the "Accessible for" setting of live streams and the associated users or service accounts to trusted users only.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · GHSA-692v-rpmx-72c8 OpenCTI Fixed in >= 7.260811.0 Advisory →
- Fix · GHSA-692v-rpmx-72c8 OpenCTI LTS 7.260309.0 Fixed in >= 7.260309.0-lts.7 Advisory →
Timeline
- 2026-11-13 Threatist record created from GHSA-692v-rpmx-72c8
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences