PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-47664 aehrc CVE debrief

Pathling Server's `$import-pnp` operation allows a caller-supplied `exportUrl` to be used as a remote FHIR Bulk Export endpoint without constraining it to a trusted source. This issue, fixed in Pathling Server 2.0.0, enables an attacker to bypass the `allowableSources` allowlist that protects the ordinary `$import` operation. As a workaround, disable the `$import-pnp` operation or do not configure PNP credentials.

Vendor
aehrc
Product
pathling
CVSS
HIGH 8.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-07
Original CVE updated
2026-09-09
Advisory published
2026-08-07
Advisory updated
2026-09-09

Who should care

Defenders responsible for Pathling Server instances, especially those in health data analytics environments, should assess exposure and prioritize verification or remediation. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-47664 allows an attacker to bypass security controls in Pathling Server, potentially impacting health data analytics security. Defenders should verify exposure and prioritize remediation.

  • Verification of Pathling Server instances for exposure
  • Potential bypass of security controls via $import-pnp operation
  • Need for workarounds or upgrades to prevent exploitation
  • Possible impact on health data analytics security

Technical summary

The $import-pnp operation in Pathling Server accepts a caller-supplied exportUrl and uses it as the remote FHIR Bulk Export endpoint without constraining it to a trusted source. This allows an attacker to bypass the allowableSources allowlist that protects the ordinary $import operation. Pathling Server 2.0.0 fixes this issue. As a workaround, disable the $import-pnp operation or do not configure PNP credentials. The vulnerability enables an attacker to bypass security controls, potentially impacting health data analytics security.

Defensive priority

Defenders should prioritize verifying exposure of Pathling Server instances, especially those with PNP credentials configured, and assess the need for workarounds or upgrades.

Recommended defensive actions

  • Verify Pathling Server instances for exposure, especially those with PNP credentials configured
  • Assess the need for workarounds or upgrades to Pathling Server 2.0.0
  • Disable the $import-pnp operation if not required
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability and its fix. Additional information on potential exploitation or affected systems is limited. Defenders should verify Pathling Server instances for exposure, especially those with PNP credentials configured, and assess the need for workarounds or upgrades. The vulnerability allows an attacker to bypass security controls, potentially impacting health data analytics security.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-47664 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-47664

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-47664 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47664

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.