Comparison Overview
Grupo Insud
Grupo Insud
Paraguay 1535, Ciudad de Buenos Aires, C1061ABC, AR
Last Update: 02/04/2026
Somos un conjunto de empresas de capitales argentinos, altamente diversificado, y con presencia global. Comenzamos trabajando en la industria farmacéutica, nuestra actividad principal. Hoy, nos consolidamos también en áreas como los emprendimientos agroforestales; las i...
Larsen & Toubro
N.M.Marg, Ballard Estate, Mumbai, Maharashtra, IN, 400001
Last Update: 04/07/2026
Larsen & Toubro is an Indian multinational engaged in EPC Projects, Hi-Tech Manufacturing and Services. It operates in over 50 countries worldwide. A strong, customer-focused approach and the constant quest for top-class quality have enabled L&T to attain and sustain ...
Compliance Ranges Comparison
Grupo Insud
Larsen & Toubro
Benchmark & Cyber Underwriting Signals
Incidents vs Executive Offices Industry Avg (This Year)
No incidents recorded for Grupo Insud in 2026.
Incidents vs Executive Offices Industry Avg (This Year)
No incidents recorded for Larsen & Toubro in 2026.
Incident History - Grupo Insud (X = Date, Y = Severity)
Grupo Insud cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Larsen & Toubro (X = Date, Y = Severity)
Larsen & Toubro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grupo Insud
Larsen & Toubro
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: *.*.