Developing threat ยท updated Nov 17, 2026

Sh2Sh.
Are you exposed?

A reported post-authentication flaw in the POSIX shell in which an attacker with shell access can obtain… shell access.

CVE-2026-0000001 CVSS 11.0 / 10 Logo: ready. Patch: pending.

This analysis is FearStack's reading of a man page, ahead of vendor confirmation. Vendor could not be identified. Read the full analysis →

30-second exposure check

Likely in scopeTick boxes to refine your verdict.

The short version

The bug

Running sh -c sh spawns a shell. Researchers confirmed the behaviour is reproducible on every system tested, including one that was turned off.

The impact

Reported as RCE. Not proven yet; the most likely outcome today is a second prompt.

Chained, an attacker may achieve exit.

Who's in scope

Everyone since 1971. Switching shells won't help: bash, zsh, fish and nu are updated, more sophisticated versions of the same exploit. See the evolution →

Four steps for security teams

01

Inventory

Run ls /bin/*sh. Each result is a finding. Export to a spreadsheet and email it to the board.

02

Prioritize

Focus first on shells reachable from other shells. That's all of them.

03

Stopgap

Test chmod 000 /bin/sh. Stopgap is not vendor-confirmed and may slow down your ability to do anything.

04

Patch & watch

Apply the patch when it ships. Until then, watch your shell closely. Do not blink.

Already running FearStack?

You're protected. FearStack customers already see Sh2Sh findings in their dashboard: 100% of hosts, critical, red, blinking. Our AI agent detected the shell, then opened a shell to investigate, generating a new finding.

Think you're hit? If you are reading this in a browser that was launched from a shell, you are. Read the analysis or talk to us →

A request to the industry

Stepping out of character for a moment: please stop sensationalizing vulnerabilities for marketing.

Defenders spend real hours on logos, countdown badges and CVSS numbers built for headlines rather than accuracy. Every overhyped bug teaches people to tune out the next one, including the one that matters.

Lead with the facts: what's affected, how it's exploited, and what to do. Say clearly what isn't confirmed. Credit the researchers and maintainers. Put the demo button somewhere other than the incident response.