Comparison Overview
a3EQUIPO
a3EQUIPO
BARCELONA LLEIDA GIRONA TARRAGONA ZARAGOZA, 08001, ES
Last Update: 06/01/2026
Consultoría tecnológica expertos en transformación digital de las empresas y despachos profesionales. Software para empresas y asesorías.
Xiaomi Technology
No. 33 Xi erqi Middle Road, Haidian District, Beijing,100085,China, Beijing, CN
Last Update: 26/06/2026
Xiaomi Corporation was founded in April 2010 and listed on the Main Board of the Hong Kong Stock Exchange on July 9, 2018 (1810.HK). Xiaomi is a consumer electronics and smart manufacturing company with smartphones and smart hardware connected by an IoT platform at its ...
Compliance Ranges Comparison
a3EQUIPO
Xiaomi Technology
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for a3EQUIPO in 2026.
Incidents vs Software Development Industry Avg (This Year)
Xiaomi Technology has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - a3EQUIPO (X = Date, Y = Severity)
a3EQUIPO cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Xiaomi Technology (X = Date, Y = Severity)
Xiaomi Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
a3EQUIPO
Xiaomi Technology
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: *.*.