hapifhir org.hl7.fhir.core up to 6.9.3 getServer origin validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in hapifhir org.hl7.fhir.core up to 6.9.3. This impacts the function getServer. This manipulation causes origin validation.
This vulnerability is handled as CVE-2026-34359. The attack can be initiated remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability has been found in hapifhir org.hl7.fhir.core up to 6.9.3 and classified as problematic. Affected by this vulnerability is the function getServer. The manipulation with an unknown input leads to a origin validation vulnerability. The CWE definition for the vulnerability is CWE-346. The product does not properly verify that the source of data or communication is valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.4, ManagedWebAccessUtils.getServer() uses String.startsWith() to match request URLs against configured server URLs for authentication credential dispatch. Because configured server URLs (e.g., http://tx.fhir.org) lack a trailing slash or host boundary check, an attacker-controlled domain like http://tx.fhir.org.attacker.com matches the prefix and receives Bearer tokens, Basic auth credentials, or API keys when the HTTP client follows a redirect to that domain. This issue has been patched in version 6.9.4.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-34359 since 03/27/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 6.9.4 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Origin validationCWE: CWE-346 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: org.hl7.fhir.core 6.9.4
Timeline
03/27/2026 CVE reserved03/31/2026 Advisory disclosed
03/31/2026 VulDB entry created
03/31/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-fgv2-4q4g-wc35
Status: Confirmed
CVE: CVE-2026-34359 (🔒)
GCVE (CVE): GCVE-0-2026-34359
GCVE (VulDB): GCVE-100-354451
Entry
Created: 03/31/2026 20:00Changes: 03/31/2026 20:00 (64)
Complete: 🔍
Cache ID: 216:3DE:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.