Skip to main content
VulnerabilityPublished

CVE-2026-82583: NextGen Healthcare Mirth Connect · SQL Injection

Affects NextGen Healthcare Mirth ConnectSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NextGen HealthcareMirth ConnectAffected
  • <=4.7.1
Fixed in–

AI-suggested

Until a fix is available, restrict access to the Database Connector API to trusted authenticated users only and monitor for suspicious activity related to SQL injection attempts.

Description

NextGen Connect (Mirth Connect) versions 4.7.1 and earlier allow an authenticated user to execute arbitrary SQL through a Database Connector API, which could result in disclosure of stored credentials for connected systems, arbitrary file write, and a denial-of-service condition.

References

Community reviews

Loading reviews…