← Back
CVE-2026-55470
high
CVSS 7.5
Vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (CVE-2026-55470)
Summary
vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (CVE-2026-55470). Risk of unauthorized operations or information disclosure. Exploitable via ``RegexTimeout``. Mitigation: upgrade to `6.9.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55470** has been found in ca.uhn.hapi.fhir:org.hl7.fhir.dstu2.
Attackers can target a specific entry point like ``RegexTimeout`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 to **6.9.10** or later.
If unsure, ask your IT team or search "ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 CVE-2026-55470" on the vendor's site.
CVE-2026-55470 (ca.uhn.hapi.fhir:org.hl7.fhir.dstu2) — CWE-1333 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `RegexTimeout` / `org.hl7.fhir.dstu2` / `FHIRPathEngine`
Patched: `6.9.10` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-1333) exists in ca.uhn.hapi.fhir:org.hl7.fhir.dstu2. Attackers reach the vulnerable code path via ``RegexTimeout`` without authentication.
📍 Affected scope
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 — . Attack surface: `RegexTimeout` / `org.hl7.fhir.dstu2` / `FHIRPathEngine`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.9.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ca.uhn.hapi.fhir:org.hl7.fhir.dstu2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ca.uhn.hapi.fhir:org.hl7.fhir.dstu2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ca.uhn.hapi.fhir:org.hl7.fhir.dstu2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 to 6.9.10ステージング環境で 6.9.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.10"}]}]
maven
ca.uhn.hapi.fhir:org.hl7.fhir.convertors
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.10"}]}]
maven
ca.uhn.hapi.fhir:org.hl7.fhir.validation
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.10"}]}]
maven
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.10"}]}]