CVE-2026-27960
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenCTI 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenCTI versions 6.6.0 through 6.9.12 contain an authentication bypass allowing unauthenticated attackers to query the API as any existing user, including the default administrator account, via improper session or token validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.9.0, < 6.9.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OpenCTI versionCheck the OpenCTI version from the platform UI (typically displayed in the footer or About section), or inspect the running container/image tag, or query the API version endpoint if availableAffected if The installed version is 6.9.0 or higher but lower than 6.9.13
-
Confirm version is within affected rangeCompare your identified version against the vulnerable range: >= 6.9.0 and < 6.9.13Affected if Your version falls within 6.9.0 to 6.9.12 inclusive
-
Verify default admin account statusCheck if the default admin account (typically with username admin or the account created during initial setup) still exists and is active in the OpenCTI user management interfaceAffected if The default admin account is present and enabled (the vulnerability allows unauthenticated impersonation of any existing user including admin)
-
Inspect admin account configurationReview the OpenCTI configuration for APP__ADMIN__EXTERNALLY_MANAGED setting - if set to false or not defined, the default admin account is internally managedAffected if APP__ADMIN__EXTERNALLY_MANAGED is not set to true, meaning the default admin account is active and internally managed
You are affected if your OpenCTI version is 6.9.0 or higher but lower than 6.9.13 AND the default admin account is present and enabled in the platform.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.9.13
Upgrade to OpenCTI version 6.9.13 or later. Alternatively, disable the default admin account by setting the APP__ADMIN__EXTERNALLY_MANAGED configuration option.
6.9.13 or later
- Backup your OpenCTI installation and database before upgrading
- Upgrade OpenCTI to version 6.9.13 or later
- Verify the upgrade was successful by checking the version number
- Test that authentication is working properly and the vulnerability is mitigated
- Alternatively, as a workaround, configure APP__ADMIN__EXTERNALLY_MANAGED to disable the default admin account
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data