# CVE-2026-113873: SmileCDR HAPI FHIR improper data decompression


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-36fr-h72x-63ph

## What is CVE-2026-113873?

CVE-2026-113873 is a high-severity vulnerability in SmileCDR HAPI FHIR, published on 22 Oct 2026. 

### Official description

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.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-113873?


## How do I fix CVE-2026-113873?

No fix has been published for CVE-2026-113873 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113873 being exploited?

There is no known exploitation of CVE-2026-113873 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113873 and fix it if it is affected.

What it is: CVE-2026-113873 is a high-severity vulnerability in SmileCDR HAPI FHIR, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113873 in the wild and no public exploit code.

Affected product: SmileCDR HAPI FHIR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113873/ (Markdown: https://insights.sbomify.com/CVE-2026-113873/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113873
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113873
- OSV: https://osv.dev/vulnerability/CVE-2026-113873

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113873/
Summaries are generated and may contain mistakes; the official description above is the record.