CVE-2026-44730
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 6.9.7, an organization admin can escalate their privileges by adding a user from a different organization with higher privileges, to their own organization. This is due to incorrect ACL on userEdit relationAdd. This vulnerability is fixed in 6.9.7.
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 confidenceIn OpenCTI prior to 6.9.7, an organization admin can escalate their privileges by adding a user from a different organization with higher privileges to their own organization. This occurs due to incorrect Access Control List (ACL) enforcement on the userEdit relationAdd function, allowing cross-organization privilege escalation.
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.7CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Check installed OpenCTI versionAccess the OpenCTI admin interface and navigate to Settings > About, or run 'docker ps' to check the container version tag, or inspect the API version endpointAffected if The installed version is earlier than 6.9.7 (e.g., 6.9.6, 6.9.5, etc.)
-
Verify organization admin role is in useNavigate to Settings > Users and Organizations > Organizations. Review the list of organizations and identify if any have users assigned the 'Organization Admin' roleAffected if One or more organizations have users with Organization Admin privileges, creating potential targets for this ACL bypass
-
Audit cross-organization user membershipsQuery the users list and examine the 'organizations' field for each user. Specifically check if any user from Organization A is also a member of Organization B with elevated rolesAffected if Any user belongs to multiple organizations, particularly if they hold higher-privilege roles (like Admin) in one organization while being added to another by an Organization Admin
-
Review userEdit relationAdd ACL permissionsInspect the OpenCTI backend logs or API configuration for the userEdit mutation and relationAdd function. Check if Organization Admins can invoke this function on users outside their own organizationAffected if The ACL configuration permits Organization Admins to call relationAdd on users from different organizations, allowing unauthorized cross-org user assignment
You are affected if running OpenCTI version below 6.9.7 and your platform has Organization Admins with the ability to add users from other organizations to their own organization.
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.7
Upgrade to OpenCTI version 6.9.7 or later. Until then, restrict organization admin permissions and monitor for unauthorized user organization assignments.
6.9.7
- Upgrade OpenCTI to version 6.9.7 or later to remediate the privilege escalation vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44730 — 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-44730 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