Medium Input validation

CVE-2026-62293 — HAPI FHIR: Stored XSS in scan report via unescaped IG and profile titles

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.11, the hidden scan command concatenates attacker-controlled Implementation Guide titles, profile titles, and source references into scan.html without escaping in Scanner.java. As a result, a user who scans an attacker-supplied IG/profile and then opens or publishes the generated local/CI HTML report can trigger stored cross-site scripting, executing attacker-controlled JavaScript in the report's browser context. This issue is fixed in version 6.9.11.

Published Aug 7, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.17%

ahead of 6% of scored CVEs · Oct 15, 2026

Affects

Hapifhir

Ca.uhn.hapi.fhir:org.hl7.fhir.validation and 2 more

CVSS base

5.0

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Hapifhir Ca.uhn.hapi.fhir:org.hl7.fhir.validation, Hapifhir Ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli, Hapifhir Org.hl7.fhir.core).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Hapifhir	Ca.uhn.hapi.fhir:org.hl7.fhir.validation	version < 6.9.11	Vulnerable	CVE Program (cve.org) e CISA ADP
Hapifhir	Ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli	version < 6.9.11	Vulnerable	CVE Program (cve.org) e CISA ADP
Hapifhir	Org.hl7.fhir.core	version < 6.9.11	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.0	CVSS 3.1	Medium	1.8	2.7	security-advisories@github.com via NIST National Vulnerability Database
5.0	CVSS 3.1	Medium	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · hapifhir/org.hl7.fhir.core, hapifhir/ca.uhn.hapi.fhir:org.hl7.fhir.validation, hapifhir/ca.uhn.hapi.fhir:org.hl7.fhir.va
Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 5.0
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 7, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

github.com/hapifhir/org.hl7.fhir.core/commit/3a9befd8845f003095ed75f4b24b9a80630
x_refsource_MISC, NIST National Vulnerability Database
github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-6vcw-fq7v-4vhw
x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

Hapifhir
every CVE for this vendor

Input validation
same class

CWE-20
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-81875 HAPI FHIR: SHCParser unbounded DEFLATE decompression causes denial of service 29d
High CVE-2026-81876 HAPI FHIR: SHCParser DEFLATE infinite loop causes denial of service 29d
High CVE-2026-62295 HAPI FHIR: JSON utility parser unbounded recursion causes StackOverflow denial of service Aug 7, 2026
High CVE-2026-62296 HAPI FHIR: XHTML narrative parser unbounded recursion causes StackOverflow denial of service Aug 7, 2026
High CVE-2026-49485 HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint Jul 17, 2026
High CVE-2026-45367 HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint Jul 16, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-62293 is "HAPI FHIR: Stored XSS in scan report via unescaped IG and profile titles", rated Medium. It affects Ca.uhn.hapi.fhir:org.hl7.fhir.validation (Hapifhir); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.0 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.