Comparison Overview
NRMA Insurance
NRMA Insurance
N/A
Last Update: 01/02/2026
For almost one hundred years we’ve helped people. In that time, we’ve repaired homes and rebuilt lives. We’ve advocated for road safety, and more resilient communities. From drought to flood, from fire to storm, we can’t change our climate, but we can change the way we ...
Sunshine Insurance Group
朝外大街, 朝阳区, 100020, CN
Last Update: 01/04/2026
Established in July 2005, Sunshine Insurance Group has experienced sustainable development, now ranking among the Top 7 insurance groups in China, with an annual business income of $12.6 billion in 2016. Sunshine is composed of Property and Casualty Insurance, Life Insu...
Compliance Ranges Comparison
NRMA Insurance
Sunshine Insurance Group
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for NRMA Insurance in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Sunshine Insurance Group in 2026.
Incident History - NRMA Insurance (X = Date, Y = Severity)
NRMA Insurance cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sunshine Insurance Group (X = Date, Y = Severity)
Sunshine Insurance Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NRMA Insurance
Sunshine Insurance 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: *.*.