Comparison Overview
SEM-SAFE Fire Safety A/S, Fully owned by Siemens
SEM-SAFE Fire Safety A/S, Fully owned by Siemens
Middelfartvej 9, Odense C, Fyn, 5000, DK
Last Update: 01/03/2026
At SEM-SAFE Fire Safety, we engineer and supply certified fire protection systems. Within the Land area, SEM-SAFE Fire Safety A/S has a successful track record with a wide range of applications, from high-pressure water mist fire safety systems for museums and heritage ...
Ingersoll Rand
525 Harbour Place Drive, Suite 600, Davidson, 28036, US
Last Update: 01/04/2026
Ingersoll Rand Inc. (NYSE:IR), driven by an entrepreneurial spirit and ownership mindset, is dedicated to Making Life Better for our employees, customers, shareholders, and planet. Customers lean on us for exceptional performance and durability in mission-critical flow ...
Compliance Ranges Comparison
SEM-SAFE Fire Safety A/S, Fully owned by Siemens
Ingersoll Rand
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for SEM-SAFE Fire Safety A/S, Fully owned by Siemens in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Ingersoll Rand in 2026.
Incident History - SEM-SAFE Fire Safety A/S, Fully owned by Siemens (X = Date, Y = Severity)
SEM-SAFE Fire Safety A/S, Fully owned by Siemens cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ingersoll Rand (X = Date, Y = Severity)
Ingersoll Rand cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SEM-SAFE Fire Safety A/S, Fully owned by Siemens
Ingersoll Rand
FAQ
Latest Global CVEs
PraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by registering agents with duplicate IDs. Attackers can exploit the lack of agent ID uniqueness enforcement to share ledger instances and expose system prompts and conversation history between agents.
PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent execution. The POST /agui endpoint lacks authentication and hardcodes Access-Control-Allow-Origin: * headers, combined with Starlette's Content-Type-agnostic JSON parsing, enabling attackers to bypass CORS preflight checks via simple requests and exfiltrate sensitive agent responses including tool execution results and environment data.
PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administrator configuration from PRAISON_APPROVAL_MODE environment variable. Authenticated attackers can instruct the LLM agent to execute arbitrary shell commands via subprocess.run with shell=True, bypassing the manual approval gate and insufficient command sanitization blocklists.
PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass approval prompts. Attackers can exploit this by obtaining initial approval for a benign command, then silently exfiltrate API keys and credentials via subsequent shell commands without user consent.