Comparison Overview
Alliance Solutions Group, Inc.
Alliance Solutions Group, Inc.
3535 Roswell Road, Marietta, 30062, US
Last Update: 21/03/2026
Alliance Solutions Group, Inc. distinguishes itself through the motto: “It’s About The Relationship.” Combining traditional values and strong work ethic to support our clients and partners, we create lasting, collaborative relationships to provide technology and RFID pr...
VINCI Energies
2169, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 31/03/2026
In a world undergoing constant change, VINCI Energies contributes to the environmental transition by helping bring about major trends in the digital landscape and energy sector. VINCI Energies’ teams roll out technologies and integrate customised multi-technical solutio...
Compliance Ranges Comparison
Alliance Solutions Group, Inc.
VINCI Energies
Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Alliance Solutions Group, Inc. in 2026.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for VINCI Energies in 2026.
Incident History - Alliance Solutions Group, Inc. (X = Date, Y = Severity)
Alliance Solutions Group, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VINCI Energies (X = Date, Y = Severity)
VINCI Energies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alliance Solutions Group, Inc.
VINCI Energies
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: *.*.