Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Uncontrolled Resource Consumption in JPA Server in HAPI FHIRGHSA-67f6-c8mx-4q2m

MEDIUMFix: hapifhir/hapi-fhir#2642

GHSA-67f6-c8mx-4q2m is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base. A fix is available for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base — see the affected versions and patch details below.

Also known asCVE-2021-32053
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.00%0.70%1.39%2.09%0.5%1.6%Apr 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-67f6-c8mx-4q2m by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

JPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenca.uhn.hapi.fhir:hapi-fhir-jpaserver-baseall versions5.4.0ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base:5.4.0

Affected Products

1 product · 1 configurations
Application
hapi fhirfhir
< 5.4.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base to 5.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67f6-c8mx-4q2m is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

JPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests.
O3 Security · Impact-Aware SCA

Is GHSA-67f6-c8mx-4q2m in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Uncontrolled Resource Consumption in JPA Server in…