Comparison Overview
SwissBorg
SwissBorg
Rue du Grand-Chêne 8, Lausanne, 1003, CH
Last Update: 31/03/2026
SwissBorg democratising wealth management by making it fun, fair, and community-centric. Headquartered in Lausanne, Switzerland, SwissBorg has an international team of over 250 people and holds two licenses to provide Virtual Currency Exchange and Virtual Currency Wall...
Edward Jones
12555 Manchester Road, St. Louis, 63131, US
Last Update: 13/09/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
SwissBorg
Edward Jones
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SwissBorg in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Edward Jones in 2026.
Incident History - SwissBorg (X = Date, Y = Severity)
SwissBorg 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
SwissBorg
Edward Jones
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.