Comparison Overview
Brand New Day Health Plan
Brand New Day Health Plan
5455 Garden Grove Blvd, Westminster, 92683, US
Last Update: 30/03/2026
Brand New Day is the Medicare product line name of Universal Care, Inc. and is a privately held health plan that has been in operation since 1985. We have focused on the importance of helping our members navigate the complex healthcare system with the goal of improving ...
CVS Health
1 CVS Drive, Woonsocket, RI, US, 02895
Last Update: 09/07/2026
CVS Health is the leading health solutions company, delivering care like no one else can. We reach more people and improve the health of communities across America through our local presence, digital channels and over 300,000 dedicated colleagues. Wherever and wheneve...
Compliance Ranges Comparison
Brand New Day Health Plan
CVS Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Brand New Day Health Plan in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for CVS Health in 2026.
Incident History - Brand New Day Health Plan (X = Date, Y = Severity)
Brand New Day Health Plan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CVS Health (X = Date, Y = Severity)
CVS Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brand New Day Health Plan
CVS Health
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: *.*.