Comparison Overview
Medline Japan

Medline Japan
Koishikawa 1-4-1, Bunkyo-ku, Tokyo, 112-0002, JP
Last Update: 20/03/2026
半世紀にわたり、医療の最前線を支え続けて― 私たちメドライン・ジャパンは、 米国最大規模のトータルメディカルサプライヤ-、メドライン社の日本法人です。 急性期病院や手術センター、介護施設、在宅介護業者などの医療現場に向け、 これまで多岐にわたる医療製品を製造・販売。 その製品とサービスは、全米の主要な医療機関で認められ、 現在は世界30ヵ国以上の国々で愛用されています。 世界の医療現場でおよそ半世紀にわたって培われてきた品質と安全性を、日本の医療現場へ―。 私たちのこれからの活躍にぜひご期待ください。 ...

Align Technology
410 North Scottsdale Road , Suite 1300, Tempe, Arizona, US, 85281
Last Update: 02/04/2026
We are dedicated to transforming lives by improving the journey to a healthy, beautiful smile. Discover your straight path to a bright future at Align Technology. As a part of our smart, diverse and fast-moving global team, you'll make an impact on the market leader t...
Compliance Ranges Comparison

Medline Japan







Align Technology






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Medline Japan in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Align Technology in 2026.
Incident History - Medline Japan (X = Date, Y = Severity)
Medline Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Align Technology (X = Date, Y = Severity)
Align Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Medline Japan

Align Technology
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.