Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

Pilz Taiwan 臺灣皮爾磁Pilz Taiwan 臺灣皮爾磁
VS
KUKAKUKA
Pilz Taiwan 臺灣皮爾磁

Pilz Taiwan 臺灣皮爾磁

松山區八德路三段36號10樓, 台北市, 10559, TW

Last Update: 02/05/2026

View Profile
Between 700 and 749
https://www.pilz.com/tw-TW
745/1000Moderate

Pilz 是安全自動化產品、系統及服務的專業供應商,總部位於德國奧斯菲爾,在全球有2400員工和42家分公司,專為人員、機械設備及環境提供安全解決方案。 身為全球技術領導品牌,Pilz產品包含感測器技術、電子式監控繼電器、安全繼電器、可程式控制系統、運動控制技術的自動化解決方案、工業用通訊協定系統,以及圖像顯示解決方案與操作終端機。 此外,Pilz服務也包含安全諮詢、工程設計及訓練,如安全風險評估,歐盟CE認證以及CMSE機械安全專家認證課程。

NAICS:33325
NAICS Definition:Others
Employees:0
Subsidiaries:26
12-month incidents
0
Known data breaches
0
Attack type number
0
KUKA

KUKA

Zugspitzstr. 140, Augsburg, 86165, DE

Last Update: 09/09/2026

View Profile
Between 750 and 799
http://www.kuka.com
781/1000Fair

KUKA SE & Co. KGaA is a global leader in intelligent automation solutions, generating around 3.7 billion euro in sales and employing approximately 15,000 people worldwide. Headquartered in Augsburg, Germany, KUKA’s mission is to make automation accessible for everyone -...

NAICS:33325
NAICS Definition:Others
Employees:10,671
Subsidiaries:6
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Ranges Comparison

Based On Specific Ai Models Category
Pilz Taiwan 臺灣皮爾磁

Pilz Taiwan 臺灣皮爾磁

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
KUKA

KUKA

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)

No incidents recorded for Pilz Taiwan 臺灣皮爾磁 in 2026.

Incidents

Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)

No incidents recorded for KUKA in 2026.

Incidents

Incident History - Pilz Taiwan 臺灣皮爾磁 (X = Date, Y = Severity)

Pilz Taiwan 臺灣皮爾磁 cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - KUKA (X = Date, Y = Severity)

KUKA cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
Pilz Taiwan 臺灣皮爾磁

Pilz Taiwan 臺灣皮爾磁

Incidents
No explicit notable incidents reported.
KUKA

KUKA

Incidents
No explicit notable incidents reported.

FAQ

Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has the best AI Cybersecurity Score ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced more cyber incidents in the past ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced more cyber incidents this year ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced at least one ransomware attack ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced at least one data breach ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced at least one targeted cyberattack ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has experienced at least one vulnerability ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one holds the most compliance certifications ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one holds the fewest compliance certifications ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has the most subsidiaries ?
Between Pilz Taiwan 臺灣皮爾磁 company and KUKA company, which one has the largest number of employees ?
Between Pilz Taiwan 臺灣皮爾磁 and KUKA, which company holds both SOC 2 Type 1 certifications ?
Between Pilz Taiwan 臺灣皮爾磁 and KUKA, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - Pilz Taiwan 臺灣皮爾磁 or KUKA ?
Which company is PCI DSS compliant - Pilz Taiwan 臺灣皮爾磁 or KUKA ?
Between Pilz Taiwan 臺灣皮爾磁 and KUKA, which company complies with HIPAA regulations for healthcare data ?
Between Pilz Taiwan 臺灣皮爾磁 and KUKA, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-90603
SUMMARY

A vulnerability was identified in Anil-matcha Open-Generative-AI up to 1.0.11/2.0.0. Affected by this issue is some unknown functionality of the file /api/upload-binary of the component S3 Upload. Such manipulation of the argument x-proxy-target-url leads to unrestricted upload. The attack may be launched remotely. The name of the patch is f013270957f75e439eaf97eb2a93decb32a4543e. Applying a patch is advised to resolve this issue.

PUBLISHED
Date2026-09-13
UPDATED
Date2026-09-13
RISK INFORMATION (Score: 7.3)
CVSS2
Base Score: 7.5
Complexity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
CVSS3
Base Score: 7.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 6.9
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
3.9
CVE-2026-90602
SUMMARY

A vulnerability was determined in Anil-matcha Open-Generative-AI up to 1.0.11/2.0.0. Affected by this vulnerability is the function renderHistory of the file ImageStudio.js of the component Studio Components. This manipulation causes cross site scripting. The attack may be initiated remotely. The pull request to fix this issue awaits acceptance.

PUBLISHED
Date2026-09-13
UPDATED
Date2026-09-13
RISK INFORMATION (Score: 3.5)
CVSS2
Base Score: 4.0
Complexity: LOW
AV:N/AC:L/Au:S/C:N/I:P/A:N
CVSS3
Base Score: 3.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
CVSS4
Base Score: 5.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
1.4
EXPLOITABILITY
2.1
CVE-2026-90601
SUMMARY

A vulnerability was found in getzep graphiti up to 0.30.2. Affected is an unknown function of the file server/graph_service/main.py of the component REST API. The manipulation results in improper authentication. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.

PUBLISHED
Date2026-09-13
UPDATED
Date2026-09-13
RISK INFORMATION (Score: 7.3)
CVSS2
Base Score: 7.5
Complexity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
CVSS3
Base Score: 7.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 6.9
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
3.9
CVE-2026-90600
SUMMARY

A vulnerability has been found in itsourcecode Sales and Inventory System 1.0. This impacts an unknown function of the file /pages/inv_edit1.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

PUBLISHED
Date2026-09-13
UPDATED
Date2026-09-13
RISK INFORMATION (Score: 6.3)
CVSS2
Base Score: 6.5
Complexity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
CVSS3
Base Score: 6.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 2.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
2.8
CVE-2026-15892
SUMMARY

The mcumgr SMP settings-management group handlers settings_mgmt_read(), settings_mgmt_write(), and settings_mgmt_delete() in subsys/mgmt/mcumgr/grp/settings_mgmt/src/settings_mgmt.c allocate a key_name buffer (and, for read, a data buffer) via k_malloc() when CONFIG_MCUMGR_GRP_SETTINGS_BUFFER_TYPE_HEAP is enabled, relying on the end: label to k_free() them. When CONFIG_MCUMGR_GRP_SETTINGS_ACCESS_HOOK is also enabled and the application access hook rejects a request by returning status MGMT_CB_ERROR_RC, the handler executed return ret_rc; directly, bypassing end: and leaking the heap allocation on every rejected request. The settings handlers are reachable over the unauthenticated SMP transport (Bluetooth LE, UART, or UDP, depending on product configuration). The access hook is the mechanism applications use to deny unauthorized settings access, and MGMT_CB_ERROR_RC is a common rejection style, so an attacker who can send settings read/write/delete commands that the hook rejects triggers a heap leak on each attempt. Because the leaked memory is never reclaimed until reboot, a sustained stream of rejected requests monotonically exhausts the kernel heap until k_malloc() fails, denying mcumgr service and impacting any other heap consumer on the device — a denial of service. The impact is availability-only; there is no memory corruption or information disclosure. Only configurations that select the heap buffer type, enable the access hook, and register a hook that returns MGMT_CB_ERROR_RC are affected (the default stack buffer type cannot leak).

PUBLISHED
Date2026-09-13
UPDATED
Date2026-09-13
RISK INFORMATION (Score: 5.3)
CVSS3
Base Score: 5.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
IMPACT SCORE
1.4
EXPLOITABILITY
3.9