Skip to main content
Menu
CVEs

CVE

OpenCTI credential disclosure in logsWorkerConfig query

Holders of any OpenCTI connector or API bearer token can request Elasticsearch credentials in releases before 7.260706.0. Fixed in 7.260706.0.

CVE-2026-76823EUVD-2026-126657

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.260706.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Holder of a connector or API bearer token (any connector identity) Returned Elasticsearch credentials are valid and Elasticsearch is reachable from the attacker's network position

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

Summary

OpenCTI, an open source cyber threat intelligence platform from OpenCTI-Platform, has a flaw in its logsWorkerConfig query that returns Elasticsearch connection details, including usernames, passwords, and API keys, to anyone holding a connector API bearer token. An attacker with network access and a low-privilege login can use those credentials to read, change, or delete OpenCTI indices and audit history directly, bypassing the platform's own access controls, with impact limited by what the credentials allow and whether Elasticsearch is reachable.

Original description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0.

Who should check

Teams running OpenCTI platform before 7.260706.0 that issue connector or API bearer tokens and have Elasticsearch behind the platform

“OpenCTI exposes Elasticsearch connection details”

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.7/10CVSS 8.7
  • 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.

    Holder of a connector or API bearer token (any connector identity) Returned Elasticsearch credentials are valid and Elasticsearch is reachable from the attacker's network position
  • Upgrade to a fixed version: 7.260706.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-76823 (OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig), 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-76823 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260706.0
Fixed versions: 7.260706.0.
Conditions (all must be true for the bug to be hit):
- Holder of a connector or API bearer token (any connector identity) (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-mwfc-578p-fccc)
- Returned Elasticsearch credentials are valid and Elasticsearch is reachable from the attacker's network position (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-mwfc-578p-fccc)
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-76823 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76823 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-mwfc-578p-fccc
- https://github.com/OpenCTI-Platform/opencti/issues/16987
- https://github.com/OpenCTI-Platform/opencti/commit/02c1c9de3c6f87b45f6c6cb1a50d92210a018920
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260706.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-76823
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-76823"}.

Timeline

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

Affected versions

  • OpenCTI-Platform opencti

    fixed in 7.260706.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-76823

Is CVE-2026-76823 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?

Any holder of a connector or API bearer token can request raw Elasticsearch credential material from the OpenCTI GraphQL API. If the returned credentials are valid and Elasticsearch is reachable, the holder could read, modify or delete CTI records and audit history, bypassing OpenCTI access controls.Source: github.com, github.com

Which versions are affected by CVE-2026-76823?

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

Am I affected, and how do I check?

The affected product is OpenCTI, in releases before 7.260706.0. The exposure depends on holding a connector or API bearer token and on whether the returned Elasticsearch credentials are valid and reachable from the holder's network position. To check a deployment, look at the OpenCTI platform version.Source: github.com, github.com

How do I fix CVE-2026-76823?

Upgrade OpenCTI to 7.260706.0, the fixed version named in the advisory.Source: github.com, github.com