<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cve-2026-81875 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-81875/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 18 Sep 2026 01:11:51 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-81875/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Unbounded DEFLATE Decompression Vulnerability in HAPI FHIR</title><link>https://feed.craftedsignal.io/briefs/2026-09-hapi-fhir-dos/</link><pubDate>Fri, 18 Sep 2026 01:11:51 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-hapi-fhir-dos/</guid><description>The HAPI FHIR SHCParser component contains an unbounded DEFLATE decompression flaw (CVE-2026-81875) allowing attackers to trigger memory exhaustion and denial-of-service.</description><content:encoded><![CDATA[<p>The HAPI FHIR library contains a vulnerability (CVE-2026-81875) in its <code>SHCParser</code> component, specifically within the <code>inflate()</code> and <code>decompress()</code> methods found in <code>SHCParser.java</code>. The library improperly handles the decompression of Smart Health Card (SHC) JWT payloads when the header specifies <code>&quot;zip&quot;:&quot;DEF&quot;</code>. Because the <code>inflate()</code> function uses a <code>ByteArrayOutputStream</code> without enforcing a maximum output size, a small, highly compressed malicious payload can be expanded into an arbitrarily large byte array in memory. An attacker who can supply SHC content for validation can exploit this to force extreme heap allocation. This vulnerability leads to severe garbage collection pressure, performance degradation, and potential application crashes due to <code>OutOfMemoryError</code>. The flaw affects <code>org.hl7.fhir.r5</code> and <code>org.hl7.fhir.validation</code> versions up to and including 6.9.11, as well as <code>org.hl7.fhir.validation.cli</code> up to version 5.0.0.</p>
<h2 id="impact">Impact</h2>
<p>The primary impact is a denial-of-service (DoS) condition affecting any validator or application utilizing the vulnerable HAPI FHIR components. Successful exploitation results in significant heap memory exhaustion, high CPU utilization during the decompression process, and potential application unavailability. This poses a high risk to healthcare-related infrastructure that processes Smart Health Cards, as an attacker can repeatedly submit crafted payloads to cause sustained service disruption or process termination.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Upgrade HAPI FHIR components to versions beyond 6.9.11 to incorporate the necessary decompression size limits.</li>
<li>For applications using <code>org.hl7.fhir.validation.cli</code>, ensure an upgrade path to a version beyond 5.0.0 is utilized.</li>
<li>Implement strict input validation or size constraints at the perimeter or API gateway level for any service that accepts and validates SHC/JWT payloads to reject oversized input before it reaches the <code>SHCParser</code>.</li>
<li>Monitor application heap usage and garbage collection metrics for anomalous spikes coinciding with the processing of incoming FHIR validation requests.</li>
</ol>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>denial-of-service</category><category>vulnerability</category><category>cve-2026-81875</category></item></channel></rss>