Comparison Overview
Keysight Technologies

Keysight Technologies
1400 Fountaingrove Pkwy, Santa Rosa, California, US, 95403
Last Update: 09/09/2026
Keysight empowers innovators to explore, design, and bring world-changing technologies to life. As the industry’s premier global innovation partner, Keysight’s software-centric solutions serve engineers across the design and development environment, enabling them to del...

Dyson
3 Sentosa Gateway, Singapore, 098544, SG
Last Update: 13/09/2026
Dyson solves real-world problems and creates better products through the application of engineering, science, design and creativity. It is a family-owned, global technology company, founded by Sir James Dyson who remains at the helm alongside his son Jake. Since inven...
Compliance Ranges Comparison

Keysight Technologies







Dyson






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Keysight Technologies in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Dyson in 2026.
Incident History - Keysight Technologies (X = Date, Y = Severity)
Keysight Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dyson (X = Date, Y = Severity)
Dyson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Keysight Technologies

Dyson
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