Skip to main content
Menu
CVEs

CVE

OpenCTI password brute-forcing via unthrottled login endpoint

Affects OpenCTI versions before 7.260428.0, where the token GraphQL login mutation has no rate limiting. Fixed in 7.260428.0.

CVE-2026-104840EUVD-2026-126654

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

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

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 7.260428.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.260428.0.

Published
Last modified
Reference
Last checked
26/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

OpenCTI, the open source cyber threat intelligence platform from OpenCTI-Platform, lacks rate limiting on its primary login token endpoint, so an attacker can reach it remotely, without logging in, and guess passwords for a chosen account at high speed. If a credential is recovered, the attacker can access that account's threat intelligence data and the operations it is permitted to perform.

Original description

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260428.0, the token GraphQL mutation used for primary login has no endpoint-specific rate limit, while the global Express limiter defaults to permitting 10,000 requests in a one-second window. An unauthenticated remote attacker can make password guesses at network speed against a chosen user account and, if a credential is recovered, access the account's threat-intelligence data and permitted operations. This issue is fixed in version 7.260428.0.

Who should check

Teams running OpenCTI-Platform opencti versions before 7.260428.0, where the primary login token mutation has no endpoint rate limit.

“The token GraphQL mutation (primary login endpoint) lacks any rate limiting”

github.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.260428.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-104840 (OpenCTI: No rate limiting on authentication endpoint allows credential brute-forcing), 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-104840 (entry last updated 2026-11-16):
Affected:
- OpenCTI-Platform opencti: fixed in 7.260428.0
Fixed versions: 7.260428.0.
Conditions (all must be true for the bug to be hit):
- The token GraphQL mutation (primary login endpoint) has no rate limiting in OpenCTI versions before 7.260428.0. (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-74jw-q47r-q5pv)
- Only the global Express rate limiter applies, which defaults to 10,000 requests per second. (source: https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-74jw-q47r-q5pv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-104840 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104840 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-74jw-q47r-q5pv
- https://github.com/OpenCTI-Platform/opencti/issues/15666
- https://github.com/OpenCTI-Platform/opencti/issues/15735
- https://github.com/OpenCTI-Platform/opencti/commit/8599366319532dbdc1cfd553c55a518ad146c3df
- https://github.com/OpenCTI-Platform/opencti/commit/d7dfab4c264e36addf215b413924cb77f0827070
- https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260428.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-104840
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-104840"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • OpenCTI-Platform opencti

    fixed in 7.260428.0

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository

Corrections

None so far.

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

Questions about CVE-2026-104840

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

The token GraphQL mutation, OpenCTI's primary login endpoint, has no rate limiting, so repeated login attempts are not throttled. Only the global Express rate limiter applies, which defaults to 10,000 requests per second. A successful password guess gives full access to that account's threat intelligence data.Source: github.com

Which versions are affected by CVE-2026-104840?

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

Am I affected, and how do I check?

OpenCTI versions before 7.260428.0 are affected, and the issue is in the token GraphQL login mutation. To check, compare the OpenCTI version of your deployment with 7.260428.0.Source: github.com

How do I fix CVE-2026-104840?

Upgrade OpenCTI to 7.260428.0 or later, which is the fixed version listed for this vulnerability.Source: github.com