Comparison Overview
Brave

Brave
580 Howard St., San Francisco, 94105, US
Last Update: 12/06/2026
Brave is on a mission to build a user-first Web. Starting with our flagship browser and search engine, Brave shields users from the creepy ads and trackers that follow you across the web. Our browser has more than 109 million users and our search engine delivers over 2 ...

SLB
5599 San Felipe St, Houston, Texas, US, 77056
Last Update: 21/07/2026
SLB is a global technology company that has driven energy innovation for more than a century. With a global footprint in more than 100 countries and employees representing almost twice as many nationalities, we work each day on innovating oil and gas, delivering digital...
Compliance Ranges Comparison

Brave







SLB






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Brave has 142.42% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for SLB in 2026.
Incident History - Brave (X = Date, Y = Severity)
Brave cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SLB (X = Date, Y = Severity)
SLB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Brave

SLB
FAQ
Latest Global CVEs
An issue in the SBN UDP interface of NASA cFS v7.0.1 allows attackers to cause a Denial of Service (DoS) via transmitting a crafted SBN frame.
A stack-based buffer overflow vulnerability exists in the cmd_edl function of OreSat Firmware v1.0. The vulnerability is triggered when processing the edl fw_flash command, where the <filename> argument is copied to a 64-byte stack buffer via memcpy without proper length validation. An attacker with physical access to the UART3 serial interface can exploit this vulnerability by sending a maliciously crafted command with an oversized filename parameter,
Adobe Campaign Classic (ACC) is affected by a Violation of Secure Design Principles vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploitation of this issue does not require user interaction.
Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could exploit this vulnerability to gain elevated privileges. Exploitation of this issue does not require user interaction.
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. Exploitation of this issue does not require user interaction. Scope is changed.