Comparison Overview
Taylor Prime Labels & Packaging
Taylor Prime Labels & Packaging
2020 Lookout Drive, North Mankato, MN, 56003, US
Last Update: 18/02/2026
Taylor Prime Labels & Packaging is part of Taylor, one of the five largest graphic communications companies in North America. We are a recognized leader in the design and manufacture of prime labels and packaging products. From flexible packaging, shrink sleeves, roll-f...
Sealed Air Corporation
2415 Cascade Pointe Boulevard, Charlotte, NC, US, 28208
Last Update: 01/04/2026
Sealed Air is in business to protect, to solve critical packaging challenges, and to make our world better than we find it. Our automated packaging solutions promote a safer, more resilient, and less wasteful global food, fluids and liquids supply chain, enable e-commer...
Compliance Ranges Comparison
Taylor Prime Labels & Packaging
Sealed Air Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Taylor Prime Labels & Packaging in 2026.
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Sealed Air Corporation in 2026.
Incident History - Taylor Prime Labels & Packaging (X = Date, Y = Severity)
Taylor Prime Labels & Packaging cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sealed Air Corporation (X = Date, Y = Severity)
Sealed Air Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Taylor Prime Labels & Packaging
Sealed Air Corporation
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: *.*.