Comparison Overview

CarMax

VS

Jewel-Osco

CarMax

12800 Tuckahoe Creek Parkway, Richmond, Virginia, US, 23238
Last Update: 2026-04-01
View Profile
Between 650 and 699
http://carmax.com

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 committed to putting people first, including our associates, customers, and communities. Spark positive change alongside us. Here’s your chance to leave a mark. Find the purpose, tools, and resources to go for greatness with teammates by your side. We offer benefits and resources to help make your best life happen. Professional growth and limitless opportunities await. There's no better place to be.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 17,416
Subsidiaries: 0
12-month incidents
1
Known data breaches
2
Attack type number
1
View Profile

Jewel-Osco

150 Pierce Road, Itasca, 60143, US
Last Update: 2026-04-02
Between 750 and 799
http://www.jewelosco.com

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 employs approximately 290,000 people nationwide. All of our stores, no matter what banner they operate under, were founded around the philosophy of offering customers the products they wanted to buy at a fair price, with lots of tender, loving care. We still open our doors every day with that in mind.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 11,682
Subsidiaries: 1
12-month incidents
0
Known data breaches
3
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/carmax.jpeg
CarMax
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/jewel-osco.jpeg
Jewel-Osco
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
CarMax
100%
Compliance Rate
0/4 Standards Verified
Jewel-Osco
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

CarMax has 50.0% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Retail Industry Average (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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/carmax.jpeg
CarMax
Incidents

Date Detected: 1/2026
Type:Breach
Attack Vector: Phishing (Voice-Phishing), Exploitation of SSO Vulnerabilities, Social Engineering
Motivation: Extortion, Data Theft for Sale on Dark Web
Blog: Blog

Date Detected: 9/2025
Type:Breach
Attack Vector: Voice-based social engineering, Man-in-the-Middle (MitM) phishing, Fake MFA prompts
Motivation: Extortion, Data theft, Financial gain, Credential harvesting
Blog: Blog
https://images.rankiteo.com/companyimages/jewel-osco.jpeg
Jewel-Osco
Incidents

Date Detected: 12/2023
Type:Breach
Attack Vector: Credential Theft (Fraudulent Website)
Blog: Blog

Date Detected: 12/2022
Type:Breach
Blog: Blog

Date Detected: 8/2014
Type:Cyber Attack
Motivation: Criminal (Potential Theft of Payment Card Data)
Blog: Blog

FAQ

Jewel-Osco company demonstrates a stronger AI Cybersecurity Score compared to CarMax company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Jewel-Osco company has faced a higher number of disclosed cyber incidents historically compared to CarMax company.

In the current year, CarMax company has reported more cyber incidents than Jewel-Osco company.

Neither Jewel-Osco company nor CarMax company has reported experiencing a ransomware attack publicly.

Both Jewel-Osco company and CarMax company have disclosed experiencing at least one data breach.

Jewel-Osco company has reported targeted cyberattacks, while CarMax company has not reported such incidents publicly.

Neither CarMax company nor Jewel-Osco company has reported experiencing or disclosing vulnerabilities publicly.

Neither CarMax nor Jewel-Osco holds any compliance certifications.

Neither company holds any compliance certifications.

Jewel-Osco company has more subsidiaries worldwide compared to CarMax company.

CarMax company employs more people globally than Jewel-Osco company, reflecting its scale as a Retail.

Neither CarMax nor Jewel-Osco holds SOC 2 Type 1 certification.

Neither CarMax nor Jewel-Osco holds SOC 2 Type 2 certification.

Neither CarMax nor Jewel-Osco holds ISO 27001 certification.

Neither CarMax nor Jewel-Osco holds PCI DSS certification.

Neither CarMax nor Jewel-Osco holds HIPAA certification.

Neither CarMax nor Jewel-Osco holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was found in Nothings stb up to 1.26. Impacted is the function stbtt_InitFont_internal in the library stb_truetype.h of the component TTF File Handler. Performing a manipulation results in out-of-bounds read. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:N/A:P
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read in VS6ComFile!get_macro_mem_COM. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

V-SFT versions 6.2.10.0 and prior contain a stack-based buffer overflow in VS6ComFile!CSaveData::_conv_AnimationItem. Opening a crafted V7 file may lead to arbitrary code execution on the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6MemInIF!set_temp_type_default. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6ComFile!load_link_inf. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References