Comparison Overview
Angling Direct PLC
Angling Direct PLC
Wendover Road, Norwich, NR13 6LH, GB
Last Update: 30/03/2026
Angling Direct is the largest specialist fishing tackle retailer in the UK. The Company principally sells fishing tackle products and related products through a network of 48 Angling Direct retail stores located in the UK and also online via its own website (www.angling...
Dollar Tree Stores
500 Volvo Pkwy, Chesapeake, 23320, US
Last Update: 01/04/2026
Dollar Tree remains committed to our original mission: giving our customers extreme value at low prices. Employing more than 150,000 associates across a network of 9,000 stores and 18 distribution centers in North America, we’re fulfilling that mission more now than eve...
Compliance Ranges Comparison
Angling Direct PLC
Dollar Tree Stores
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Angling Direct PLC in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Dollar Tree Stores in 2026.
Incident History - Angling Direct PLC (X = Date, Y = Severity)
Angling Direct PLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dollar Tree Stores (X = Date, Y = Severity)
Dollar Tree Stores cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Angling Direct PLC
Dollar Tree Stores
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: *.*.