Comparison Overview
Samsung Baltics

Samsung Baltics
Duntes iela 6, Rīga, 1013, LV
Last Update: 20/02/2026
Samsung inspires the world and shapes the future with transformative ideas and technologies. The company is redefining the worlds of TVs, smartphones, wearable devices, tablets, digital appliances, network systems, and memory, system LSI, foundry and LED solutions. It i...

Garmin
1200 E. 151st Street, Olathe, KS, US, 66062
Last Update: 10/09/2026
WHERE DO WE START? How about Kansas City? That’s our home. That’s where Garmin put a stake in the ground in 1989. We’ve grown substantially over the years, offering diverse products and global reach in 5 diverse markets. But some things won’t ever change: Our entreprene...
Compliance Ranges Comparison

Samsung Baltics







Garmin






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Samsung Baltics in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Garmin has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Samsung Baltics (X = Date, Y = Severity)
Samsung Baltics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Garmin (X = Date, Y = Severity)
Garmin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Samsung Baltics

Garmin
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)