Skip to main content

SmileCDR HAPI FHIR EUVDEUVD-2026-108273

| CVE-2026-113873 HIGH
Improper Handling of Highly Compressed Data (Data Amplification) (CWE-409)
2026-10-22 cisa-cg GHSA-36fr-h72x-63ph
8.7
CVSS 4.0 · Vendor: cisa-cg
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed FHIR decompressing endpoint
  2. Exploit
    Send small highly compressed payload
  3. Execution
    Trigger massive in-memory expansion
  4. Impact
    Exhaust JVM heap / crash service

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
Exploitation Conditions

The affected Smile CDR / HAPI FHIR service must accept and decompress attacker-supplied compressed input (e.g. a gzip/deflate-encoded HTTP request body or compressed FHIR payload) on a network-reachable endpoint; the flaw triggers when that compressed data is expanded during processing. Per CVSS AV:N/AC:L/PR:N/UI:N no authentication, user interaction, or special privilege is required, so default internet- or network-exposed FHIR endpoints that handle compressed payloads are reachable. Limiting factors: the description scopes impact to 'certain services' (only some components crash, not necessarily the whole platform), the endpoint must be exposed to the attacker and must actually decompress untrusted input, and impact is confined to availability - there is no data disclosure or modification. The available sources do not further specify which exact services or compression formats are affected.

Impact

The signals are consistent and point to a genuine but single-dimension (availability-only) risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remote, low-complexity, unauthenticated attack with no special attack requirements, and the impact metrics confirm this is purely a denial-of-service issue: VC:N/VI:N (no confidentiality or integrity impact) with VA:H (high availability impact). My independent CVSS 3.1 reading (A:H only, ~7.5) agrees - this is not a code-execution or data-breach flaw, so the 8.7 score reflects easy, unauthenticated reachability against an availability sink rather than broad technical impact. The vuln.today Decision label is 'this_week' (not act_now/emergency), which matches a serious-but-not-fire-drill posture. Key corroborating exploitation signals are MISSING, not negative: no EPSS score is provided, there is no CISA KEV listing, and no PoC/exploit reference appears in the input - so exploitation probability cannot be quantified from this data. CWE-409 (improper handling of highly compressed data, i.e. a decompression/zip-bomb class) aligns with the DoS description. Net: a real priority to patch for availability-sensitive healthcare deployments, but the absence of confidentiality/integrity impact and of any exploitation evidence argues against treating it as an emergency; the 'this_week' label is the appropriate urgency anchor.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a small but highly compressed payload (e.g. a gzip-encoded request body) to an exposed Smile CDR / HAPI FHIR endpoint that decompresses input. On decompression the data expands enormously, exhausting JVM heap and crashing or hanging affected services, denying care-delivery systems access to the FHIR API. No public exploit identified at time of analysis; exploitation requires only the ability to reach a decompressing endpoint, consistent with the AV:N/AC:L/PR:N/UI:N vector.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Oct 22, 2026

SmileCDR HAPI FHIR can be driven into heap exhaustion and service crashes by unauthenticated attackers who submit highly compressed payloads that are expanded during server-side decompression. The CVSS:4.0 score of 8.7 (assessed as CVSS:3.1 AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H) reflects an availability-only impact: no confidentiality or integrity loss, no privileges or user interaction required, but a high availability hit against network-reachable FHIR endpoints that decompress untrusted input. No public exploit code has been identified at the time of analysis and the CVE is not listed in CISA KEV; the vuln.today decision label is this_week, so treatment should be scheduled in the current patch cycle rather than treated as an emergency, and deployed instances that accept compressed request bodies should be prioritized.

Earlier versions of this analysis (1)
v1 Oct 22, 2026 - 18:38 CVSS 7.5

Heap exhaustion and service crashes in the Smile CDR HAPI FHIR server arise because the product does not properly handle highly compressed input, letting an unauthenticated remote attacker submit compressed payloads whose decompressed size overwhelms server memory (CVSS 7.5, availability-only impact). Instances are exposed only if they accept and decompress client-supplied compressed data on a network-reachable endpoint; the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms no credentials or user interaction are needed against such an endpoint. No public exploit has been identified at time of analysis (no KEV or PoC reference in the supplied sources), although the flaw is rated a this_week priority item by vuln.today.

RemediationAI

No vendor-released patch or fixed version is identified in the available data, so confirm the current status against the CISA CSAF advisory va-26-294-01 (https://raw.githubusercontent.com/cisagov/CSAF/develop/cisaf_files/IT/white/2026/va-26-294-01.json) and the NVD record (https://nvd.nist.gov/vuln/detail/CVE-2026-113873) before planning the upgrade, and apply the vendor's fixed build once it is published. In the interim, because the flaw requires the service to decompress attacker-supplied compressed input on a reachable endpoint, the effective compensating controls act on that precondition: disable acceptance of compressed request bodies (gzip/deflate Content-Encoding) at the FHIR front end or reverse proxy, at the cost of losing bandwidth savings and breaking clients that rely on compressed uploads; or cap the maximum decompressed request size and reject oversized expansions before parsing, which reduces but does not eliminate the heap-exhaustion path and requires tuning to avoid rejecting legitimate large FHIR bundles. Additionally, restrict network exposure of FHIR endpoints that process compressed payloads to trusted client networks, accepting that this is not viable for public interoperability APIs. Because the assessment notes the sources do not specify which individual services are affected, apply these controls across all SmileCDR components that decompress inbound content rather than only the primary FHIR endpoint.

Affected VersionsENISA

HAPI FHIR 0 <*

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The weakness is CWE-409, improper handling of highly compressed data - the decompression-bomb class in which a small attacker-supplied compressed blob expands to a vastly larger in-memory representation. In HAPI FHIR / SmileCDR deployments the relevant surface is the FHIR REST layer: HTTP request bodies and FHIR payloads can be gzip/deflate encoded, and the server must inflate them before parsing, which lets a compact request consume heap disproportionate to its wire size. The CPE cpe:2.3:a:smilecdr:hapi_fhir:*:*:*:*:*:*:*:* and the EUVD range of "0 <*" indicate no version boundary is published, i.e. the record does not distinguish fixed from vulnerable releases. Notably, the assessment states that the sources do not specify which exact SmileCDR services or which compression formats are affected, and the description scopes the crash impact to "certain services" rather than guaranteed whole-platform failure; the CWE classification describes the flaw class, not a confirmed statement about how decompression is triggered in each component.

Know when Hapi Fhir gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisa-cg) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Remote unauthenticated request to a decompressing endpoint with no UI (AV:N/AC:L/PR:N/UI:N); impact is availability-only (A:H), no confidentiality or integrity effect, scope unchanged.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cisa-cg).

CVSS VectorVendor: cisa-cg

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Analysis Updated
Oct 22, 2026 - 19:29 vuln.today
v2 - CVSS changed
CVSS changed
Oct 22, 2026 - 19:23 NVD
7.5 (HIGH) 8.7 (HIGH)
CVE Published
Oct 22, 2026 - 17:57 cve.org
HIGH 7.5

DescriptionCVE.org

SmileCDR HAPI FHIR does not properly handle highly compressed data, allowing an unauthenticated attacker to send compressed payloads that exhaust server heap or crash certain services when decompressed.

Executive ViewAI

Why It Matters

CVE-2026-113873 exposes SmileCDR HAPI FHIR deployments to unauthenticated heap exhaustion and service crashes through malicious compressed payloads, directly threatening availability of clinical data exchange. Leadership should prioritize remediation in the current patch cycle to prevent disruptions to patient care and operational continuity, especially for internet-facing FHIR endpoints.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling compressed request body handling if not required, enforcing strict payload size limits, rate limiting, and restricting network access to trusted clients.

Threat Intelligence Overview

Prevalence
Medium
widely used FHIR server in healthcare, but industry-specific not universal
Social Media
1
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy