# CVE-2026-93012: Email::Sender::Transport::Sendmail versions before 2.602 for Perl allow arbitrary command execution on Windows sending a message whose envel

> Attackers can execute arbitrary commands on Windows by injecting shell metacharacters into email envelope addresses processed by the Sendmail transport.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-j6jw-3jf9-6hc7, UBUNTU-CVE-2026-93012

## What is CVE-2026-93012?

CVE-2026-93012 is a critical command injection vulnerability, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Email::Sender::Transport::Sendmail versions before 2.602 for Perl allow arbitrary command execution on Windows sending a message whose envelope address reaches the shell in _sendmail_pipe.

On MSWin32 the envelope sender and every recipient go into a single command string, which open() passes to a shell. Every other platform gets the list form, which runs sendmail directly. When the caller supplies no envelope, Email::Sender::Simple takes the recipients from the To and Cc headers and the sender from the From header.

An attacker who controls one of those header addresses runs commands as the sending process.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-93012?


## How do I fix CVE-2026-93012?

No fix has been published for CVE-2026-93012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93012 being exploited?

There is no known exploitation of CVE-2026-93012 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93012 and fix it if it is affected.

What it is: CVE-2026-93012 is a critical command injection vulnerability, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93012 in the wild and no public exploit code.

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-93012/ (Markdown: https://insights.sbomify.com/CVE-2026-93012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93012
- OSV: https://osv.dev/vulnerability/CVE-2026-93012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93012/
Summaries are generated and may contain mistakes; the official description above is the record.