Comparison Overview
NEC Open Networks

NEC Open Networks
7-1, Shiba 5-chome, Minato, Tokyo, 108-8001, JP
Last Update: 11/02/2026
NEC is leveraging its rich history of innovation in network architecture and telecommunications to drive global digital transformation through openness and collaboration. With our cutting-edge suite of products and services, including RAN, Transport, Core, and System I...

Cox Automotive Inc.
3003 Summit Blvd., 200, Atlanta, GA, US, 30319
Last Update: 12/09/2026
Cox Automotive is the world’s largest automotive services and technology provider. Fueled by the largest breadth of first- and third-party data fed by 2.3 billion online interactions a year, Cox Automotive tailors leading solutions for car shoppers, auto manufacturers, ...
Compliance Ranges Comparison

NEC Open Networks







Cox Automotive Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for NEC Open Networks in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Cox Automotive Inc. in 2026.
Incident History - NEC Open Networks (X = Date, Y = Severity)
NEC Open Networks cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cox Automotive Inc. (X = Date, Y = Severity)
Cox Automotive Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

NEC Open Networks

Cox Automotive Inc.
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