Comparison Overview
Pottery Barn

Pottery Barn
151 Union Street, San Francisco, CA, 94111, US
Last Update: 15/11/2025
For over 70 years, Pottery Barn has represented exceptional quality and unparalleled value. America’s most meaningful, beautiful design source, we bring together good products, people and values. We believe that style evolves, but quality is timeless. Original designs...

O'Reilly Auto Parts
233 S Patterson Ave, Springfield, MO, US, 65802
Last Update: 01/04/2026
O’Reilly Auto Parts started as a single store and has grown into a leading retailer in the automotive aftermarket industry with more than 6,100 locations and counting. With more than 94,000 team members, O’Reilly has expanded into 48 states, Puerto Rico, Mexico, and Can...
Compliance Ranges Comparison

Pottery Barn







O'Reilly Auto Parts






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Pottery Barn in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for O'Reilly Auto Parts in 2026.
Incident History - Pottery Barn (X = Date, Y = Severity)
Pottery Barn cyber incidents detection timeline including parent company and subsidiaries.
Incident History - O'Reilly Auto Parts (X = Date, Y = Severity)
O'Reilly Auto Parts cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Pottery Barn

O'Reilly Auto Parts
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.