Comparison Overview
Torq
Torq
Rua Bela Cintra 755, São Paulo, 01415-001, BR
Last Update: 09/06/2026
Somos o hub de inovação da Sinqia, e a nossa função é fomentar a inovação no mercado financeiro! O Torq Ventures é o nosso programa de Corporate Venture Capital (CVC), que acelera a estratégia de Open Innovation dentro e fora da companhia, fortalecendo o nosso relacion...
Allianz Technology
Dieselstraße 8, Unterföhring, Bavaria, DE, 85774
Last Update: 29/03/2026
With its headquarters in Munich, Germany, Allianz Technology is Allianz's global IT service provider and delivers IT solutions that drive the group's digitalization. With more than 11,000 employees in more than 20 countries around the world, Allianz Technology is tasked...
Compliance Ranges Comparison
Torq
Allianz Technology
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Torq in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Allianz Technology in 2026.
Incident History - Torq (X = Date, Y = Severity)
Torq cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Allianz Technology (X = Date, Y = Severity)
Allianz Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Torq
Allianz Technology
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: *.*.