Comparison Overview
CarMax

CarMax
12800 Tuckahoe Creek Parkway, Richmond, Virginia, US, 23238
Last Update: 14/09/2026
We're fueled by a common goal: creating an iconic car-buying experience. We make car-buying fair, accessible, and joyful for all. We are committed to making progress in how we positively impact our society, now and in the future. Above all, we care about people. We are ...

Jewel-Osco
150 Pierce Road, Itasca, 60143, US
Last Update: 02/04/2026
Proudly serving our customers in the Chicagoland area since 1899, Jewel-Osco provides friendly service, quality products and great value. Jewel-Osco operates 188 stores throughout the Chicagoland area, Indiana and Iowa, which is part of a 2,200+ store operation that emp...
Compliance Ranges Comparison

CarMax







Jewel-Osco






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
CarMax has 46.24% fewer 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 Jewel-Osco in 2026.
Incident History - CarMax (X = Date, Y = Severity)
CarMax cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jewel-Osco (X = Date, Y = Severity)
Jewel-Osco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CarMax

Jewel-Osco
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.