CVE-2026-35210

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (26th 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
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: 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.260326.0, an authorization bypass vulnerability in OpenCTI allows any authenticated user with KNOWLEDGE_KNUPDATE permission to bypass Confidence Level validation and Object Marking restrictions by injecting the synchronized-upsert: true HTTP header, enabling attackers to downgrade confidence levels, remove security markings such as TLP:RED, manipulate relationships, and affect STIX object types including Indicators, ThreatActors, Malware, and Reports. This issue is fixed in version 7.260326.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
26th
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_commit, github_release, github, github_pr.
GitHub release Patch Available

Version 7.260326.0

Patch available: OpenCTI-Platform/opencti 7.260326.0

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

commit 134531ddf5ec (OpenCTI-Platform/opencti)

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

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

[backend] Fix use of synchronized-upsert header (#14015)

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

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

Authorization Bypass via `synchronized-upsert` HTTP Header Injection · Advisory · OpenCTI-Platform/opencti · GitHub

https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-36fr-4m54-94mj

Affected Packages

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 33× 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 139 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 40 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-35210?
CVE-2026-35210 is a high-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.260326.0, an authorization bypass vulnerability in OpenCTI allows any authenticated user with KNOWLEDGE_KNUPDATE permission to bypass Confidence Level validation and Object Marking…
When was the CVE record for CVE-2026-35210 published?
The CVE record for CVE-2026-35210 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-35210 actively exploited?
CVE-2026-35210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35210?
CVE-2026-35210 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-35210?
A fix for CVE-2026-35210 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-35210

Explore →

Is Your Infrastructure Affected by CVE-2026-35210?

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

Book a Demo →Browse All CVEs