Loading vulnerability…
Unauthorized Resource Disclosure Through HAPI FHIR REST-Hook Subscriptions
CVE-2026-113875 is a missing-authorization vulnerability in HAPI FHIR REST-hook subscriptions, including deployments incorporated into Smile CDR. Neither subscription creation-time validation nor notification delivery enforces the subscription creator's resource-read permissions. Delivery reloads matching resources using SystemRequestDetails, allowing complete clinical resources outside the creator's authorized read scope to be sent to a designated callback endpoint. The vulnerability was reproduced on upstream HAPI FHIR 8.10.0, with vulnerable code paths also identified in versions 8.8.2, 8.10.1, and 8.12.1. Downstream Smile CDR exploitation was not independently tested.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An authorized subscription creator can obtain restricted clinical resources through subscription notifications despite being denied direct read access. Disclosure can include complete resource representations and future matching records, compromising patient-data confidentiality. Testing demonstrated disclosure of an Observation from another patient's compartment within the same partition; cross-tenant delivery was not demonstrated.
If you can’t patch tonight, do this now.
Temporarily disable REST-hook subscriptions where feasible, or restrict subscription-creation permissions to trusted users authorized to read every resource their subscriptions could expose. Review existing subscriptions and disable those that could deliver resources beyond their creators' authorized scope. These are precautionary measures, not a confirmed vendor-approved workaround; restricting direct resource reads alone does not address the disclosure path.
Patch, then assume compromise.
No fixed release or vendor-provided remediation was identified as of October 22, 2026; the vulnerable code path remained unchanged on the upstream development branch. Obtain current fix and affected-version guidance from the maintainer or product vendor. A corrective implementation must enforce the subscription creator's read authorization during subscription processing and resource delivery.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.