Comparison Overview
next
next
Rua Domingos Sérgio dos Anjos, 277 - Jardim Santo Elias , São Paulo, São Paulo, 05136-170, BR
Last Update: 07/12/2025
O next é um banco digital completo e gratuito, criado em 2017 para simplificar e transformar a vida das pessoas. Reunimos diversos talentos em uma equipe plural, diversa e conectada, que faz do next um lugar único. Nós, nexters, somos movidos pelo desejo de impulsionar ...
LSEG
10 Paternoster Square, London, EC4M 7DX, GB
Last Update: 08/09/2026
LSEG (London Stock Exchange Group) is a diversified international markets infrastructure business —earning our clients’ trust for over 300 years. That legacy of customer-focused excellence ensures that you can rely on our expertise in capital formation, intellectual pro...
Compliance Ranges Comparison
next
LSEG
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for next in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for LSEG in 2026.
Incident History - next (X = Date, Y = Severity)
next cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LSEG (X = Date, Y = Severity)
LSEG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
next
LSEG
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.