Comparison Overview
SEMI Japan
SEMI Japan
丸の内1-4-1, 千代田区, 1000005, JP
Last Update: 31/01/2026
SEMI（セミ）は半導体製造を中心にサプライチェーンを繋ぐ世界的な業界団体です。SEMICON Japan（セミコン・ジャパン）は1977年より続く、エレクトロニクスサプライチェーン唯一の国際展示会です。
Médecins Sans Frontières (MSF)
Rte de Ferney 140, 1202 Genève, Geneva, GE, CH, 1202
Last Update: 04/04/2026
Médecins Sans Frontières (MSF) is an international, independent, medical humanitarian organisation working to provide medical assistance to people affected by conflict, epidemics, disasters, or exclusion from healthcare. Since our founding in 1971, we’ve grown to a gl...
Compliance Ranges Comparison
SEMI Japan
Médecins Sans Frontières (MSF)
Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for SEMI Japan in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Médecins Sans Frontières (MSF) in 2026.
Incident History - SEMI Japan (X = Date, Y = Severity)
SEMI Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Médecins Sans Frontières (MSF) (X = Date, Y = Severity)
Médecins Sans Frontières (MSF) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SEMI Japan
Médecins Sans Frontières (MSF)
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: *.*.