Comparison Overview
Exclusive Networks Thailand
Exclusive Networks Thailand
202, Room 2201, 22nd Floor, Le Concorde Tower, Bangkok, 10310, TH
Last Update: 14/05/2026
Exclusive Networks (Euronext Paris: EXN) is a global cybersecurity specialist that provides partners and end-customers with a unique combination of services and product portfolios via proven routes to market, leveraging the technical know-how of our teams. With offices ...
AlmavivA Group
Via di Casal Boccone, 188-190, Roma, IT, 00137
Last Update: 01/04/2026
Almaviva is the Italian digital innovation group that supports the country’s growth by helping enterprises meet the challenges of staying competitive in the digital age. The Group helps organizations transform their business models, operational structures, corporate cul...
Compliance Ranges Comparison
Exclusive Networks Thailand
AlmavivA Group
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Exclusive Networks Thailand in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AlmavivA Group in 2026.
Incident History - Exclusive Networks Thailand (X = Date, Y = Severity)
Exclusive Networks Thailand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AlmavivA Group (X = Date, Y = Severity)
AlmavivA Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Exclusive Networks Thailand
AlmavivA Group
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: *.*.