On 2024-05-20, CISA added CVE-2023-43208 (NextGen Healthcare Mirth Connect) to its Known Exploited Vulnerabilities (KEV) catalog [2]. The vulnerability is listed in the catalog as "NextGen Healthcare Mirth Connect Deserialization of Untrusted Data Vulnerability" [2]. CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Backfill: this event became public on May 20, 2024 and we added it on Nov 10, 2026. It is not a new event.
CISA Adds NextGen Healthcare Mirth Connect Vulnerability CVE-2023-43208 to Known Exploited Vulnerabilities Catalog
1 min read
- Disclosed
- May 20, 2024
- Published
- Nov 10, 2026
- Last updated
- Nov 8, 2026
- CVSS basis
- Our assessment
- 85.9%, higher than 100% of CVEs
- Exploitation and patch status
- ExploitedKEV
- Attack vector
- Vulnerability status
- Actor type
- Motivation
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Government, Cross-industry
What to do nowOur advice
CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Timeline
Technical details
CISA KEV Listing Record
CISA added CVE-2023-43208 (NextGen Healthcare Mirth Connect) to the Known Exploited Vulnerabilities () catalog on 2024-05-20 [2].
Original Technical Description
NextGen Healthcare Mirth Connect contains a deserialization of untrusted data vulnerability that allows for unauthenticated via a specially crafted request. [2]
Official Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. [2]
Individual Vulnerability Record
The U.S. National Vulnerability Database (NVD) provides an independent vulnerability record and description for CVE-2023-43208 [1].
References
Official / primary3
- [1]
“NextGen Healthcare Mirth Connect before version 4.4.1 is vulnerable to unauthenticated remote code execution. Note that this vulnerability is caused by the incomplete patch of CVE-2023-37679.”
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.