CVE-2026-76823: Infoleak
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 elasticsearchusername, elasticsearchpassword, elasticsearchapikey, 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 7.260706.0
Event History
Frequently Asked Questions
Who can retrieve the exposed Elasticsearch connection details?
Any holder of a connector API bearer token can invoke the affected logsWorkerConfig GraphQL query. The query is protected by the broad CONNECTORAPI capability rather than a narrower authorization check.
What could an attacker do with the retrieved credentials?
If the credentials remain valid and Elasticsearch is reachable, the caller may directly read, modify, or delete OpenCTI indices and audit history. The actual impact depends on the privileges assigned to those credentials and Elasticsearch network reachability.
Are application-level access controls still enforced after direct Elasticsearch access?
No. Direct Elasticsearch access using the returned credentials can bypass OpenCTI application-layer role, marking, organization, and audit controls.
What version fixes this issue?
Upgrade OpenCTI to version 7.260706.0 or later. Versions prior to 7.260706.0 are affected.