All Breaches
July 10, 2025 Verified Sensitive Record Media

Washington Post Data Breach

The 2025 Washington Post data breach resulted from exploitation of a previously unknown vulnerability in Oracle E-Business Suite software used by the organization.

At least 862
Affected People
5
Data Types
At least Low
Severity
Oct 10, 2026
Last updated

This classification is based on a reviewed lower bound; the actual impact and severity may be higher.

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

1 sensitive5
  • Health insurance information
  • Names
  • Social security numbers
  • Government IDs
  • Financial account information

About This Breach

A Texas regulator record confirms that at least 862 people were affected; the nationwide total has not been disclosed.

The Washington Post is a U.S. news organization operating print and digital publications. The incident involved data held in internal Oracle business applications, not accounts on the newspaper's news website.

How Did the Incident Occur?

The Washington Post began a forensic investigation after a threat actor contacted it in October 2025 and claimed access to its Oracle applications. The review confirmed that data was accessed and acquired without authorization between July 10 and August 22, 2025. The same vulnerability affected many Oracle customers and was not specific to The Post. A detailed data review was completed on June 10, 2026.

What Information Was Affected?

According to the Texas record, the information could have included names, Social Security numbers, government-issued identification such as passports or state IDs, financial information, and health-insurance information, depending on the person. The public sample notice does not show which fields applied to each recipient, so not every category necessarily applied to every person.

How Did The Washington Post Respond?

The organization investigated with external forensic specialists, secured its Oracle environment, and applied patches as they became available. It notified people identified in an initial review and then contacted additional people found during a deeper analysis. Notice recipients were offered either 12 or 24 months of identity-protection services.

What Should Affected People Do?

Notice recipients should review financial accounts, credit reports, and health-insurance statements for unfamiliar activity. People whose Social Security or government-ID information was involved may consider a credit freeze or fraud alert. Messages referring to the incident should be verified through known official Washington Post channels instead of links in unexpected emails.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information