Comparison Overview
KPJ Healthcare Bhd
KPJ Healthcare Bhd
Level 12, Menara 238, 238 Jalan Tun Razak,, Kuala Lumpur, 50400, MY
Last Update: 01/04/2026
Since its inception in 1981 as the first private specialist hospital in Johor, KPJ Healthcare has served communities and neighbourhoods nationwide for over 40 years. Our fundamental purpose since day 1 is the delivery of exceptional diagnosis, health treatment and care ...
Johnson & Johnson
New Brunswick, NJ, US, 08903
Last Update: 28/06/2026
At Johnson & Johnson, we believe health is everything. Our strength in healthcare innovation empowers us to build a world where complex diseases are prevented, treated, and cured, where treatments are smarter and less invasive, and solutions are personal. Through our ex...
Compliance Ranges Comparison
KPJ Healthcare Bhd
Johnson & Johnson
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for KPJ Healthcare Bhd in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Johnson & Johnson has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - KPJ Healthcare Bhd (X = Date, Y = Severity)
KPJ Healthcare Bhd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson & Johnson (X = Date, Y = Severity)
Johnson & Johnson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
KPJ Healthcare Bhd
Johnson & Johnson
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: *.*.