Comparison Overview
EBV Elektronik
EBV Elektronik
Im Technologiepark 2-8, Poing, Bavaria, 85586, DE
Last Update: 19/02/2026
EBV Elektronik, an Avnet (NYSE: AVT) company, was founded in 1969 and is the leading specialist in European semiconductor distribution. EBV maintains its successful strategy of personal commitment to customers and excellent services. 260 Technical Sales Specialists prov...
Broadcom
3401 Hillview Ave, Palo Alto, California, US, 94304
Last Update: 21/06/2026
Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs. We combine long-term R&D investment with superb execution to deliver the best technology, at scale. Through focus and expertise, Broadcom sets the st...
Compliance Ranges Comparison
EBV Elektronik
Broadcom
Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for EBV Elektronik in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
Broadcom has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - EBV Elektronik (X = Date, Y = Severity)
EBV Elektronik cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Broadcom (X = Date, Y = Severity)
Broadcom cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
EBV Elektronik
Broadcom
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.