Comparison Overview
Comsearch, Inc.
Comsearch, Inc.
308 Market Street, Warren, Rhode Island, US, 02885
Last Update: 02/04/2026
Who We Are Comsearch leads the industry in providing a comprehensive portfolio of services to insurance companies, enabling them to better manage auto and property claims. We apply proven, market-tested experience and expertise to the business of property and auto claim...
HUB International
300 North LaSalle, 17th Floor, Chicago, IL, US, 60654
Last Update: 01/04/2026
Hi, we’re HUB. We advise businesses and individuals on how to reach their goals. When you partner with us, you’re at the center of a vast network of risk, insurance, employee benefits, retirement and wealth management specialists that bring clarity to a changing world ...
Compliance Ranges Comparison
Comsearch, Inc.
HUB International
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Comsearch, Inc. in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for HUB International in 2026.
Incident History - Comsearch, Inc. (X = Date, Y = Severity)
Comsearch, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HUB International (X = Date, Y = Severity)
HUB International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Comsearch, Inc.
HUB International
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: *.*.