Comparison Overview
BLACKBIRD.AI
BLACKBIRD.AI
New York, 10111, US
Last Update: 24/06/2026
BLACKBIRD.AI protects organizations from narrative attacks that cause financial, operational, and reputational harm. Our Constellation AI-driven Narrative Intelligence Platform identifies key narratives that impact your organization/industry, the influence behind them, ...
IDEMIA
2 place Samuel Champlain, Courbevoie, 92400, FR
Last Update: 01/04/2026
IDEMIA Secure Transactions (IST) is a leading provider of payment, connectivity, and cybersecurity solutions, serving billions of people worldwide. With decades of expertise in cryptography and credential issuance, IST is trusted by over 2000 financial institutions, mob...
Compliance Ranges Comparison
BLACKBIRD.AI
IDEMIA
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
BLACKBIRD.AI has 6.54% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for IDEMIA in 2026.
Incident History - BLACKBIRD.AI (X = Date, Y = Severity)
BLACKBIRD.AI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IDEMIA (X = Date, Y = Severity)
IDEMIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BLACKBIRD.AI
IDEMIA
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.