Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-fgv2-4q4g-wc35

HAPI FHIR Core has Authentication Credential Leakage via Improper URL Prefix Matching on HTTP Redirect

CVSS 7.4 HighEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 30 Mar 2026, 17:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ca.uhn.hapi.fhir:org.hl7.fhir.coreMaven<6.9.46.9.4
ca.uhn.hapi.fhir:org.hl7.fhir.utilitiesMaven<6.9.46.9.4
Identifiers
GHSA-fgv2-4q4g-wc35 · CVE-2026-34359
Weakness (CWE)
CWE-346
Tags
Published
30 Mar 2026
Updated
31 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The HAPI FHIR Core packages org.hl7.fhir.core and org.hl7.fhir.utilities, versions before 6.9.4, match configured server URLs by string prefix when sending authentication credentials. An attacker who can redirect a request to a domain whose name begins with a configured server URL (for example, a lookalike domain appended to a configured terminology server) can receive Bearer tokens, Basic auth credentials, or API keys, and can potentially bypass the HTTPS requirement. Upgrade to version 6.9.4 or later.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.