Comparison Overview
Chemprene
Chemprene
Beacon, 12508, US
Last Update: 06/03/2026
Founded over 75 years ago, Chemprene began as a chemical rubber products company in Beacon, NY. Over the decades, we expanded our expertise from military-coated fabrics to include automotive diaphragms, specialty belting, and advanced belt-curing machinery. Today, we op...
BAT
4 Temple Place, London, WC2R 2PG, GB
Last Update: 28/06/2026
We are BAT, a leading global consumer goods company driven by a clear purpose: to create A Better Tomorrow™ by Building a Smokeless World. Founded in 1902, we’ve grown into a truly international business, operating across six continents with a presence in over 180 mark...
Compliance Ranges Comparison
Chemprene
BAT
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Chemprene in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for BAT in 2026.
Incident History - Chemprene (X = Date, Y = Severity)
Chemprene cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAT (X = Date, Y = Severity)
BAT cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Chemprene
BAT
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: *.*.