CVE-2026-35210

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

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_pr

[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 Patch Available

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 rangeFixed inDependents
pycti1.2.1 ... 7.260318.0 (403 versions)7.260326.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 56× 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.

  1. 2026-08-27 21:48 UTCEG score recompute
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-27 01:21 UTCEG score recompute
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-26 04:44 UTCEG score recompute
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-24 22:13 UTCEG score recompute
  8. 2026-08-24 09:41 UTCEG score recompute
  9. 2026-08-23 06:24 UTCEG score recompute
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 05:17 UTCEG score recompute
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 03:57 UTCEG score recompute
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 01:56 UTCEG score recompute
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 20:44 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 16:47 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 15:16 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:44 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:39 UTCEG score recompute
Show 63 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 00:35 UTCEG score recompute
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-12 23:30 UTCEG score recompute
  5. 2026-08-12 13:50 UTCEPSS rescore
  6. 2026-08-11 22:25 UTCEG score recompute
  7. 2026-08-11 09:53 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-09 20:17 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 19:13 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 18:08 UTCEG score recompute
  14. 2026-08-06 17:04 UTCEG score recompute
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-06 04:32 UTCEG score recompute
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-05 03:29 UTCEG score recompute
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 14:56 UTCEG score recompute
  21. 2026-08-04 10:38 UTCEPSS rescore
  22. 2026-08-03 13:50 UTCEG score recompute
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-02 12:40 UTCEG score recompute
  25. 2026-08-02 02:27 UTCEPSS rescore
  26. 2026-08-01 11:36 UTCEG score recompute
  27. 2026-08-01 04:16 UTCEPSS rescore
  28. 2026-07-30 21:52 UTCEG score recompute
  29. 2026-07-30 16:28 UTCEPSS rescore
  30. 2026-07-30 08:22 UTCEG score recompute
  31. 2026-07-30 01:30 UTCEPSS rescore
  32. 2026-07-28 17:15 UTCEG score recompute
  33. 2026-07-27 15:38 UTCEG score recompute
  34. 2026-07-27 14:13 UTCEPSS rescore
  35. 2026-07-27 00:57 UTCEG score recompute
  36. 2026-07-26 14:54 UTCEPSS rescore
  37. 2026-07-26 14:54 UTCEPSS rescore
  38. 2026-07-26 12:23 UTCEG score recompute
  39. 2026-07-25 14:18 UTCEPSS rescore
  40. 2026-07-25 14:18 UTCEPSS rescore
  41. 2026-07-24 14:17 UTCEPSS rescore
  42. 2026-07-24 14:17 UTCEPSS rescore
  43. 2026-07-23 14:18 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 03:10 UTCEG score recompute
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-21 15:24 UTCEPSS rescore
  48. 2026-07-20 17:08 UTCEPSS rescore
  49. 2026-07-19 14:31 UTCEPSS rescore
  50. 2026-07-19 02:29 UTCEPSS rescore
  51. 2026-07-18 10:04 UTCEPSS rescore
  52. 2026-07-16 17:03 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 02:00 UTCEPSS rescore
  56. 2026-07-13 22:30 UTCEPSS rescore
  57. 2026-07-13 06:13 UTCEPSS rescore
  58. 2026-07-13 06:13 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-09 19:10 UTCEPSS rescore
  62. 2026-07-08 21:12 UTCEG score recompute
  63. 2026-07-08 21:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-35210?
CVE-2026-35210 is a high vulnerability 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 CVE-2026-35210 disclosed?
CVE-2026-35210 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35210 actively exploited?
CVE-2026-35210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-35210?
CVE-2026-35210 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-35210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs