Comparison Overview
CDK Global Heavy Truck

CDK Global Heavy Truck
11809 Domain Dr, Austin, 78758, US
Last Update: 19/03/2026
CDK Global Heavy Truck is committed to providing Heavy Truck dealers with the solutions you need to keep the industry moving faster — and smarter. We've been in the Heavy Truck business from the beginning and we continue to invest. You can count on us to be there for yo...

DoorDash
San Francisco, US
Last Update: 20/09/2026
At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and...
Compliance Ranges Comparison

CDK Global Heavy Truck







DoorDash






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for CDK Global Heavy Truck in 2026.
Incidents vs Software Development Industry Avg (This Year)
DoorDash has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - CDK Global Heavy Truck (X = Date, Y = Severity)
CDK Global Heavy Truck cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DoorDash (X = Date, Y = Severity)
DoorDash cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CDK Global Heavy Truck

DoorDash
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