Comparison Overview
Clean it with Chemetall North America
Clean it with Chemetall North America
675 Central Avenue, New Providence, 07974, US
Last Update: 12/03/2026
Whether it is soil, by-products, or microbes, Chemetall provides a product to clean it. Countless companies trust Chemetall for everything from general maintenance to precision cleaning.
BASF
Carl-Bosch-Str. 38, Ludwigshafen, DE, 67056
Last Update: 07/05/2026
At BASF, we create chemistry for a sustainable future. Our ambition: We want to be the preferred chemical company to enable our customers’ green transformation. We combine economic success with environmental protection and social responsibility. Around 112,000 employees...
Compliance Ranges Comparison
Clean it with Chemetall North America
BASF
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Clean it with Chemetall North America in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
BASF has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Clean it with Chemetall North America (X = Date, Y = Severity)
Clean it with Chemetall North America cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BASF (X = Date, Y = Severity)
BASF cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Clean it with Chemetall North America
BASF
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: *.*.