NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
Python API client for OpenCTI.
Latest stable
7.261109.3
Last release 10 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Most releases are documented
notes for 53 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
473 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
[backend] Changed vulnerabilities to vulnerability in security coverage vocabulary (#14676) by @MTorbay-Filigran in https://github.com/OpenCTI-Platfor…
content to all containers (#12530) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/15146Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260326.0...7.260401.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
[frontend] migrate react-grid-layout from v1 to v2 (#14955) by @ludovic in https://github.com/OpenCTI-Platform/opencti/pull/14959
['entity_type'] — regression from UI design system refactorx_opencti_negative field is not updated on upsertFull Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260318.0...7.260326.0
[frontend] fix “has” relationship in the vulnerabilities menu (#15036) by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/15038
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260317.0...7.260318.0
[backend] Add relationships to support vulnerability impact analysis (#14338) by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/14712
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260309.0...7.260317.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[backend] Fix dashboard export failing with dynamicRegardingOf filters (#14539, #14527) by @SamuelHassine in https://github.com/OpenCTI-Platform/openc
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260306.1...7.260309.0
[backend] fix OpenIDConnect when token are not valid JWT (#14839) by @xfournet in https://github.com/OpenCTI-Platform/opencti/pull/14840
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260306.0...7.260306.1
[doc] Fix typos, spelling mistakes, and grammar issues across docs/ folder by @Copilot in https://github.com/OpenCTI-Platform/opencti/pull/14627
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260305.0...7.260306.0
[frontend] add revoked to vulnerability edition form (#14106) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/14138
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260227.0...7.260305.0
docs: fix broken and incorrect links in documentation by @Copilot in https://github.com/OpenCTI-Platform/opencti/pull/14587
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/7.260224.0...7.260227.0
…of interest such as IOCs, threat actors, and vulnerabilities. It then enriches them with contextual cards displaying information already present in yo…
Dear community, we're excited to announce the launch of OpenCTI version 7 (7.260224.0) 🥳. We packed a lot of content on this release, and you will see important changes when using OpenCTI. This changes imply breaking changes.
[!IMPORTANT] Make sure you read the Breaking Change section at the bottom of this Release Note.
We are also introducing a new version naming convention matching our current ability to deliver releases. All of it make it worth to jump into the 7 digit 🙂
An LTS license allows Entreprise Edition users to stay on a LTS version for up to one year while receiving backported fixes for critical bugs and security issues. This licence is available to those of our On-Prem EE customers that might be tied by mandatory testing framework before going to production and that cannot match our current rythm of release.
We plan to release two LTS versions per year, giving you the option to align feature upgrades with a predictable twice‑yearly cycle.
You will find all information about the new Product Lifecycle of OpenCTI, including the new naming convention and the new Long Term Support offering, to this documentation page: https://docs.opencti.io/latest/administration/product-life-cycle/
🍬 Important to note, OpenCTI v7 introduces first steps towards a full new UI Design System, helping users to focus on what matters & reduce the cognitive load. From the start, you will see the difference!
This Major release is also full of improvements and new features, focusing on solving key pain points and unlocking new use cases, including:
In version 7 you will now be able to manage your SSO authentication mechanism via the OpenCTI UI (if your platform is Entreprise edition). This means that you will no longer need to update the configuration file (cross your fingers and hope) and reload the app to make changes. For all existing, your configurations will now be available via the UI and you can easily update and add new configurations as you require. This feature allows you be self sufficient, regardless of your deployment type (on-premise, SaaS).
[!IMPORTANT] As announced in December 2025, SSO will fall under Entreprise Edition license in Version 7. This will mean that any Community Edition platforms that migrate to version 7.0.0 and onwards will not be able to login using SSO configured previously. Moving SSO to the Enterprise Edition ensures that Filigran can sustainably maintain and continuously improve OpenCTI over the long term, while keeping investment strong in the Community Edition's core capabilities and responsibly managing the resources required to run a secure, high-quality open-source security platform.*
Almost all existing authentication methods will remain available in the UI. Configuration defined in files will still exist but migrated into the database and used for login. For migration details, authentication setup guidance, or troubleshooting, please refer to the links below.
We've redesigned API token management in OpenCTI for better control, security, and visibility.
What's changed
Existing tokens will continue working. We recommend reviewing tokens and transitioning to the new model for expiration controls and per-integration isolation.
Draft mode now supports granular capability controls, separate from platform-wide permissions.
This lets you restrict analysts to creating/updating data in drafts only, while others approve and validate—securing your platform and preventing unwanted changes.
This is the first step toward a validation workflow leveraging the draft workspace—more updates coming soon.
User visibility ensures no data leakage across organizations (available since 6.9.11)
The platform interface has been completely modernized with the V7 design system. This comprehensive redesign touches nearly every visual element you interact with: buttons, navigation, drawers, cards, labels, header, and many other components.
The goal? Create a lighter, cleaner interface that helps you work faster and with less visual noise.
Key improvements include:
This foundational redesign addresses previous challenges with visual complexity and outdated patterns, transforming the interface into a modern, efficient workspace that helps security teams focus on what matters most: Threat intelligence and Analysis.
We're introducing a browser extension that bridges any web page directly with your OpenCTI platform, eliminating the need to switch between your browser and OpenCTI when collecting threat intelligence.
How it works:
The extension is available for all major browsers: Firefox, Chrome, Edge, and Safari.
What this solves:
Analysts spend significant time browsing the web for threat intelligence across blogs, social media, advisories, and other sources. When they find relevant content, they face a tedious workflow: checking if the information already exists in OpenCTI, then manually creating objects and relationships, or converting the page to PDF for AI-assisted extraction.
This extension eliminates that friction. You stay on the page you're reading while the extension handles detection, enrichment, and ingestion. No more context switching, no more manual modeling, no more PDF conversions.
Community vs. Enterprise capabilities:
This extension transforms casual web browsing into an active intelligence collection workflow, making it effortless to capitalize on threat intelligence wherever you find it.
Playbooks can now remove specific labels and markings from entities, even if those values weren't added by the playbook itself. Previously, you could only remove values that were added within the same playbook execution, forcing manual cleanup for pre-existing labels or markings. This enhancement eliminates that limitation, allowing you to fully automate label and marking management without manual intervention.
You can now manually trigger playbooks on any entity type. A new "Enroll in playbook" button allows analysts to initiate automated workflows on-demand for specific entities. The interface displays available playbooks filtered by entity compatibility and trigger conditions, enabling one-click manual enrollment.
🔗 Connectors & Integrations (CE)
This milestone brings a significant expansion of the OpenCTI connector ecosystem, with new integrations and meaningful improvements across the board.
External Import
Enrichment
Third-Party Applications
Additionally, a large set of connectors has been added to the OpenCTI catalog with one-click deployment support: DNSTwist, Red Flag Domains, Microsoft Sentinel Incidents, Valhalla, MITRE Atlas, MalwareBazaar, Wiz Cloud Landscape, URLHaus, MISP, CPE, Recorded Future Enrichment, DISARM, Phishunt, AbuseIPDB Blacklist, MISP Feed, Dragos, Microsoft Defender Intel, Silobreaker, Microsoft Sentinel Intel, Intel471, and First EPSS.
For all the breaking changes, please have a look at our documentation: https://docs.opencti.io/latest/deployment/breaking-changes/?h=breaking+change.
api_token per user with a modern multi-token system featuring HMAC-hashed storage, expiration policies, per-token usage tracking, and capability-based access control. Connector-to-platform authentication is upgraded from raw token passthrough to JWT-based mutual authentication using platform-derived Ed25519 key pairs. All existing tokens are automatically migrated to the new system. After migration existing tokens will be encrypted and so no longer be retrievable by the user.User.api_token → User.api_tokens (type changed from String! to [ApiToken!]!)MeUser.api_token → MeUser.api_tokensmeTokenRenew mutation removedUserEditMutations.tokenRenew mutation removedMeUser.api_token → MeUser.api_tokenstoken_renew() method removed, replaced by create_token() / remove_token()- Env variable: APP__ENCRYPTION_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- Configuration file: app { encryption_key = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
content attribute to fintel (#12530) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/13702Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.22...7.260224.0
[backend/frontend] fix users visibility outside org segreg (#15158) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/15173
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.28...6.9.29
*No changelog for this release.*
No changelog for this release.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.27...6.9.28
[backend] backport of add sha256 to file metadata & use sha256 to check for duplicate upload (#14877) by @JeremyCloarec in https://github.com/OpenCTI-
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.26...6.9.27
[backend/frontend] Fix drawer visble for all users for 6.9.x (#14895) by @xfournet in https://github.com/OpenCTI-Platform/opencti/pull/14907
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.25...6.9.26
#### Enhancements: * #14891 : Update 3rd party dependencies on 6.9.x Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.24...6.9.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.24...6.9.25
[backend] Stream consumers should only return valid and ongoing consumers (#14816) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/1
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.23...6.9.24
[ci] do not produce prerelease build and docker images by @labo-flg in https://github.com/OpenCTI-Platform/opencti/pull/14618
Bug fixes
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.22...6.9.23
[backend] fix buggy history events (#14537) by @xfournet in https://github.com/OpenCTI-Platform/opencti/pull/14538
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.21...6.9.22
[Doc] Fix some typos by @romain-filigran in https://github.com/OpenCTI-Platform/opencti/pull/14520
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.20...6.9.21
*No changelog for this release.*
No changelog for this release.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.19...6.9.20
[backend/client] add ruleApplyAsync method (#11626) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/14034
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.18...6.9.19
*No changelog for this release.*
No changelog for this release.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.17...6.9.18
*No changelog for this release.*
No changelog for this release.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.16...6.9.17
[doc] openaev : correct link to openaev documentation by @MarineLeM in https://github.com/OpenCTI-Platform/opencti/pull/14118
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.15...6.9.16
[backend] Delete workbenches as other files when deleting an entity (#14301) by @SamuelHassine in https://github.com/OpenCTI-Platform/opencti/pull/143
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.14...6.9.15
[deps] Update dependency axios to v1.13.3 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/14250
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.13...6.9.14
[backend] Optimize JSON mapper memory usage and performance by @OctaveLaventure in https://github.com/OpenCTI-Platform/opencti/pull/14042
update_linked and delete_linked to draft (#14027) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/14028Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.12...6.9.13
[frontend] - (streams) Add 1 click deploy #14171 by @carinelebas in https://github.com/OpenCTI-Platform/opencti/pull/14208
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.11...6.9.12
This release introduces an issue: creating observables from the UI is no longer possible for several observable types. We advise to skip this version.
This release introduces an issue: creating observables from the UI is no longer possible for several observable types. We advise to skip this version.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.10...6.9.11
[frontend] Softwares list in Vulnerability details (#14139) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/14151
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.9...6.9.10
[backend] fix post filtering in elPaginate (#12701) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/13582
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.8...6.9.9
[deps] Update dependency body-parser to v2.2.2 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/13963
h1 size for fintel template preview (#13445) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/13998Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.7...6.9.8
[frontend] - (XTMHub - FreeTrials) Change redirection URL on learn more #13933 by @hervyt in https://github.com/OpenCTI-Platform/opencti/pull/13934
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.6...6.9.7
[frontend] Add has-label in relationship type filter values for knowledge widgets (#13837) by @Archidoit in https://github.com/OpenCTI-Platform/openct
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.5...6.9.6
[backend] Fix default dashboard for a group not taken into account (#11811) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.4...6.9.5
[backend] add stream type managers state tracking & state recovery (#13254) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/1325
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.3...6.9.4
[docs] Move github pages configuration (#13720) by @aHenryJard in https://github.com/OpenCTI-Platform/opencti/pull/13722
nx to octi/opencti repo (#13767) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/13743Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.2...6.9.3
[backend] Allow Array function in platform notifier (#13641) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/13655
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.1...6.9.2
[client] remove entirely deprecated methods (#13521) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/13617
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.9.0...6.9.1
Selective processing of entities (indicators, vulnerabilities, etc.) linked to specific PIR threats
Dear community, we're excited to announce the launch of OpenCTI 6.9.0! 🥳
This release focuses on solving key pain points and unlocking new use cases:
🌟 Make Priority Intelligence Requirements actionable (EE)
This allows teams to move beyond static threat lists and automatically respond to prioritized threats. Playbooks now execute targeted actions on the threats that matter most to your organization, reducing noise and accelerating response times to high-priority threats.
🤖 CTI driven assessment by integrating OpenCTI & OpenAEV (CE)
Security assessments can now be initiated from threat intelligence in OpenCTI, executed as simulations in OpenAEV, and results automatically imported back into OpenCTI as actionable gap analyses, within a new entity type Security coverage. Additionally, the creation and generation of security coverages can now be fully automated through our playbook engine. This capability, combined with the ability to trigger playbooks based on PIR events, enables you to automatically test your defense posture against threats identified as relevant for your organization.
This first implementation lays the foundation for transforming security assessments from manual processes into automated, threat-driven continuous validation
See details in our documentation.
💡 Draft Authorize members, to protect from unwanted modification or approval & Service Account bypass (CE)
To get an approval workflow for draft, the first step has been for us to enable Authorize Members on Drafts.
This way, when creating a draft manually or via file upload, you will be able to define authorized members at draft creation. This will ensure no user will be able to validate your draft on your behalf or even modify it without your consent.
This change required us to introduce another related change: Service Account now bypasses Authorize Members. The rationale behind this behavior is that Service Accounts should be able to enrich observables within a Draft, even if the draft has some Authorize Members enabled. To be clear: even if Service Accounts are not added as Authorized Members, they will get the Edit permission on the entity (draft, containers). This bypass is a default behavior that cannot be changed.
👤 Avoid some IOC to decay by introducing Decay Exclusion Rules (CE)
Some IOCs should never expire: for instance, Yara rules (or any detection rules) should never be revoked, to avoid having any tools like your SIEM, XDR, EDR… failing to detect a malicious IOC.
This is the purpose of Decay Exclusion Rules: you can filter on some IOC attributes to avoid having the matching IOCs fall under a decay rule. Ultimately, it prevents your IOCs from being automatically revoked.
Please be careful with the decay exclusion rules:
This feature should also help you if you use sources that also manage the lifecycle of your IOCs to avoid having 2 automated lifecycle management applied to your IOCs.
See details in our documentation.
🛡️ Framework to import data in the platform via Form Intake (CE)
Creating data in the platform can be a complex task, especially because:
As a result, we’re proud to introduce the Form Intake, to streamline the collection of threat intelligence data from external sources and stakeholders through structured forms.
Form intakes allow Administrators to define a form to specify which entities should be created and their needed mandatory fields. Also, Administrators can decide to automatically create relationships between entities created via the form and to create them as a draft or not. Additionally, the administrator can also label the entity or a specific field with a non-STIX label: this helps users not familiar with the platform and/or STIX to easily enter information in the platform.
This feature has proven (since available from 6.8.X) to be useful in the FIMI context, sharing communities such as ISACs or even Incident reporting.
Please provide as much feedback as possible on this feature, which should help you consolidate your database with consistent data.
🎨 UI & UX improvements (CE)
We keep working on the UI & UX part to provide a better experience to users.
💡 Many other improvements (new capa for playbooks, pattern matching for IOC…)
New observable to model SSH keys (CE): a new observable type, SSH key, has been introduced to help the modelization of SSH keys.
Email notifier improvements (CE): In the current implementation of our platform's mailer notifier, the content is generated in HTML format. However, the description field of an entity is formatted in Markdown by default. We introduce a solution for converting Markdown-formatted content to HTML to ensure consistency and proper rendering in the mail notifications.
Pattern matching filter (CE/EE): now also available for indicators in playbook, Live streams, CSV Feeds, and TAXII Collection.
Composer configuration (EE): for configuring a global HTTP/HTTPS proxy for connector network connectivity.
Change the capability linked to playbooks (EE): Playbook capability has been split into two capabilities:
This should help administrators in managing the RBAC with a fine-grained approach. See details in our documentation.
Change of capability for Delete & Merge knowledge (CE): After some feedback from the community, we have decided to change the capability to merge & delete, to ensure that that now merge and delete are now two specific capabilities.
Add original value in the logs (CE): Understanding the changes on an entity in detail is key in Cybersecurity. Therefore, we have improved data traceability by allowing users to view the detailed changes about an entity. Now, each line of the history of an entity is clickable, to give you more details about the initial value and the new one.
Send to template in playbook (EE): a new box “Send email from template has been introduced”, allowing you to send email using the templates defined in parameters/security. The end goal is to send an email to users, leveraging the HTML capabilities of the Email template Editor. This template only supports user-related variables and not entity-related variables. Additionally, this capability supports some dynamic variables, such as selecting “dynamic objects from the object in bundle” (organization), to extract directly the users from the organization triggering the playbook. More info on our documentation page.
Introduction of an onboarding email template (EE): for new platforms, an email template for user onboarding will be prepopulated, to help administrators save time in setting up their platform.
Support of CVSS 3.0 vector strings (CE): until now, platform only supported CVSS 3.1, but is now able to also support CVSS 3.0 vector strings.
🔗 Connectors & Integrations (CE)
Regarding connectors and integrations, this milestone brought several new connectors.
Import Connectors
Enrichment Connectors
Stream Connectors
Multiple connectors were added to the OpenCTI catalog, enabling one-click deployment (Feedly, Google TI, Recorded Future, CrowdStrike, VirusTotal, Mandiant)
[deps] Update vitest monorepo to v4 (major) by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/12940
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.16...6.8.17
[client] deprecate methods no longer working following removal of cache_index (#13521) by @JeremyCloarec in https://github.com/OpenCTI-Platform/openct…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.15...6.8.16
[backend] Introduce option to restrict the capacity to change the platform sender email (#13214) by @richard-julien in https://github.com/OpenCTI-Plat
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.14...6.8.15
[deps] Update rabbitmq Docker tag to v4.2.0 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/13159
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.13...6.8.14
[deps] Update dependency @graphql-codegen/typescript-resolvers to v5.1.2 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/13203
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.12...6.8.13
[frontend] Allow immediate deletion of managed connectors after stop request (#12474) by @maelv-filigran in https://github.com/OpenCTI-Platform/openct
yarn build fails with error TS2740, missing propertiesFull Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.11...6.8.12
[backend] change SSO absolute redirection (#13011) by @aHenryJard in https://github.com/OpenCTI-Platform/opencti/pull/13012
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.10...6.8.11
[backend] improve update message (#12051) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull/12978
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.9...6.8.10
Update aws-sdk-js-v3 monorepo to v3.913.0 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/10907
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.8...6.8.9
Update react monorepo by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/10918
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.7...6.8.8
⚠️ This release introduces an issue that can prevent the use of several connectors, please use 6.8.8 in that case.⚠️
⚠️ This release introduces an issue that can prevent the use of several connectors, please use 6.8.8 in that case.⚠️
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.6...6.8.7
One column per quarter.