People search Adobe data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 11 Adobe-linked incidents, with headline counts up to 152M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Adobe breach history matters
Adobe operates in Software (United States). Across indexed rows, recurring themes include credential theft and social engineering, cloud and database misconfiguration, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — alleged BPO path to ~13M support tickets + ~15k staff rows (“Mr. Raccoon”; early Apr)
Unverified claim — treat actor counts cautiously. In early April 2026, security blogs and trade outlets (Cybernews, SecurityOnline, Cyberpress, and others) summarized a threat-actor narrative attributing a very large support-ticket exposure to Adobe via a compromised India-based business-process outsourcing (BPO) partner and weak ticketing export controls, with monikers such as “Mr. Raccoon” appearing in coverage. Journalists emphasized screenshots of SharePoint/OneDrive-style contexts and unauthenticated bulk export claims; Adobe had not universally issued a deta Exposed categories include Support-ticket content, alleged employee and bug-bounty adjacent material per actor claims—verification mixed. BreachHistory cites approximately 13M+ affected records in this row. See the adobe2026-bpo-support-claims and canonical BreachHistory entry.
2019 — — 7.5M records
Cataloged incident. Poor security. 7.5M records. Exposed categories include Names, emails, addresses, and other PII. BreachHistory cites approximately 75 affected records in this row. See the adobe-20182019 and canonical BreachHistory entry.
2019 — — Adobe Inc.: Poor security / misconfiguration, 7,500,000 records
Cataloged incident. Data breach reported. tech organization. Method: poor security. Source: Wikipedia List of data breaches. Exposed categories include Personal and demographic data. BreachHistory cites approximately 7.5M+ affected records in this row. See the adobe2019-7500000-wiki2 and canonical BreachHistory entry.
2017 — — Adobe: Adobe has earned mockery after accidentally posting…
Cataloged incident. Adobe has earned mockery after accidentally posting its private PGP key on the firm's official security blog.Last week, Adobe's product security incident response team (PSIRT) accidentally published the private PGP key on the PSIRT blog on Friday, a lesson in what you should never reveal unless you want others to impersonate you. Exposed categories include Personal information. No attested victim count is published for this row yet. See the adobe2017 and canonical BreachHistory entry.
2014 — — Adobe: Sep 17th 2013, 152.0M records
Cataloged incident. Sep 17th 2013. Hackers obtained access to a large swathe of Adobe customer IDs and encrypted passwords & removed sensitive information (i.e. names, encrypted credit or debit card numbers, expiration dates, etc.). Approximately 38 million Adobe customers. Updated: Now 152m (May 2014) BreachHistory cites approximately 152M+ affected records in this row. See the adobe2014 and canonical BreachHistory entry.
2013 — source code and user data breach
Cataloged incident. Attackers breached Adobe's network and stole source code for multiple products and encrypted customer password hashes. Many hashes were weak (reversible) and user data was exposed. Exposed categories include Dates of birth, Source code, Credentials, Passwords (hashed). BreachHistory cites approximately 38M+ affected records in this row. See the mzfj and canonical BreachHistory entry.
2013 — — Adobe: Up to 160,000 people may have had their information…
Cataloged incident. Up to 160,000 people may have had their information exposed by a breach. Anyone who was booked into a city or county jail int he state of Washington between September of 2011 and December of 2012 may have had their Social Security number exposed.Additionally, three classes of people may have had their names and driver's license information exposed. First, people who received a DUI citation between 1989 and 2011 in the state of Washington may have had their names and drivers' license numbers ex Exposed categories include Personal information. BreachHistory cites approximately 160K+ affected records in this row. See the adobe2013 and canonical BreachHistory entry.
2013 — — Adobe: Sep 17th 2013, 36.0M records
Cataloged incident. Sep 17th 2013. Hackers obtained access to a large swathe of Adobe customer IDs and encrypted passwords & removed sensitive information (i.e. names, encrypted credit or debit card numbers, expiration dates, etc.). Approximately 36 million Adobe customers were involved: 3.1 million whose credit or debit card information was taken and nearly 33 million active users whose current, encrypted passwords were in the database taken. Correction Jan 2015: we previously reported 152m records were taking, but the remainder affe BreachHistory cites approximately 36M+ affected records in this row. See the adobeu and canonical BreachHistory entry.
2013 — — 152M records
Cataloged incident. Hacked. 152M records. Exposed categories include Names, emails, addresses, and other PII. BreachHistory cites approximately 2K+ affected records in this row. See the adobe-20132013 and canonical BreachHistory entry.
2013 — — Adobe Systems Incorporated: Hacking, 152,000,000 records
Cataloged incident. Data breach reported. tech organization. Method: hacked. Source: Wikipedia List of data breaches. Exposed categories include Personal and demographic data. BreachHistory cites approximately 152M+ affected records in this row. See the adobe2013-152000000-wiki2 and canonical BreachHistory entry.
2012 — — Adobe: A hacker released the names, email addresses, and…
Unverified claim — treat actor counts cautiously. A hacker released the names, email addresses, and encrypted passwords of 230 members of Adobe's company database. The hacker claimed to have access to over 150,000 records. Adobe announced that it would reset approximately 150,000 passwords of members of the Connectusers.com site.UPDATE (11/14/2012): The 230 people who were affected also had their titles, affiliated organizations, and usernames exposed. A number of those affected were associated with U.S. government agencies such as the Depar Exposed categories include Personal information. BreachHistory cites approximately 230 affected records in this row. See the adobe2012 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Adobe catalog entries; prioritize controls that address this class of failure.
- Cloud and database misconfiguration — appears across multiple Adobe catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Adobe catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the Adobe company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/adobe · Latest: adobe2026-bpo-support-claims.
Sources: BreachHistory catalog (11 rows for Adobe), company and regulator disclosures cited in individual breach records.