Comparison Overview
Bath & Body Works

Bath & Body Works
Columbus, Ohio, US, 43068
Last Update: 02/04/2026
We were founded on a simple idea: to make the world a brighter, happier place through the power of fragrance. As we've grown, so has our purpose and today, we help the world live more fully through the power of fragrance. We’re a team that cares about our customers and...

Acosta
6651 Gate Pkwy, Jacksonville, 32256, US
Last Update: 01/04/2026
Acosta brings simplicity to retail sales. We act as a catalyst to boldly connect brands, retailers and consumers, fueling growth and building long-term value throughout North America and Europe. We are deeply embedded in every corner of the retail industry, strengtheni...
Compliance Ranges Comparison

Bath & Body Works







Acosta






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Bath & Body Works in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Acosta in 2026.
Incident History - Bath & Body Works (X = Date, Y = Severity)
Bath & Body Works cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Acosta (X = Date, Y = Severity)
Acosta cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bath & Body Works

Acosta
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.