Comparison Overview
Bonanza Satrangi Pakistan
Bonanza Satrangi Pakistan
Korangi Industrial Area, Karachi, 74900, PK
Last Update: 19/03/2026
Excellence... Innovation... Value... Style... With over 40 years of experience, Bonanza continues its legacy of providing superior fabric, value for money and stylish apparel to its consumers. It all began in 1976 when the textile industry had not even flourished to...
MANGO
Mercaders 9-11, Palau Solità i Plegamans, 08184, ES
Last Update: 02/04/2026
Mango, one of the leading international fashion groups, is a global company with design and creativity at the heart of its business model and a strategy based on constant innovation, the pursuit of sustainability and a complete ecosystem of channels and partners. With ...
Compliance Ranges Comparison
Bonanza Satrangi Pakistan
MANGO
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Bonanza Satrangi Pakistan in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
MANGO has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Bonanza Satrangi Pakistan (X = Date, Y = Severity)
Bonanza Satrangi Pakistan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MANGO (X = Date, Y = Severity)
MANGO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bonanza Satrangi Pakistan
MANGO
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: *.*.