How severe is CVE-2023-37679?

No CVSS score has been assigned to CVE-2023-37679 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2023-37679?

Affected package information for CVE-2023-37679 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-37679?

No fixed release is recorded for CVE-2023-37679 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2023-37679 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2023-37679 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2023-37679 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2023-37679, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-37679?

CVE-2023-37679 has an EPSS (Exploit Prediction Scoring System) score of 99.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2023-37679?

CVE-2023-37679 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2023-37679?

A Nuclei detection template exists for CVE-2023-37679, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-37679 published, and has it been updated?

CVE-2023-37679 was published on August 3, 2023 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2023-37679 — connect

CVE-2023-37679 is a CWE-77 vulnerability. 2 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Aug 3, 2023

Updated

Oct 20, 2026

Affected

1 product

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

99.4%probability of exploitation in next 30 days

Very High Risk+0.24%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

A remote command execution (RCE) vulnerability in NextGen Mirth Connect v4.3.0 allows attackers to execute arbitrary commands on the hosting server.

Affected Products

1 product · 1 configurations

Application

mirth connectnextgen

1 version

4.3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A remote command execution (RCE) vulnerability in NextGen Mirth Connect …

ihteam.netNVDAug 2023

A remote command execution (RCE) vulnerability in NextGen Mirth Connect …

github.comMetasploitJan 2024

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2023-37679 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2023-37679

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-37679 -u https://target

Template: NextGen Mirth Connect - Remote Code Execution
Severity: critical
Impact: Unauthenticated attackers can exploit XML deserialization vulnerabilities to execute arbitrary code on the Mirth Connect server, potentially compromising sensitive healthcare data and integration workflows.
Remediation: Update NextGen Mirth Connect to version 4.4.1 or later that properly validates XML input and prevents unsafe deserialization attacks.

Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

A remote command execution (RCE) vulnerability in NextGen Mirth Connect v4.3.0 allows attackers to execute arbitrary commands on the hosting server.

O3 Security · Impact-Aware SCA

Is CVE-2023-37679 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works