Comparison Overview
St. Louis Metro Transit
St. Louis Metro Transit
One Metropolitan Square, St. Louis, 63102, US
Last Update: 14/12/2025
We are Metro Transit. Our mission is to keep countless hopes and dreams alive for our people, our communities and our future. And it's our job to know more about where 2.8 million of them call Home than anybody. As an organization, Metro Transit has fueled more person...
Lyft
185 Berry Street, San Francisco, CA, US, 94107
Last Update: 30/04/2026
Whether it’s an everyday commute or a journey that changes everything, Lyft is driven by our purpose: to serve and connect. In 2012, Lyft was founded as one of the first ridesharing communities in the United States. Now, millions of drivers have chosen to earn on billio...
Compliance Ranges Comparison
St. Louis Metro Transit
Lyft
Benchmark & Cyber Underwriting Signals
Incidents vs Ground Passenger Transportation Industry Avg (This Year)
No incidents recorded for St. Louis Metro Transit in 2026.
Incidents vs Ground Passenger Transportation Industry Avg (This Year)
Lyft has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - St. Louis Metro Transit (X = Date, Y = Severity)
St. Louis Metro Transit cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lyft (X = Date, Y = Severity)
Lyft cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
St. Louis Metro Transit
Lyft
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout