Comparison Overview
Pacific Seafood
Pacific Seafood
16797 SE 130th Ave., Clackamas, OR, US, 97015
Last Update: 01/04/2026
Founded in 1941 by the Dulcich Family, Pacific Seafood is a family-owned and operated company dedicated to providing the healthiest protein on the planet. Pacific Seafood manages all parts of the supply chain from harvesting/fishing to processing, and distribution in or...
PT SMART Tbk
Jl. M.H. Thamrin No. 51, Jakarta, 10350, ID
Last Update: 01/04/2026
PT SMART Tbk (SMART) / Sinar Mas Agribusiness and Food adalah salah satu perusahaan publik produk konsumen berbasis kelapa sawit yang terintegrasi dan terkemuka di Indonesia yang berkomitmen pada produksi minyak sawit yang berkelanjutan. Perkebunan kelapa sawit SMART m...
Compliance Ranges Comparison
Pacific Seafood
PT SMART Tbk
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Pacific Seafood in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for PT SMART Tbk in 2026.
Incident History - Pacific Seafood (X = Date, Y = Severity)
Pacific Seafood cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT SMART Tbk (X = Date, Y = Severity)
PT SMART Tbk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pacific Seafood
PT SMART Tbk
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: *.*.