Comparison Overview
P&G Singapore Innovation Center (SgIC)
P&G Singapore Innovation Center (SgIC)
70 Biopolis Street, Singapore, 138547, SG
Last Update: 25/03/2026
The P&G Singapore innovation center (SgIC) is one of the largest private research facilities in Singapore. Our passion is end-to-end consumer goods innovation, enabled by advanced capabilities. From robotics to virtual reality, chemistry to consumer understanding and bi...
Tupy
Rua Albano Schmidt 3400, Joinville, 89227-220, BR
Last Update: 31/03/2026
Tupy is a Brazilian company specialized in developing and manufacturing highly-engineered structural cast iron components applied to complex metallurgical and geometrical components extensively used in capital goods that serve freight transport, construction industry, ...
Compliance Ranges Comparison
P&G Singapore Innovation Center (SgIC)
Tupy
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for P&G Singapore Innovation Center (SgIC) in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Tupy in 2026.
Incident History - P&G Singapore Innovation Center (SgIC) (X = Date, Y = Severity)
P&G Singapore Innovation Center (SgIC) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tupy (X = Date, Y = Severity)
Tupy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
P&G Singapore Innovation Center (SgIC)
Tupy
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: *.*.