Comparison Overview
BMW Türkiye

BMW Türkiye
Firuzköy Bulvarı No: 21, İstanbul, 34320, TR
Last Update: 27/01/2026
BMW Türkiye LinkedIn hesabına hoş geldiniz!

Lear Corporation
21557 Telegraph Rd, Southfield , 48033, US
Last Update: 21/09/2026
Lear Corporation (NYSE: LEA) is a global automotive leader in Seating and E-Systems. The company designs, manufactures, and delivers advanced technologies to the world’s major automakers. Building on more than 100 years of heritage, Lear is the largest U.S.-based automo...
Compliance Ranges Comparison

BMW Türkiye







Lear Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for BMW Türkiye in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Lear Corporation in 2026.
Incident History - BMW Türkiye (X = Date, Y = Severity)
BMW Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lear Corporation (X = Date, Y = Severity)
Lear Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BMW Türkiye

Lear Corporation
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.