Comparison Overview
Teleflora

Teleflora
11444 Olympic Blvd., Los Angeles, CA, 90064, US
Last Update: 01/03/2026
Teleflora brings together the time-honored tradition of sending flowers with the modern benefits of an advanced florist network. By tapping over 11,000 member florists in North America alone, Teleflora offers the kind of personal touches, artistry and expertise you expe...

Dräger
Moislinger Allee 53-55, Lübeck, 23552, DE
Last Update: 09/09/2026
Dräger is an international leader in the fields of medical and safety technology. The family-owned company was founded in Lübeck, Germany, in 1889. The company’s long-term success is based on the four key strengths of its value-driven culture: customer intimacy, profess...
Compliance Ranges Comparison

Teleflora







Dräger






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Teleflora in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Dräger in 2026.
Incident History - Teleflora (X = Date, Y = Severity)
Teleflora cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dräger (X = Date, Y = Severity)
Dräger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Teleflora

Dräger
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.