Comparison Overview
STURM und DRANG GmbH
STURM und DRANG GmbH
Holzdamm 14, Hamburg, 20099, DE
Last Update: 22/12/2025
STURMundDRANG conducts research into longings, behaviors and culture within our constantly changing world on the levels of living, working and consumerism and develops renewal strategies based on the insights obtained for companies and brands that are effective for gene...
Conduent
100 Campus Dr, Florham Park, New Jersey, US, 07932
Last Update: 19/06/2026
Conduent delivers digital business solutions and services spanning the commercial, government and transportation spectrum – creating valuable outcomes for its clients and the millions of people who count on them. We leverage cloud computing, artificial intelligence, mac...
Compliance Ranges Comparison
STURM und DRANG GmbH
Conduent
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for STURM und DRANG GmbH in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Conduent has 466.04% more incidents than the average of all companies with at least one recorded incident.
Incident History - STURM und DRANG GmbH (X = Date, Y = Severity)
STURM und DRANG GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Conduent (X = Date, Y = Severity)
Conduent cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
STURM und DRANG GmbH
Conduent
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: *.*.