Goat Feed · Guidance

    NextGen Healthcare Mirth Connect

    Successful exploitation of these vulnerabilities could allow an attacker to exfiltrate date or cause a denial-of-service condition.

    Back to the daily feed
    Guidance
    notable

    Blue Goat analysis

    Scored with Blue Goat's medical device cybersecurity risk methodology: STRIDE classification and CVSS v4.0 exploitability, with a severity-of-harm readout for your own ISO 14971 hazard analysis.

    Mirth Connect is an integration engine widely used to move HL7 and other clinical messages between systems, including connected devices and SaMD back ends. CISA's advisory covers three vulnerabilities. CISA lists versions below 4.7.1 as affected, and its description covers 4.7.1 and earlier.

    CVEWhat an attacker can doSTRIDECVSS v4.0 ExploitabilitySecurity impact
    CVE-2026-78224The XSLT Transformer step is built without secure parser settings, so XML external entity (XXE) injection can exfiltrate data or cause a denial of service (CWE-611)Information disclosure, Denial of serviceHighHigh
    CVE-2026-82578With XML batch processing on and the XPath option selected, batch input is parsed with no entity restrictions, so XXE injection can exfiltrate data or cause a denial of service (CWE-611)Information disclosure, Denial of serviceHighHigh
    CVE-2026-82583An authenticated user can run arbitrary SQL through a Database Connector API, which could disclose stored credentials (CWE-89)Information disclosure, Elevation of privilegeMediumHigh

    The two XXE vectors are network-reachable with no privileges and no user action, so Exploitability reads High. The SQL injection needs a low-privilege login, so it reads Medium. On Blue Goat's security matrix, the two XXE flaws are Critical and the SQL injection is High, as published.

    The published vectors describe the software, not your device. If the service is reachable only on a segmented clinical network or behind authentication, score your own deployment with the CVSS v4.0 environmental metrics before you rate your risk.

    At High exploitability, for the two XXE flaws:

    Severity from your hazard analysisSafety risk at High exploitability
    NegligibleMedium
    Minor or SeriousHigh
    Critical or CatastrophicVery High

    At Medium exploitability, for the SQL injection:

    Severity from your hazard analysisSafety risk at Medium exploitability
    NegligibleLow
    Minor or SeriousMedium
    Critical or CatastrophicHigh

    An integration engine carries clinical messages between systems. Disclosed credentials, or a stalled engine, can expose patient data or stop results and orders from reaching the systems that need them.

    What to check now

    1. Search your SBOM and your deployment for Mirth Connect 4.7.1 or earlier.
    2. Check whether your channels use the XSLT Transformer step, or XML batch processing with the XPath option.
    3. Update to Mirth Connect 4.7.2 or later, which NextGen recommends.
    4. If you're not affected, record that in a VEX statement with the justification.
    5. Re-score each affected threat, and carry patient-harm results into your ISO 14971 file.

    This analysis is informational. It is based on CISA's published advisory and does not assess any specific manufacturer's device.

    Other items reviewed by the Blue Goat team.

    Need help acting on this?

    Talk to Blue Goat Cyber

    Penetration testing, SBOM, threat modeling, and 524B submission support for MedTech.