How to Fix CVE-2026-34361: org.hl7.fhir.core (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-34361 is a sibling vulnerability in the same Hapifhir org.hl7.fhir.core advisory bundle as CVE-2026-34359. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-34361 matches the primary write-up.

What is different about CVE-2026-34361?

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.4, the FHIR Validator HTTP service exposes an unauthenticated "/loadIG" endpoint that makes outbound HTTP requests to attacker-controlled URLs. Combined with a startsWith() URL prefix matching flaw in the credential provider (ManagedWebAccessUtils.getServer()), an attacker can steal authentication tokens (Bearer, Basic, API keys) configured for legitimate FHIR servers...

Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-34361

Apply the patched build per the primary write-up: How to Fix CVE-2026-34359.

For a quick check, confirm the running version of org.hl7.fhir.core:

# Confirm the installed version via your package manager
dpkg -l | grep -i org.hl7.fhir.core   # Debian/Ubuntu
rpm -qa | grep -i org.hl7.fhir.core   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-34361 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-34361?

CVSS rates it 9.3 (Critical). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take org.hl7.fhir.core offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-34361 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-vr79-8m62-wh98
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-34361
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-34359

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Hapifhir org.hl7.fhir.core advisory bundle. Full procedure at how-to-fix-cve-2026-34359.*