Samsung Health (com.sec.android.app.shealth): Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for Samsung Health.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Samsung Health
KRX
2026-06-22
94d ago
Waiting
Critical
Samsung Health reads and writes sixteen categories of your most sensitive health data, including heart rate, sleep and blood glucose, and feeds it into an AI system that builds a behavioural profile of you, without ever disclosing that to users. This happens even inside the children's-account mode, so a child's health data can shape that same undisclosed AI profile. Samsung never engaged a human reviewer with any of the ten findings across 94 days.
16 Art.9 health categories READ+WRITE, CVSS v4.0 CRITICAL/9.3. 926 smali: Rubin AI behavioral persona fed by health data, undisclosed, CVSS v4.0 base MEDIUM/6.9, held at HIGH under blast-radius escalation (500M+ devices). CONTROL_CARE: children's health settings, CVSS v4.0 CRITICAL/9.3. NFC blood glucose receiver corrected to MEDIUM/5.2 (proximity-gated, not remote). China NAL permission in global binary, MEDIUM/6.9 base held at HIGH under blast-radius escalation. Only reply ever received: an automated DPO ticket closure on 2026-07-02 naming no finding. Case closed and published 2026-09-24, four days after the 2026-09-20 embargo.
click to expand
GDPR Art. 9GDPRGDPR Art. 22+4
Yes
Closed
Disclosure
94d 00h 00m 00s
Published
PDF

This ledger is updated in real time as companies respond. Silence is public. Severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius.