Photon Health Metabase Breach: Inventory Every Vendor Dashboard Holding PHI

Published On
November 7, 2026
Share this post
Photon Health Metabase breach briefing for law firms: vendor BI dashboard PHI exposure, 30,625 individuals, by Emry Networks

Photon Health, a Brooklyn, NY healthcare technology and e-prescribing network acting as a Business Associate, is notifying individuals after a data security incident involving Metabase, a third-party business-intelligence application Photon runs on a self-hosted basis. Photon learned on August 21st, 2026 that an unauthorized third party exploited a previously unknown ("zero-day") vulnerability in Metabase to access certain data. Photon completed its review of the impacted data on September 4th, 2026, began notification letters about October 8th, 2026, and submitted the incident to HHS OCR on October 9th, 2026. The OCR breach portal lists 30,625 individuals. (Photon PR Newswire)

Photon states that Social Security numbers and financial information were not impacted because Photon does not collect or store that information. The investigation identified instances of name, address, phone number, date of birth, and prescription medication information for certain individuals, and notes that the types of information affected varied by person. Complimentary credit monitoring and identity theft protection for twelve to twenty-four months was offered, along with a dedicated call center for affected individuals.

For law firms, medical groups, and any regulated business that trusts Business Associates and BI dashboards with sensitive data, this is a clear test of vendor inventory, patch ownership, and who watches unusual dashboard access after hours. Here is what to confirm this week.

Watch the 60-Second Briefing: Watch our narrated YouTube Short on the Photon Health Metabase breach and what firms must inventory this week on YouTube (@emrynetworks).

Executive takeaway

  • What happened: On August 21st, 2026, Photon learned an unauthorized party exploited a previously unknown Metabase vulnerability on a self-hosted BI and customer-dashboard app. The OCR portal lists 30,625 individuals. (Photon PR Newswire)
  • What was exposed: For some people, name, address, phone, date of birth, and prescription medication information. Photon states SSNs and financial information were not impacted.
  • What to do: Inventory every BI dashboard and Business Associate that can see PHI or client data, name the patch-SLA owner, enforce least privilege, and confirm who answers unusual dashboard access overnight.
  • Standard IT vs. Defensible IT: Standard IT inventories the EHR or practice system and stops. Defensible IT inventories every dashboard that can see sensitive data and keeps 24x7 evidence for insurers and ABA Rule 1.6c.

What happened at Photon Health?

Photon's October 8th, 2026 notice states that on August 21st, 2026 the company learned an unauthorized third party exploited a previously unknown security flaw in Metabase. Photon uses Metabase on a self-hosted basis for business intelligence, product metrics, and customer dashboards. Photon says it took immediate measures to secure the application, engaged cybersecurity experts, and completed a thorough review of the impacted data on September 4th, 2026. Photon reports no evidence of misuse or attempted misuse of the potentially affected information. (Photon PR Newswire)

HHS OCR lists Photon Health (NY, Business Associate) with 30,625 individuals, a hacking/IT incident, and an October 9th, 2026 submission date. Some state listings show a smaller resident count (for example, Texas AG materials have been summarized at 3,085 residents). The OCR figure of 30,625 is the national count; state listings are separate, smaller counts.

What is Metabase and why did it hold PHI?

Metabase is a business-intelligence and dashboard product. Photon ran it self-hosted to support BI, product metrics, and customer dashboards. That means prescription-related and demographic data that looked like "analytics" still sat in a system many firms never treat as a regulated data store. Photon's notice did not name a public Metabase CVE identifier.

What data may have been acquired?

Photon identified instances of name, address, phone number, date of birth, and prescription medication information for certain individuals. Not every person had every element exposed. Photon states SSNs and financial information were not impacted because Photon does not collect them.

Why does this matter for a law firm?

Law firms rely on e-prescribe vendors, practice-management portals, e-discovery analytics, and BI tools that hold client or patient data outside the "core" matter system. ABA Model Rule 1.6(c) requires a lawyer to make reasonable efforts to prevent the unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client. Reasonable efforts include knowing which vendors and dashboards can see that information. (ABA Model Rule 1.6)

Cyber insurance applications and renewals ask the same question in underwriting language: which vendors touch sensitive data, whether those systems were in scope for monitoring, and whether dashboards outside the primary EHR or DMS were inventoried. A Metabase-class tool that nobody listed is a claim-file problem as well as a confidentiality problem.

Is a yearly vendor questionnaire enough?

No. A questionnaire filed once a year does not prove that a self-hosted BI dashboard was patched on time, that accounts were least privilege, or that unusual exports were reviewed overnight. Insurers and ABA 1.6c both care about living inventories and dated evidence.

What do HIPAA Business Associate rules expect?

HIPAA covered entities and Business Associates must safeguard ePHI and manage vendor relationships under the Security Rule, including administrative and organizational requirements that reach systems BAs use to create, receive, maintain, or transmit ePHI. (eCFR Part 164) A BI dashboard that can query prescription data is in that class even when staff think of it as "only analytics."

What should counsel ask its IT provider this week?

Ask for dated answers in writing, not a slide deck.

  1. Which BI tools and Business Associates can see PHI or client data today? Include self-hosted dashboards, customer portals, and analytics replicas.
  2. Who owns the patch SLA for every Metabase-class dashboard, and when was the last apply? Name the person and the date.
  3. Are dashboard accounts least privilege, with MFA that holds up? Shared "reporting" logins should be gone.
  4. If unusual dashboard access hits at 2 a.m., who answers, and where is that logged? Name the person or MDR team and the evidence location.
  5. When was the BA inventory last reconciled against production? Ask for the ticket or change record.
  6. Save the answers. Put the written replies, dates, and reviewer name in your confidentiality and cyber-insurance file.

What if a vendor just disclosed a dashboard incident?

Treat every connected account and export path as suspect until reviewed. Preserve dashboard and IdP logs before cleanup, confirm whether your clients' or patients' data elements were in scope, and open your incident response plan with privacy counsel. Document the awareness date.

Emry Networks 4-layer Defensible IT blueprint for vendor dashboards: BA inventory, patch SLAs, least-privilege BI access, and 24x7 MDR with compliance evidence

Standard IT vs. Defensible IT

Standard IT inventories the EHR or practice-management system and treats BI tools as optional reporting. Defensible IT can show every dashboard and BA that can see sensitive data, who patches them, who can query them, and who watched overnight alerts.

Standard IT says "our core system is fine." Defensible IT can show the BA inventory, the dashboard patch SLA, the least-privilege roles, and the 24x7 case notes, with dates.

Standard IT looks like this:

  • Vendor list limited to the primary EHR, DMS, or PMS.
  • Self-hosted BI and customer dashboards out of scope for monitoring.
  • Patch and access reviews during business hours only.
  • A yearly questionnaire counted as the finish line, with thin evidence for an insurer.

Defensible IT looks like this:

  • A living inventory of every BI tool and Business Associate that can see PHI or client data, delivered through compliance-first managed IT services.
  • Named patch-SLA owners, least-privilege dashboard roles, and MFA that holds up.
  • Alerts on unusual dashboard queries or exports.
  • 24x7 managed detection and response so a 2 a.m. dashboard alert gets a human response that night, with notes that land in the compliance binder.

How does Emry Networks help regulated businesses in Jacksonville FL, Manchester NH, and nationwide?

Emry Networks provides managed IT, cybersecurity, and compliance services for law firms, medical and dental groups, financial advisors, defense contractors, and other regulated industries across the United States, from hubs in the Jacksonville, FL and Manchester, NH areas. We work on all-inclusive flat monthly pricing, so an overnight incident response does not bring a surprise invoice. Every engagement follows a 90-day blueprint:

  • Phase 1 (Days 1-30): Scoping, a baseline gap assessment, and software deployment. We inventory BAs, BI dashboards, and admin paths to sensitive data, confirm MFA strength, and deploy EDR, logging, and device management.
  • Phase 2 (Days 31-60): Tool implementation and policy authoring. We tighten dashboard roles and session lifetimes, route unusual-access alerts to 24x7 coverage, and write policies that match what actually runs.
  • Phase 3 (Days 61-90): Verification and a second gap assessment. We test that alerts reach a person at any hour, confirm fixes, and hand you before-and-after evidence.

Not sure which vendor dashboards can see your clients' or patients' data? Book a 30-Minute Risk Assessment. We will review your BA inventory, dashboard scope, and after-hours alert path, and tell you plainly what we find. Prefer the phone? Call (603) 202-3200.

Next Steps for Your Business

Frequently asked questions

What happened in the Photon Health Metabase breach?

On August 21st, 2026, Photon learned an unauthorized third party exploited a previously unknown vulnerability in Metabase, a self-hosted BI and customer-dashboard app. Photon finished its data review on September 4th, began notices about October 8th, and submitted to HHS OCR on October 9th, 2026. OCR lists 30,625 individuals.

What data was exposed?

Photon reports that for some people the data may have included name, address, phone, date of birth, and prescription medication information. Photon states SSNs and financial information were not impacted because Photon does not collect them.

Why should a law firm care about a healthcare BA breach?

Firms rely on e-prescribe vendors, practice systems, and BI dashboards that hold client or patient data outside the core matter system. ABA Rule 1.6c and cyber insurers both expect you to know which vendors can see that data and how they are monitored.

Do we need a CVE number to act?

No. Photon's notice describes a previously unknown Metabase vulnerability and does not publish a CVE identifier. Inventory and patch ownership do not wait on a CVE string.

How does 24x7 MDR differ from a business-hours ticket queue?

A business-hours queue may not see a 2 a.m. dashboard-access alert until the next morning. 24x7 managed detection and response puts a person on that alert the same night and leaves dated evidence for your insurer and auditor.

Next steps

See how we help businesses in your industry, or book a short call to talk through where you stand today.

Share this post

Read more from our team

Explore insights on compliance and security.

Ready to strengthen your compliance?

Get hands-on assessment and guidance from our compliance experts.