Comparison Overview
Applied Materials Taiwan
Applied Materials Taiwan
Hsinchu , TW
Last Update: 02/04/2026
應用材料公司是提供材料工程解決方案的領導者，我們的設備用來製造幾近世界上每顆新式晶片與先進顯示器。我們以工業規模在原子層級進行材料改質的專業，協助客戶將可能轉化成真。在應用材料公司，我們引領材料創新，驅動世界的關鍵變革。 台灣應用材料公司自 1989 年在台營運，深耕台灣三十五年，厚植技術創新、人才培育與社會關懷。我們擁有獨一無二的設施，包括位於桃園的亞洲設備零組件物流中心、新竹的全球技術培訓中心、台南的顯示器設備製造中心與研發實驗室，以及半導體設備製造中心與維修中心，致力攜手台灣半導體及顯示器產業生態系，推動技術創新與發展。 ...
Broadcom
3401 Hillview Ave, Palo Alto, California, US, 94304
Last Update: 30/07/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
Applied Materials Taiwan
Broadcom
Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Applied Materials Taiwan in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
Broadcom has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Applied Materials Taiwan (X = Date, Y = Severity)
Applied Materials Taiwan 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
Applied Materials Taiwan
Broadcom
FAQ
Latest Global CVEs
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in PhialsBasement KoboldCPP-MCP-Server 1.0.0. Affected by this issue is the function makeRequest of the file src/index.ts of the component BaseConfigSchema. Executing a manipulation of the argument apiUrl can lead to server-side request forgery. It is possible to launch the attack on the local host. The project was informed of the problem early through an issue report but has not responded yet.
A security flaw has been discovered in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this vulnerability is the function fs.readFileSync of the file src/index.ts of the component upload_document. Performing a manipulation of the argument File results in path traversal. Attacking locally is a requirement. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was identified in Nikolaibibo claude-comfyui-mcp 1.0.0. Affected is the function copyFileSync of the file src/tools/utils.ts of the component comfy_upload_image. Such manipulation of the argument image_path leads to path traversal. An attack has to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.