# CVE-2026-27960: OpenCTI privilege escalation and unauthenticated access via default admin account

> Unauthenticated attackers can escalate privileges and access the API as any user, including the default admin, in OpenCTI.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-6vvv-vmfr-xhrx, PYSEC-2026-119

## What is CVE-2026-27960?

CVE-2026-27960 is a critical authentication bypass vulnerability in OpenCTI-Platform opencti, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. In versions 6.6.0 through 6.9.12, there is a privilege escalation vulnerability that can be exploited by unauthenticated attackers to query the API as any existing user, including the default admin account. This issue has been fixed in version 6.9.13. As a workaround, the default admin can be disabled using the `APP__ADMIN__EXTERNALLY_MANAGED` configuration.

Weakness: CWE-287 (Improper Authentication)

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

1 open source package ship an affected version, including pycti. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pycti` | PyPI | From 6.9.0 | 6.9.13 |

Products: Citeum Opencti.

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

Upgrade pycti to 6.9.13 or later.

## Is CVE-2026-27960 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27960 exists.

Public exploit code:

- OpenCTI Authentication Bypass and Notifier EJS Remote Code Execution (metasploit)
- OpenCTI < 6.9.13 - Authentication Bypass via User Impersonation (nuclei): http/cves/2026/CVE-2026-27960.yaml

## Other vulnerabilities in OpenCTI-Platform opencti

- [CVE-2026-39980](https://insights.sbomify.com/CVE-2026-39980/): OpenCTI affected by RCE via notifier template (critical 9.1)
- [CVE-2025-24977](https://insights.sbomify.com/CVE-2025-24977/): OpenCTI has remote code execution and sensitive secrets exposed through web hook (critical 9.1)
- [CVE-2024-26139](https://insights.sbomify.com/CVE-2024-26139/): OpenCTI Authenticated Privilege Escalation (high 8.3)
- [CVE-2024-45404](https://insights.sbomify.com/CVE-2024-45404/): OpenCTI's lack of Rate Limit lead to OTP brute forcing (high 8.1)
- [CVE-2026-21887](https://insights.sbomify.com/CVE-2026-21887/): OpenCTI has a Semi-Blind SSRF via Unvalidated External URL in Data Ingestion Feature (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27960 and fix it if it is affected.

What it is: CVE-2026-27960 is a critical authentication bypass vulnerability in OpenCTI-Platform opencti, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27960 exists.

Affected packages and fixed versions:
- pycti (PyPI): affected from 6.9.0; fixed in 6.9.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27960/ (Markdown: https://insights.sbomify.com/CVE-2026-27960/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27960
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27960
- OSV: https://osv.dev/vulnerability/CVE-2026-27960

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27960/
Summaries are generated and may contain mistakes; the official description above is the record.