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.
CVE-2026-35210
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EPSS
- 18.6%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026Version 7.260326.0
Patch available: OpenCTI-Platform/opencti 7.260326.0
https://github.com/OpenCTI-Platform/opencti/releases/tag/7.260326.0commit 134531ddf5ec (OpenCTI-Platform/opencti)
Fix landed in OpenCTI-Platform/opencti commit 134531ddf5ec — awaiting tagged release
https://github.com/OpenCTI-Platform/opencti/commit/134531ddf5ecf741006b7f0870b7c36711b96540[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/14243Authorization Bypass via `synchronized-upsert` HTTP Header Injection · Advisory · OpenCTI-Platform/opencti · GitHub
https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-36fr-4m54-94mjWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-13 01:37 UTCEG score recompute
- 2026-07-12 13:05 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 00:32 UTCEG score recompute
- 2026-07-11 11:59 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 23:27 UTCEG score recompute
- 2026-07-10 10:53 UTCEG score recompute
- 2026-07-09 22:19 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 09:45 UTCEG score recompute
- 2026-07-08 21:12 UTCEG score recompute
- 2026-07-08 21:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639 · CWE-863
Frequently asked(5)
What is CVE-2026-35210?
When was CVE-2026-35210 disclosed?
Is CVE-2026-35210 actively exploited?
What is the CVSS score of CVE-2026-35210?
How do I remediate CVE-2026-35210?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-35210
Is Your Infrastructure Affected by CVE-2026-35210?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.