Mutagen list and monitor operations do not neutralize control characters in text controlled by remote endpoints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N

EPSS

• CVE-2023-30844: 0.74% estimated exploitation activity in the next 30 days; percentile 54.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Mutagen command line operations, as well as the log output from mutagen daemon run, are susceptible to control characters that could be provided by remote endpoints. This can cause terminal corruption, either intentional or unintentional, if these characters are present in error messages, file paths/names, and/or log output. This could be used as an attack vector if synchronizing with an untrusted remote endpoint, synchronizing files not under control of the user, or forwarding to/from an untrusted remote endpoint. On very old systems with terminals susceptible to issues such as CVE-2003-0069, the issue could theoretically cause code execution. Patches The problem has been patched in Mutagen v0.16.6 and v0.17.1. Earlier versions of Mutagen are no longer supported and will not be patched. Versions of Mutagen after v0.18.0 will also have the patch merged. One caveat is that the templating functionality of Mutagen's list and monitor commands has been only partially patched. In…

Published by the source

5 May 2023, 02:25 UTC

Last modified by the source

5 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jmp2-wc4p-wfh2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-30844

Advisory: Mutagen list and monitor operations do not neutralize control characters in text controlled by remote endpoints
IDs: CVE-2023-30844, GHSA-jmp2-wc4p-wfh2
Record: https://patchnext.com/advisories/cve-2023-30844 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/mutagen-io/mutagen 0.17.1, 0.16.6; github.com/mutagen-io/mutagen-compose 0.17.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/mutagen-io/mutagen: affected < 0.16.6; >= 0.17.0, < 0.17.1; fixed in 0.16.6, 0.17.1
- Go github.com/mutagen-io/mutagen-compose: affected < 0.17.1; fixed in 0.17.1

## Suggested inspection (read-only)
- Go github.com/mutagen-io/mutagen: check the installed version with your package manager.
- Go github.com/mutagen-io/mutagen-compose: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/mutagen-io/mutagen, github.com/mutagen-io/mutagen-compose.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jmp2-wc4p-wfh2 (GitHub-reviewed advisory GHSA-jmp2-wc4p-wfh2 lists affected ranges: Go github.com/mutagen-io/mutagen >=0 =0.17.0 =0 <0.17.1)

Commands are suggestions: review each one before running it.