CVE-2026-21886
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. Prior to version 6.9.1, the GraphQL mutations "IndividualDeletionDeleteMutation" is intended to allow users to delete individual entity objects respectively. However, it was observed that this mutation can be misused to delete unrelated and sensitive objects such as analyses reports etc. This behavior stems from the lack of validation in the API to ensure that the targeted object is contextually related to the mutation being executed. Version 6.9.1 fixes the issue.
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 GraphQL API contains an Insecure Direct Object Reference (IDOR) vulnerability in the IndividualDeletionDeleteMutation. The mutation lacks proper authorization validation to verify that the targeted object is contextually related to the individual entity being deleted, allowing attackers to delete unrelated sensitive objects like analysis reports.
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.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm OpenCTI installationLocate the OpenCTI application directory or check running services (e.g., ps aux | grep opencti, docker ps, or systemd service status)Affected if OpenCTI is present in the environment
-
Identify installed OpenCTI versionCheck the version file, container image tag, or query the GraphQL API introspection for version info (typically at /api)Affected if Version is less than 6.9.1
-
Verify GraphQL API is accessibleConfirm the GraphQL endpoint is reachable (default: /api/graphql) and accepts mutationsAffected if GraphQL API accepts authenticated or unauthenticated requests
-
Confirm IndividualDeletionDeleteMutation existsQuery the GraphQL introspection (query { __schema { mutationType { name fields { name } } } }) to verify the mutation is exposedAffected if The mutation is present in the schema without contextual authorization checks
Environment is affected if OpenCTI version is below 6.9.1 and the GraphQL API with the IndividualDeletionDeleteMutation is accessible to the user.
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.1
Upgrade OpenCTI to version 6.9.1 or later, which implements contextual validation to ensure deleted objects are properly related to the mutation being executed.
6.9.1
- Identify the current OpenCTI version running in your environment
- Plan for a maintenance window to perform the upgrade
- Back up the OpenCTI database and configuration files before upgrading
- Upgrade OpenCTI to version 6.9.1 or later by following the official upgrade documentation at https://github.com/OpenCTI-Platform/opencti
- Verify the upgrade was successful by checking the version number in the UI or via API
- Test that the IndividualDeletionDeleteMutation now properly validates contextual relationships before allowing deletions
- Monitor system logs for any unauthorized deletion attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21886 — 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-21886 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