Skip to main content
Menu
CVEs

CVE

OpenCTI sensitive data exposure in GraphQL via HTTP GET

CVE-2026-114505EUVD-2026-126661

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

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 7.260722.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.260722.0.

Published
Last modified
Reference
Last checked
23/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

OpenCTI, an open source platform for managing cyber threat intelligence, accepts GraphQL query requests sent over HTTP GET, which places the full query and its arguments in the URL. Remotely, without logging in, an attacker who can read server or proxy logs, browser history, or shared caches could recover other users' sensitive search queries and filters, though mutations and code execution are not possible this way.

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

Original description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260722.0, the GraphQL endpoint accepts query operations over HTTP GET because CSRF prevention is disabled (csrfPrevention: false), placing the complete GraphQL query and its arguments in the request URL. Server and reverse-proxy logs, browser history, and shared caches can retain sensitive filters, marking-restricted identifiers, and investigation search arguments, allowing a person with access to those records to recover legitimate users' query contents. GraphQL mutations are not accepted over GET, and the issue does not permit code execution. This issue is fixed in version 7.260722.0.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.260722.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-114505 (OpenCTI: Acceptance of GraphQL Operations via HTTP GET Method), 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-114505 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260722.0
Fixed versions: 7.260722.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-114505 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114505 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-fh34-63w7-r782
- https://github.com/OpenCTI-Platform/opencti/issues/16998
- https://github.com/OpenCTI-Platform/opencti/commit/52af09cb1deba9d1196e8760ae859ce591dd667b
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260722.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-114505
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-114505"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • OpenCTI-Platform opencti

    fixed in 7.260722.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-114505

Is CVE-2026-114505 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

Which versions are affected by CVE-2026-114505?

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

How do I fix CVE-2026-114505?

Upgrade to a fixed version: 7.260722.0.Source: cve.now feed data