Comparison Overview
MassMutual Oregon
MassMutual Oregon
5885 Meadows Road, Suite 850, Lake Oswego, Oregon, 97035, US
Last Update: 20/01/2026
At MassMutual Oregon, we help you define what you want out of life. Then, we map out financial strategies to help you get there. We work with you to help minimize risk, protect your assets, reduce taxes and build your long-term wealth. Based in Lake Oswego, MassMutual...
Empower
8515 E. Orchard Road, Greenwood Village, CO, US, 80111
Last Update: 02/04/2026
At Empower, we’ve always been guided by strong values with a focus on helping people achieve the financial freedom they deserve. It’s been an incredible journey so far, but our story is just getting started. From the very beginning, we’ve prided ourselves on puttin...
Compliance Ranges Comparison
MassMutual Oregon
Empower
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for MassMutual Oregon in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Empower in 2026.
Incident History - MassMutual Oregon (X = Date, Y = Severity)
MassMutual Oregon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Empower (X = Date, Y = Severity)
Empower cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MassMutual Oregon
Empower
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: *.*.