Skip to main content
Menu
CVEs

CVE

OpenCTI privilege escalation to global admin via group assignment

Only affects OpenCTI before 7.260624.0 where an Organization Administrator holds the VIRTUAL_ORGANIZATION_ADMIN and KNOWLEDGE_KNUPDATE capabilities. Fixed in 7.260624.0.

CVE-2026-63477EUVD-2026-126658

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.260624.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Attacker is an Organization Administrator: a non-global-admin user holding the VIRTUAL_ORGANIZATION_ADMIN capability plus KNOWLEDGE_KNUPDATE. OpenCTI versions before 7.260624.0 (the incomplete CVE-2026-44730 fix is in place).

Published
Last modified
Reference
Last checked
17/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

OpenCTI, an open source platform for managing cyber threat intelligence, has a flaw that lets a remote attacker with an organization administrator account and a low-privilege login escalate to global administrator. The attacker can add their own account to the built-in Administrators group and gain access across organizations, users, settings, markings, connectors, and ingestion.

Original description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260624.0, an Organization Administrator with VIRTUAL_ORGANIZATION_ADMIN and KNOWLEDGE_KNUPDATE can use organizationFieldPatch to replace the administered organization's grantable_groups without a SETTINGS_SETACCESSES authorization check. The administrator can add the built-in Administrators group to that grant scope and then bypass the grantable_groups guard added by the incomplete CVE-2026-44730 remediation to add their own account to Administrators. Membership grants the BYPASS capability after session cache refresh, escalating the tenant-scoped account to global administrator with access across organizations, users, settings, markings, connectors, and ingestion. This issue is fixed in version 7.260624.0.

Who should check

Teams running OpenCTI platform releases before 7.260624.0 where organization administrators hold VIRTUAL_ORGANIZATION_ADMIN and KNOWLEDGE_KNUPDATE.

Not fixed by: The CVE-2026-44730 guard alone does not close this; grantable_groups stayed writable.

“Organization Administrator (a non-global-admin user holding the virtual VIRTUAL_ORGANIZATION_ADMIN capability plus the common KNOWLEDGE_KNUPDATE capability)”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Attacker is an Organization Administrator: a non-global-admin user holding the VIRTUAL_ORGANIZATION_ADMIN capability plus KNOWLEDGE_KNUPDATE. OpenCTI versions before 7.260624.0 (the incomplete CVE-2026-44730 fix is in place).
  • Upgrade to a fixed version: 7.260624.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-63477 (OpenCTI: Organization administrator can escalate to global administrator via unvalidated `grantable_groups` write (incomplete fix of…), 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-63477 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260624.0
Fixed versions: 7.260624.0.
Conditions (all must be true for the bug to be hit):
- Attacker is an Organization Administrator: a non-global-admin user holding the VIRTUAL_ORGANIZATION_ADMIN capability plus KNOWLEDGE_KNUPDATE. (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-2j49-g9h3-75hp)
- OpenCTI versions before 7.260624.0 (the incomplete CVE-2026-44730 fix is in place). (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-2j49-g9h3-75hp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-63477 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63477 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-2j49-g9h3-75hp
- https://github.com/OpenCTI-Platform/opencti/issues/16747
- https://github.com/OpenCTI-Platform/opencti/commit/6abd3b300ced390d87af01209dd6d59ebfe59d4c
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260624.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-63477
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-63477"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • OpenCTI-Platform opencti

    fixed in 7.260624.0

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63477

Is CVE-2026-63477 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: cve.now feed data

What does this mean?

An Organization Administrator can write the grantable_groups setting without validation and escalate to global administrator with BYPASS capability. That grants read and write over every organization's data, all users, roles, capabilities, settings, markings (TLP), connectors and ingestion.Source: github.com

Which versions are affected by CVE-2026-63477?

opencti: before 7.260624.0.Source: cve.now feed data

Am I affected, and how do I check?

OpenCTI versions before 7.260624.0 are affected, and the bug needs a non-global-admin user holding VIRTUAL_ORGANIZATION_ADMIN plus KNOWLEDGE_KNUPDATE. To check a deployment, look at the OpenCTI version in the platform and at which roles hold those two capabilities.Source: github.com

How do I fix CVE-2026-63477?

Upgrade OpenCTI to 7.260624.0 or later, which is the version that fixes this issue. The earlier CVE-2026-44730 fix was incomplete, so an install that only has that fix is still before 7.260624.0.Source: github.com