Comparison Overview
PROTIQ - A Phoenix Contact Company
PROTIQ - A Phoenix Contact Company
Flachsmarkt Straße 54, Blomberg, Nordrhein-Westfalen 32825, DE
Last Update: 29/04/2026
May we introduce ourselves? We are the PROTIQ Marketplace, your online marketplace for industrial manufacturing. On the PROTIQ Marketplace you can easily have individual components manufactured. The desired objects are manufactured by PROTIQ itself or one of over 30 hi...
Alpargatas S.A.
Av. das Nações Unidas, 14.261, São Paulo, 04794-000, BR
Last Update: 01/04/2026
We are a global company, founded and based in Brazil for over 115 years. We are committed to delight the world with amazing brands, that convey lightness and joy to the everyday lives of our consumers. We own Havaianas brand, world leader in open shoes, known for the ic...
Compliance Ranges Comparison
PROTIQ - A Phoenix Contact Company
Alpargatas S.A.
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for PROTIQ - A Phoenix Contact Company in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Alpargatas S.A. in 2026.
Incident History - PROTIQ - A Phoenix Contact Company (X = Date, Y = Severity)
PROTIQ - A Phoenix Contact Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alpargatas S.A. (X = Date, Y = Severity)
Alpargatas S.A. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PROTIQ - A Phoenix Contact Company
Alpargatas S.A.
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: *.*.