Comparison Overview
Interactive Brokers

Interactive Brokers
2 Pickwick Plaza, Greenwich, 06830, US
Last Update: 20/09/2026
Rated #1 Active Traders and #1 International Trading in 2025 by StockBrokers.com. Interactive Brokers Group (Nasdaq: IBKR) and its affiliates provide automated trade execution and custody of securities, commodities, foreign exchange, and forecast contracts around the...

Discover
2500 Lake Cook Road, Riverwoods, IL, US, 60015
Last Update: 16/09/2026
Discover® is now part of Capital One. Together, we’ll continue to deliver exceptional financial products and experiences, drive innovation, and serve customers. Find the latest updates at https://capitalonediscover.com. Discover is one of the most recognized brands in ...
Compliance Ranges Comparison

Interactive Brokers







Discover






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Interactive Brokers in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Discover in 2026.
Incident History - Interactive Brokers (X = Date, Y = Severity)
Interactive Brokers cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Discover (X = Date, Y = Severity)
Discover cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Interactive Brokers

Discover
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)