cmd.exe has detected a shell and will now open another one. If this problem persists, open another one.
Advisory
- CVSS score
- 10.0 CriticalDisplayed as 10.~1
- Attack vector
- Win+R, “cmd”, EnterFive keystrokes, counting the R
- Affected versions
- Windows NT onwardsRoughly three decades of exposure
- Relationship to PowerShell2Shell
- ParentPowerShell2Shell is the remake
- Exploited in the wild
- ConstantlyBy every IT helpdesk on earth
- Vendor status
- No responseThe vendor contact is on a floppy disk
What’s going on
When the PowerShell2Shell disclosure went out, researchers asked the obvious question: did the older shell do it first? It did. Typing cmd at a Command Prompt has spawned a second Command Prompt since before most of the researchers were born.
Analysts describe Cmd2Shell as “PowerShell2Shell, but beige”. It offers fewer features, no object pipeline and no tab completion worth mentioning, yet delivers exactly the same impact: none.
Researchers also confirmed that the flaw survives a full upgrade path from Windows NT to Windows 11, making it more stable than most production systems.
Proof of concept
C:\>cmd
Advanced attackers can chain the exploit with cmd /k cmd, which opens a shell that opens a shell and then waits politely.
Save the exploit as a .bat file for the authentic experience, complete with a window that flashes and closes before you can read the error.
Mitigation
- Type
exit. Shell count goes down by one. - Repeat until the window closes.
- Migrate to PowerShell. Note that this leaves you exposed to PowerShell2Shell.
- Migrate back to cmd. Note that this leaves you exposed to Cmd2Shell.
- Continue alternating until retirement.
Disclosure timeline
| When | What happened |
|---|---|
| 1990s | Vulnerability shipped. Nobody noticed, because it was a feature. |
| 2006 | PowerShell released. Inherits the bug, as children do. |
| 2026, day 0 | PowerShell2Shell gets a logo. cmd.exe feels left out. |
| Day 0, +2 min | Researcher types cmd into cmd. Second shell appears. |
| Day 0, +3 min | cmd2shell.com registered. |
| Day 0, +40 min | Vendor notified by fax. Fax machine also found to be vulnerable. |
| Day 1 | Embargo broken by a researcher who couldn’t stop laughing on a call. |
The 2Shell family tree
Every vulnerability now needs “Shell” in its name to be taken seriously. Cmd2Shell would like to point out that it was a shell before it was cool.
| Name | Year | Cmd2Shell’s opinion |
|---|---|---|
| Shellshock | 2014 | Respectable. A shell bug in an actual shell. |
| Log4Shell | 2021 | Set the naming trend. We have mixed feelings. |
| Spring4Shell | 2022 | Riding the coat-tails. |
| Text4Shell | 2022 | Riding the coat-tails of the coat-tails. |
| React2Shell | 2025 | Changed the 4 to a 2. Bold. |
| PowerShell2Shell | 2026 | Our grandchild. Gets all the attention. |
| Cmd2Shell | 1990s / 2026 | The original. Accept no substitutes. |
Questions
Am I affected?
If your computer has a Start button, almost certainly.
Is this just PowerShell2Shell again?
No. PowerShell2Shell is just Cmd2Shell again.
Will there be a patch?
The patch is distributed as 14 floppy disks. Please insert disk 1.
Does it work with Unicode?
Run chcp 65001 and hope.
Why does the CVE end in ~1?
The real name was too long for DOS. CVE-2026-2SHEL~2 is reserved for the sequel.