# Capital One (2019): what the sources say about the cloud incident

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Capital One disclosed the incident on 29 Jul 2019. The ledger reads the access path as exposed network services and request paths. The cloud or provider involved: AWS. Every field rests on the primary sources listed below. Fields no primary source states read not public.

- **Disclosed:** 29 Jul 2019
- **Incident window:** March 22 and 23, 2019 (the company's 8-K); the company determined the incident on July 19, 2019
- **Cloud or provider:** AWS
- **What was exposed:** The company stated the event affected approximately 100 million individuals in the United States and approximately 6 million in Canada. Credit card application data from 2005 through early 2019 (names, addresses, ZIP or postal codes, phone numbers, email addresses, dates of birth, self-reported income), portions of credit card customer data, about 140,000 Social Security numbers and about 80,000 linked bank account numbers of US secured credit card customers, and approximately 1 million Canadian Social Insurance Numbers. The company stated no credit card account numbers or log-in credentials were compromised.
- **How access was gained:** The company stated that a highly sophisticated individual was able to exploit a specific configuration vulnerability in its infrastructure and that the issue was not specific to the cloud. The OCC consent order finds the bank failed to establish appropriate risk management for its cloud operating environment, including network security controls.
- **Access path:** [Exposed network services and request paths](/access-paths/exposed-network-service/)
- **Kind of control that addresses it:** review and test the configuration of internet-facing request-handling components, and block workloads from reaching cloud credential services they do not need

## In the words of the source

“a highly sophisticated individual was able to exploit a specific configuration vulnerability in our infrastructure.” (company statement, [Capital One Form 8-K dated July 29, 2019, Exhibit 99.1 press release and questions](https://www.sec.gov/Archives/edgar/data/927628/000092762819000262/exhibit991-pressrelease72919.htm))

## Primary sources

- company statement: [Capital One Form 8-K dated July 29, 2019, Exhibit 99.1 press release and questions](https://www.sec.gov/Archives/edgar/data/927628/000092762819000262/exhibit991-pressrelease72919.htm), dated 29 Jul 2019
- company statement: [Information on the Capital One cyber incident](https://www.capitalone.com/digital/facts2019/), dated not stated
- regulator filing: [OCC consent order, Capital One, N.A. (AA-EC-20-51)](https://www.occ.gov/static/enforcement-actions/ea2020-036.pdf), dated 5 Aug 2020

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Capital%20One%20(capital-one-2019)) with the entry name in the subject.

## Related pages

- [Online Buddies (Jack’d dating app) 2019: jackd s3](/incidents/online-buddies-jackd-s3-2018/)
- [Veradigm Inc. 2026: vendor api](/incidents/veradigm-vendor-api-2026/)
- [IEH Corporation 2026: microsoft 365](/incidents/ieh-microsoft-365-2026/)

## Sources

- Capital One Form 8-K dated July 29, 2019, Exhibit 99.1 press release and questions: https://www.sec.gov/Archives/edgar/data/927628/000092762819000262/exhibit991-pressrelease72919.htm (read 16 Nov 2026)
- Information on the Capital One cyber incident: https://www.capitalone.com/digital/facts2019/ (read 16 Nov 2026)
- OCC consent order, Capital One, N.A. (AA-EC-20-51): https://www.occ.gov/static/enforcement-actions/ea2020-036.pdf (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/capital-one-2019/
