CVE-2026-35211

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260401.0, the OpenCTI GraphQL API exposes a script filter operator in its FilterOperator enum that allows any authenticated user with the KNOWLEDGE capability to pass user-supplied Elasticsearch Painless script values directly into search queries without validation or sanitization, allowing computationally expensive scripts to consume cluster CPU resources and degrade or deny service for all users. This issue is fixed in version 7.260401.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Version 7.260401.0

Patch available: OpenCTI-Platform/opencti 7.260401.0

https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260401.0
GitHub commit

commit b134ccedf9e6 (OpenCTI-Platform/opencti)

Fix landed in OpenCTI-Platform/opencti commit b134ccedf9e6 — awaiting tagged release

https://github.com/OpenCTI-Platform/opencti/commit/b134ccedf9e68386723cb42197f8e1d60c3bdbd9
GitHub pull request

[backend] move script usage to internal_script and remove by default from API (#15267)(#15218)

Fix merged in OpenCTI-Platform/opencti PR #15284 on 2026-03-31 — awaiting tagged release

https://github.com/OpenCTI-Platform/opencti/pull/15284
GitHub advisoryMentions a patch (unverified)

Elasticsearch Painless Script Injection via GraphQL `script` filter operator allows authenticated user to exfiltrate data and cause DoS · Advisory · OpenCTI-Platform/opencti · GitHub

https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-qpp6-p693-rmm4

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pycti1.2.1 ... 7.260326.0 (404 versions)
  • every version up to 7.260401.0: fixed in 7.260401.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 136 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 37 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-12 16:12 UTCEG score recompute
  4. 2026-10-11 19:54 UTCEG score recompute
  5. 2026-10-11 17:07 UTCEG score recompute
  6. 2026-10-11 14:34 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-01 16:09 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-09-28 13:19 UTCEG score recompute
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-24 11:44 UTCEG score recompute
  25. 2026-09-23 06:03 UTCEG score recompute
Show 74 more
  1. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-09-18 05:40 UTCEG score recompute
  4. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-09-14 07:42 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-09-13 08:22 UTCEG score recompute
  11. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-09-12 03:30 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-09-05 22:42 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-08-30 07:28 UTCEG score recompute
  26. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-08-27 21:48 UTCEG score recompute
  29. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-08-26 04:44 UTCEG score recompute
  32. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-08-24 22:35 UTCEG score recompute
  34. 2026-08-23 23:14 UTCEG score recompute
  35. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  36. 2026-08-22 00:36 UTCEG score recompute
  37. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  38. 2026-08-21 01:17 UTCEG score recompute
  39. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-08-20 01:56 UTCEG score recompute
  41. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  42. 2026-08-18 22:27 UTCEG score recompute
  43. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  44. 2026-08-17 22:52 UTCEG score recompute
  45. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  46. 2026-08-16 23:33 UTCEG score recompute
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  48. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  49. 2026-08-16 00:14 UTCEG score recompute
  50. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-08-14 01:35 UTCEG score recompute
  52. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-08-13 02:16 UTCEG score recompute
  54. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-08-12 02:57 UTCEG score recompute
  56. 2026-08-11 03:37 UTCEG score recompute
  57. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  58. 2026-08-10 04:18 UTCEG score recompute
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-08-09 04:59 UTCEG score recompute
  61. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-08-08 05:40 UTCEG score recompute
  63. 2026-08-07 06:21 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  65. 2026-08-06 07:02 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  67. 2026-08-05 07:43 UTCEG score recompute
  68. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  69. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  70. 2026-08-04 08:21 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  72. 2026-08-02 09:01 UTCEG score recompute
  73. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  74. 2026-08-01 09:41 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-35211?
CVE-2026-35211 is a medium-severity vulnerability; its CVE record was published on July 8, 2026. OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260401.0, the OpenCTI GraphQL API exposes a script filter operator in its FilterOperator enum that allows any authenticated user with the KNOWLEDGE capability to pass user-supplied…
When was the CVE record for CVE-2026-35211 published?
The CVE record for CVE-2026-35211 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 13, 2026; the record at its source may have been updated since.
Is CVE-2026-35211 actively exploited?
CVE-2026-35211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35211?
CVE-2026-35211 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-35211?
A fix for CVE-2026-35211 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35211

Explore →

Is Your Infrastructure Affected by CVE-2026-35211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs