Comparison Overview
BNP Paribas Asset Management
BNP Paribas Asset Management
8, Rue du Port, None, Nanterre, Île-de-France, FR, 92729
Last Update: 11/03/2026
A changing world offers many opportunities. It also brings challenges that develop our abilities and test our ambitions, views and determination. At BNP Paribas Asset Management, we embrace these changes to make a difference to people's lives by adding sustainable val...
Edward Jones
12555 Manchester Road, St. Louis, MO, US, 63131
Last Update: 29/03/2026
Edward Jones is a leading North American financial services firm in the U.S. and through its affiliate in Canada. The firm’s more than 20,000 financial advisors throughout North America serve more than 9 million clients with a total of $2.2 trillion in client assets und...
Compliance Ranges Comparison
BNP Paribas Asset Management
Edward Jones
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas Asset Management in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Edward Jones in 2026.
Incident History - BNP Paribas Asset Management (X = Date, Y = Severity)
BNP Paribas Asset Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Edward Jones (X = Date, Y = Severity)
Edward Jones cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BNP Paribas Asset Management
Edward Jones
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: *.*.