Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/pycti@6.9.1 |
| Type | pypi |
| Namespace | |
| Name | pycti |
| Version | 6.9.1 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | true |
| Next_non_vulnerable_version | 6.9.13 |
| Latest_non_vulnerable_version | 6.9.13 |
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-pdyx-j197-6faj |
| vulnerability_id |
VCID-pdyx-j197-6faj |
| summary |
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 6.9.7, an organization admin can escalate their privileges by adding a user from a different organization with higher privileges, to their own organization. This is due to incorrect ACL on userEdit relationAdd. This vulnerability is fixed in 6.9.7. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2026-44730, GHSA-q537-qhj4-wcjx, PYSEC-2026-167
|
| risk_score |
4.0 |
| exploitability |
0.5 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-pdyx-j197-6faj |
|
| 1 |
| url |
VCID-sa46-3cys-4ue3 |
| vulnerability_id |
VCID-sa46-3cys-4ue3 |
| summary |
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. In versions 6.6.0 through 6.9.12, there is a privilege escalation vulnerability that can be exploited by unauthenticated attackers to query the API as any existing user, including the default admin account. This issue has been fixed in version 6.9.13. As a workaround, the default admin can be disabled using the `APP__ADMIN__EXTERNALLY_MANAGED` configuration. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2026-27960, GHSA-6vvv-vmfr-xhrx, PYSEC-2026-119
|
| risk_score |
4.4 |
| exploitability |
0.5 |
| weighted_severity |
8.8 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-sa46-3cys-4ue3 |
|
|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-8vjm-472q-tbh4 |
| vulnerability_id |
VCID-8vjm-472q-tbh4 |
| summary |
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to version 6.9.1, the GraphQL mutations "IndividualDeletionDeleteMutation" is intended to allow users to delete individual entity objects respectively. However, it was observed that this mutation can be misused to delete unrelated and sensitive objects such as analyses reports etc. This behavior stems from the lack of validation in the API to ensure that the targeted object is contextually related to the mutation being executed. Version 6.9.1 fixes the issue. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2026-21886, GHSA-mhmx-j75v-2m6x, PYSEC-2026-117
|
| risk_score |
3.6 |
| exploitability |
0.5 |
| weighted_severity |
7.3 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-8vjm-472q-tbh4 |
|
|
| Risk_score | 4.4 |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/pycti@6.9.1 |