Comparison Overview
Hobbs London

Hobbs London
183 Eversholt Street, London, England, NW1 1BU, GB
Last Update: 01/02/2026
Hobbs London is a luxury women's fashion brand, showcasing timeless British style and expert craftsmanship. Since our first shop opened in Hampstead, London in 1981, Hobbs has grown from a small yet sought-after shoe label to a global brand synonymous with the best of B...

Hallmark Cards
2501 McGee, Kansas City, 64108, US
Last Update: 11/09/2026
Hallmark believes if you care enough you can change the world as we work to help create a more emotionally connected world in every life, every day. Founded in 1910 by a teenage entrepreneur with two shoe boxes of postcards under his arm, Hallmark today is still famil...
Compliance Ranges Comparison

Hobbs London







Hallmark Cards






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Hobbs London in 2026.
Incidents vs Retail Industry Avg (This Year)
Hallmark Cards has 194.12% more incidents than the average of all companies with at least one recorded incident.
Incident History - Hobbs London (X = Date, Y = Severity)
Hobbs London cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hallmark Cards (X = Date, Y = Severity)
Hallmark Cards cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hobbs London

Hallmark Cards
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)