Cmd2Shell

The original shell-to-shell vulnerability. An attacker with a Command Prompt can obtain a Command Prompt. Tracked as CVE-2026-2SHEL~1, because the full name wouldn’t fit in 8.3.

C:\WINDOWS\system32\cmd.exe
Shell depth: 1Privileges gained: 0
cmd.exe

cmd.exe has detected a shell and will now open another one. If this problem persists, open another one.

ADVISORY.TXT - Notepad

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
README.TXT - Notepad

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.

EXPLOIT.BAT

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.

MITIGATE.HLP

Mitigation

  1. Type exit. Shell count goes down by one.
  2. Repeat until the window closes.
  3. Migrate to PowerShell. Note that this leaves you exposed to PowerShell2Shell.
  4. Migrate back to cmd. Note that this leaves you exposed to Cmd2Shell.
  5. Continue alternating until retirement.
TIMELINE.LOG

Disclosure timeline

WhenWhat happened
1990sVulnerability shipped. Nobody noticed, because it was a feature.
2006PowerShell released. Inherits the bug, as children do.
2026, day 0PowerShell2Shell gets a logo. cmd.exe feels left out.
Day 0, +2 minResearcher types cmd into cmd. Second shell appears.
Day 0, +3 mincmd2shell.com registered.
Day 0, +40 minVendor notified by fax. Fax machine also found to be vulnerable.
Day 1Embargo broken by a researcher who couldn’t stop laughing on a call.
FAMILY.TRE

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.

NameYearCmd2Shell’s opinion
Shellshock2014Respectable. A shell bug in an actual shell.
Log4Shell2021Set the naming trend. We have mixed feelings.
Spring4Shell2022Riding the coat-tails.
Text4Shell2022Riding the coat-tails of the coat-tails.
React2Shell2025Changed the 4 to a 2. Bold.
PowerShell2Shell2026Our grandchild. Gets all the attention.
Cmd2Shell1990s / 2026The original. Accept no substitutes.
FAQ.HLP

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.