Comparison Overview
Pierre Robert Group
Pierre Robert Group
Drammensveien 149, Oslo, undefined, 0277, NO
Last Update: 13/06/2026
Underwear should be well-designed, comfortable, and easy to pick up on your day-to-day visits to the grocery store. Pierre Robert Group develops basic garments for women, men, and children, with uncompromising emphasis on comfort, fit and convenience. We believe that e...
Shaw Industries
616 East Walnut Ave, Dalton, 30720, US
Last Update: 30/03/2026
Shaw Industries Group, Inc. is a leader in flooring and other surface solutions designed for residential housing, commercial spaces and outdoor environments. Leveraging strengths in design, innovation and operational excellence, the company takes a people-centered, cust...
Compliance Ranges Comparison
Pierre Robert Group
Shaw Industries
Benchmark & Cyber Underwriting Signals
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for Pierre Robert Group in 2026.
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for Shaw Industries in 2026.
Incident History - Pierre Robert Group (X = Date, Y = Severity)
Pierre Robert Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shaw Industries (X = Date, Y = Severity)
Shaw Industries cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pierre Robert Group
Shaw Industries
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: *.*.