Comparison Overview
Hach Thailand
Hach Thailand
D3 11,3rd Floor,No.735/4 Srinakarin Rd., Bangkok, 10250, TH
Last Update: 15/12/2025
Hach Thailand has total solutions to solve your specific needs and we taking care of customers in Thailand, Myanmar, Laos, and Cambodia. By the designed systems that offering sophisticated on-line instrumentation, accurate portable laboratory, equipment, high-quality pr...
Grupo Tragsa
C/ Maldonado 58, Madrid, ES, 28006
Last Update: 02/04/2026
Tragsa Group is a group of public companies, integrated in the State Industrial Ownership Corporation (SEPI), which has become a full service supplier and a reference company to Public Administrations. It is formed by four enterprises: Tragsa (1977) responsible for wor...
Compliance Ranges Comparison
Hach Thailand
Grupo Tragsa
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Hach Thailand in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Grupo Tragsa in 2026.
Incident History - Hach Thailand (X = Date, Y = Severity)
Hach Thailand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Grupo Tragsa (X = Date, Y = Severity)
Grupo Tragsa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hach Thailand
Grupo Tragsa
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: *.*.