Comparison Overview
The UPS Store
The UPS Store
San Diego, 92121, US
Last Update: 02/04/2026
With more than 5,500 locally owned locations across North America, The UPS Store is the nation’s largest retail network of shipping, postal, printing and business service centers. The UPS Store, Inc., franchisor for The UPS Store locations in the U.S., is a wholly owned...
Reliance Digital
Reliance Digital, Navi Mumbai, IN
Last Update: 01/04/2026
Reliance Digital is a Consumer Electronics, Durables, IT & Telecom retail arm of Reliance Retail Group with more than 1300+ stores across India. Reliance Digital seeks to fulfill the dream of every Indian, be it through its nationwide network of conveniently located...
Compliance Ranges Comparison
The UPS Store
Reliance Digital
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for The UPS Store in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Reliance Digital in 2026.
Incident History - The UPS Store (X = Date, Y = Severity)
The UPS Store cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Reliance Digital (X = Date, Y = Severity)
Reliance Digital cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The UPS Store
Reliance Digital
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: *.*.