Get started

Data breach, reported Aug 27, 2026

Kim Knobbe data breach

Kim Knobbe reported a data breach affecting 11,927 people to the HHS Office for Civil Rights on Aug 27, 2026. The filing lists the incident as unauthorized access or disclosure involving a network server and other, and names Kim Knobbe as a business associate based in Missouri. The filings reviewed do not say what data was exposed.

Reported
Aug 27, 2026
People affected
11,927

Key facts

States notified
Reported to HHS
Entity type
Business Associate (Missouri)

What happened

Kim Knobbe reported the incident to the HHS Office for Civil Rights on Aug 27, 2026. The HHS breach portal classifies it as unauthorized access or disclosure, with the location given as a network server and other.

The HHS list does not give the dates the breach began or ended, or the date Kim Knobbe discovered it. No notice letter text was available in the material reviewed, so this page cannot describe how the incident happened.

What information was exposed

The HHS entry does not list the types of data involved, and no notice letter was available. The filings reviewed do not say what was exposed. Check your letter, which should list the specific information involved in your case.

Who was notified

The HHS Office for Civil Rights breach portal lists 11,927 people affected, reported on Aug 27, 2026. The entry marks a business associate as present. No state attorney general filings or counts of residents by state appeared in the material reviewed.

What Kim Knobbe is offering

The filings reviewed do not say whether Kim Knobbe is offering credit monitoring, and they give no call center number or enrollment deadline. Check your notice letter for these details.

What to do now

  • Read your notice letter and note which information it says was involved.
  • Consider a credit freeze at Equifax, Experian and TransUnion, which is free and limits new accounts opened in your name.
  • Consider placing a fraud alert with one of the credit bureaus.
  • Review bank statements, card statements and health insurance explanations of benefits for charges or services you do not recognize.
  • If your letter says Social Security numbers were exposed, consider requesting an IRS Identity Protection PIN.
  • If it says login credentials were exposed, change those passwords and any reused ones.

Lawsuits and settlements

As of Nov 16, 2026, no settlement for this breach appears in the material reviewed, and no lawsuit is named. A breach notice is the organization's own report and is not a finding of wrongdoing. Claim will show a settlement if one opens. Claim is not a law firm and gives no legal advice.

Frequently asked questions

Is the Kim Knobbe breach letter real?

Do not rely on contact details in an email or on the letter alone. Verify by calling a phone number from Kim Knobbe's own website or official statement. The HHS breach portal does list a Kim Knobbe report dated Aug 27, 2026.

How do I know if I was affected by the Kim Knobbe data breach?

Affected people are notified by letter. HHS reports 11,927 people were affected. If you did not get a letter but think your information could be involved, contact Kim Knobbe using a number from its own website.

What information was exposed in the Kim Knobbe breach?

The HHS entry does not list the data types, and the filings reviewed do not say. Your notice letter should list what was involved.

Is Kim Knobbe offering credit monitoring?

The filings reviewed do not say. Check your notice letter for any offer and an enrollment deadline.

Is there a Kim Knobbe data breach settlement?

As of Nov 16, 2026, no settlement for this breach appears in the material reviewed. Claim will show one if it opens.

Claim finds settlements you qualify for and helps you file.

Get alerts if a settlement opens

Related pages

Last updated Nov 17, 2026 by Dev Dixit, Head of Media at Claim. Claim works to keep these details accurate. If this page differs from an official source, the official source is correct.

Claim is not a law firm, a court, a government agency, or a settlement administrator, and does not give legal advice.

This page is a plain language summary, not legal advice, and does not create an attorney client relationship.

Company names are trademarks of their owners. Claim uses them only to identify the matter described on this page and is not affiliated with those companies.

Read our full disclaimer