Comparison Overview
Parcel Insurance Plan
Parcel Insurance Plan
undefined, St. Louis, MO, undefined, US
Last Update: 17/11/2025
Parcel Insurance Plan was founded in 1966 with the mission to provide dramatically lower-cost package insurance to business shippers, while offering superior customer and claims service. PIP has been owned by Brown & Brown Insurance, the world's 7th largest insurance br...
Bajaj General Insurance
Yerawada, Bajaj Insurance House, Pune, Maharastra, IN, 411006
Last Update: 01/04/2026
Bajaj General Insurance Limited (formerly known as Bajaj Allianz General Insurance Company Limited) is one of India’s leading, most trusted and dynamic private general insurance companies. It is a subsidiary of Bajaj Finserv Limited, India’s leading and most diversified...
Compliance Ranges Comparison
Parcel Insurance Plan
Bajaj General Insurance
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Parcel Insurance Plan in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Bajaj General Insurance in 2026.
Incident History - Parcel Insurance Plan (X = Date, Y = Severity)
Parcel Insurance Plan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bajaj General Insurance (X = Date, Y = Severity)
Bajaj General Insurance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Parcel Insurance Plan
Bajaj General Insurance
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: *.*.