Comparison Overview
Marks and Spencer

Marks and Spencer
Waterside House, London, W2 1NW, GB
Last Update: 06/09/2026
At M&S, we're dedicated to being the most trusted retailer, prioritising quality and delivering value. Every day, we bring the magic of M&S to our customers, whenever, wherever and however they want to shop with us. For over a century, we've set the standard, doing the ...

Ulta Beauty
1000 Remington Blvd, Bolingbrook, 60440, US
Last Update: 02/04/2026
At Ulta Beauty (NASDAQ: ULTA), the possibilities are beautiful. Ulta Beauty is the largest U.S. beauty retailer and the premier beauty destination for cosmetics, fragrance, skin care products, hair care products and salon services. In 1990, the Company reinvented the be...
Compliance Ranges Comparison

Marks and Spencer







Ulta Beauty






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

Marks and Spencer

Ulta Beauty
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout