Comparison Overview
PHOENIX FEINBAU GmbH & Co. KG

PHOENIX FEINBAU GmbH & Co. KG
Gustavstraße 3, Lüdenscheid, North Rhine-Westphalia, 58511, DE
Last Update: 29/04/2026
Phoenix Feinbau GmbH & Co. KG is a metal processing company based in Lüdenscheid. As a member of the Phoenix Contact Group, the company bundles competencies in the areas of toolmaking, stamped part production, surface technology and assembly with injection molding produ...

Signify
High Tech Campus 48, Eindhoven, North Brabant, NL, 5656 AE
Last Update: 05/04/2026
Signify (Euronext: LIGHT Signify is the world leader in lighting for professionals and consumers. We unlock the extraordinary potential of light for brighter lives and a better world. Our global portfolio of brands deliver advanced products, connected systems and servic...
Compliance Ranges Comparison

PHOENIX FEINBAU GmbH & Co. KG







Signify






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for PHOENIX FEINBAU GmbH & Co. KG in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Signify in 2026.
Incident History - PHOENIX FEINBAU GmbH & Co. KG (X = Date, Y = Severity)
PHOENIX FEINBAU GmbH & Co. KG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Signify (X = Date, Y = Severity)
Signify cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PHOENIX FEINBAU GmbH & Co. KG

Signify
FAQ
Latest Global CVEs
Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.
- https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834
- https://github.com/v12-security/pocs/tree/main/redis/server_ssl
- https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES
Unrestricted Upload of File with Dangerous Type in the product photo upload in Roskus Prospero Flow CRM before 5.16.0 allows an authenticated user holding the create product permission (routine Seller role) to execute arbitrary JavaScript in the application origin. The photo validation rule classifies the file only by its content (magic bytes) and rejects only a fixed list of PHP extensions, while ProductSaveController::save() names the stored file using the client-supplied extension and copies it into the public web root. A file that begins with an image header and carries an HTML extension passes validation, is stored under public/asset/upload/product/, and is served with a text/html content type, turning the upload into first-party stored script execution.
A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4
A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgrade to the version 0.24 or later.
A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.