# CVE-2026-107570: Use of Out-of-range Pointer Offset in mutt > An attacker can execute arbitrary code by sending a crafted email with a malicious Content-Type header to a user of the Mutt email client. - **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 8 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** AZL-106736, CLSA-2026-1792092200, DEBIAN-CVE-2026-107570, GHSA-3756-2mxq-33pr, MGASA-2026-0517, OESA-2026-4644, OESA-2026-4645, OESA-2026-4646, OESA-2026-4647, SUSE-SU-2026:24242-1, SUSE-SU-2026:4685-1, SUSE-SU-2026:4818-1, SUSE-SU-2026:4857-1, UBUNTU-CVE-2026-107570, openSUSE-SU-2026:12094-1, openSUSE-SU-2026:22099-1 ## What is CVE-2026-107570? CVE-2026-107570 is a low-severity memory corruption vulnerability in mutt, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description heap OOB write in convert_file_from_to() via a crafted Content-Type header allows attacker to OOB write when email is used as a template. Weakness: CWE-823 (Use of Out-of-range Pointer Offset) ## Which versions are affected by CVE-2026-107570? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mutt` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.2.14-150600.3.9.1 | | `mutt` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.10.1-55.36.1 | | `mutt` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 2.2.14-150600.3.9.1 | | `mutt` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.2.16-160000.3.1 | | `mutt` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.10.1-55.36.1 | | `mutt` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.10.1-150000.3.32.1 | | `mutt` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 2.2.14-150600.3.9.1 | | `mutt` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.2.16-160000.3.1 | | `mutt` | openSUSE:Leap 16.0 | All versions | 2.2.16-160000.3.1 | | `mutt` | openSUSE:Tumbleweed | All versions | 2.4.2-2.1 | ## How do I fix CVE-2026-107570? Apply the vendor's patch. ## Is CVE-2026-107570 being exploited? There is no known exploitation of CVE-2026-107570 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107570 and fix it if it is affected. What it is: CVE-2026-107570 is a low-severity memory corruption vulnerability in mutt, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-107570 in the wild and no public exploit code. Affected product: mutt. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107570/ (Markdown: https://insights.sbomify.com/CVE-2026-107570/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107570 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107570 - OSV: https://osv.dev/vulnerability/CVE-2026-107570 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107570/ Summaries are generated and may contain mistakes; the official description above is the record.