Comparison Overview
NEC Asia Pacific Pte Ltd
NEC Asia Pacific Pte Ltd
80 Bendemeer Road, Singapore, 339949, SG
Last Update: 16/02/2026
At NEC Asia Pacific, we lead in propelling Singapore's Smart Nation initiatives, integrating trusted technology with social responsibility. As a leading information and communications technology provider, we provide innovative solutions through AI, analytics, data, digi...
Infosys
Infosys Limited, Bangalore, Karnataka, IN, 560100
Last Update: 07/05/2026
Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over three decades of experience in managing the systems and workings of global enterprises, we expe...
Compliance Ranges Comparison
NEC Asia Pacific Pte Ltd
Infosys
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NEC Asia Pacific Pte Ltd in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys in 2026.
Incident History - NEC Asia Pacific Pte Ltd (X = Date, Y = Severity)
NEC Asia Pacific Pte Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Infosys (X = Date, Y = Severity)
Infosys cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NEC Asia Pacific Pte Ltd
Infosys
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: *.*.