Skip to main content

CVE-2026-76823OpenCTI-Platform opencti insufficiently protected credentials

Schedule itHigh8.7EPSS not scored yet

CVE-2026-76823 is a insufficiently protected credentials in OpenCTI-Platform opencti, rated high (8.7 on CVSS 4.0).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Credentials are stored or sent in a way others can recover. The software reveals data to someone who should not see it.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade OpenCTI-Platform opencti to 7.260706.0 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.
  • Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
  • APIs that over-share. The flaw sits between internal data and whoever can read the response or log.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.
  • Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.

Questions to answer about your own systems

  • Where does OpenCTI-Platform opencti run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.