Naming Advisory E4S-001 · Published 2026 · Last branded: just now
EVERYTHING4SHELL
One name for every vulnerability, so you never have to read a CVE number again.
- Attack vectorConference talk
- ComplexityNone, it has a logo
- Privileges requiredA domain registrar
- User interactionRetweet
This is a parody. Everything4Shell is not a real vulnerability, not a real advisory, and not affiliated with the CVE Program, MITRE, NIST, FIRST, CISA, the Apache Software Foundation, or anyone who has ever shipped working software.
Am I affected?
A rigorous four-question triage flow, developed over one weekend by people who had already bought the domain.
The Naming Engine
Type in any technology. Receive a disclosure-ready brand, a severity score, and a press release you can send before you have read the code.
Alternate brandings
Launch readiness
Press release
The Taxonomy
The Shell Naming Authority recognizes seven approved suffix families. Anything else is a CVE number, and nobody is going to read that.
| Family | Era | Signals | Prior art | Logo requirement |
|---|---|---|---|---|
-4Shell | 2021– | Remote code execution, probably in a logger | Log4Shell, Spring4Shell, Text4Shell | Flame, or a shell prompt |
2Shell | 2024– | The sequel. Same bug class, new package | nginx2Shell* | Roman numeral II |
Shell- (prefix) | 2021– | A chain of three bugs you will describe as one | ProxyShell, ProxyLogon | Isometric proxy diagram |
-bleed | 2014– | Memory disclosure; you will leak 64KB at a time | Heartbleed, Zenbleed | Something anatomical, bleeding |
-ageddon / -pocalypse | 2015– | Scale. Patch coordination across an entire ecosystem | Glibc-geddon*, Dependopocalypse* | Horsemen, optional |
| Hardware mononym | 2018– | Microarchitectural, unpatchable, 40% perf hit | Spectre, Meltdown, Rowhammer | Ghost, or liquid metal |
regre- / -gate | 2024– | A bug that was fixed in 2006 and has returned | regreSSHion | A circle with an arrow |
* Illustrative. These ones are made up, which is exactly how the real ones started.
Naming rules (mandatory, unenforceable)
- Four syllables maximum. It has to survive being said out loud on a conference stage by someone who is nervous.
- The domain comes first. Register before you report. A vulnerability without a landing page is just a ticket.
- The logo precedes the patch. If there is no logo, journalists will invent one, and it will be a padlock.
- Never name it after the vendor. Name it after the ecosystem, so that everyone has to care.
- Severity is a marketing field. CVSS caps at 10, which is a failure of imagination.
- One bug, one name. Three bugs, also one name. Nine bugs, one name and a keynote.
Severity vs. Hype
Technical severity has a ceiling. Branding does not. The gap is where this website lives.
Named vulnerabilities: CVSS score vs. Hype Index
CVSS values are the published base scores (approximate). The Hype Index is entirely fabricated, in keeping with the rest of the field.
A short history of the movement
Twelve years from “we should give this one a name” to “we should give this one a brand book.”
- 2014Heartbleed ships with a logo and a website. Security communication is never the same. This was, to be fair, a genuinely good idea.
- 2014Shellshock establishes that “shell” is the most alarming word in English.
- 2017EternalBlue proves a name can outlive its vendor’s patch cycle by several years.
- 2018Spectre and Meltdown arrive with two logos and a performance regression.
- 2021Log4Shell. A logging library becomes a holiday-season cancellation event. The -4Shell suffix is born.
- 2022Spring4Shell and Text4Shell arrive within months. The suffix is now a template.
- 2024regreSSHion demonstrates that puns are also acceptable.
- 2025Naming velocity exceeds patching velocity. Several vulnerabilities are now named twice.
- 2026The Shell Naming Authority publishes Everything4Shell, a single name covering all current and future vulnerabilities. Disclosure is now O(1).
Responsible Naming Disclosure
Our coordinated process, in full.
Day 0
Researcher discovers bug. Researcher checks domain availability. Researcher does not yet verify the bug.
Day 0, + 4 minutes
Domain registered. Logo commissioned. Name reserved with the SNA for a fee of one (1) t-shirt.
Day 1–89
Vendor is notified. Vendor asks what a “4Shell” is. Microsite is built. Press list is warmed.
Day 90
Coordinated release of the name. The patch follows at an unspecified later date, and the name is already trending.
The SNA reserves the right to rename your vulnerability if your name has five syllables.
Mitigation guidance
Because Everything4Shell affects everything, remediation is correspondingly broad.
Immediate
- Patch everything. Yes, that too.
- Inventory your dependencies. Realize you cannot.
- Forward this page to leadership before a vendor does.
Compensating controls
- Egress filtering, which you have been meaning to do since 2021.
- An SBOM that someone actually reads.
- Rename your production environment to
stagingso attackers lose interest.
Configuration
# /etc/everything4shell.conf
#
# Ship this file. It is as effective as the last six
# mitigations you pasted out of a vendor blog post.
naming.enabled = true
naming.suffix = 4shell # 2shell also accepted
naming.max_syllables = 4
severity.ceiling = disabled # 10 was holding us back
disclosure.domain_first = true
patch.eta = "soon"
blame.target = "the dependency"
This file does nothing. Neither does the one your scanner asked for.
FAQ
Is this a real vulnerability?
No. Everything4Shell is satire. There is no CVE, no exploit, no advisory, and no patch. If a scanner reports Everything4Shell, the scanner is also satire.
Why 4 and not for?
Because Log4j contained a 4, and the entire industry pattern-matched on it rather than on the vulnerability class. This is the central joke and also, unfortunately, the central truth.
Can I use these names for a real vulnerability?
Yes. Royalty-free, no attribution required. If your name comes from the generator, please at least verify the bug exists first. That is the one step the industry keeps skipping.
Are named vulnerabilities actually bad?
No — and this is worth saying plainly. Heartbleed got patched fast because it had a name, a logo and a website that a CFO could understand. Naming is a genuinely effective communication tool. The failure mode is when the brand arrives before the analysis, when severity gets inflated for reach, and when three unrelated bugs get merged into one scary word because the word is what gets clicks.
Is my grandmother affected?
Yes. Her router is affected, her car is affected, and the loyalty card in her wallet is affected. She is handling it better than your incident channel.
Who runs the Shell Naming Authority?
It is one person, a domain renewal reminder, and this repository. The SNA has no members, no charter, and no standing. Like several real standards bodies, it has a logo.
How do I report a vulnerability in this website?
Open an issue. Name it first.
Press kit
Everything a journalist needs to cover a vulnerability that does not exist.
Brand colors
#39e58cShell Green#e66767Incident Red#c98500Advisory Amber#1a1a19War Room Black
Style guide
- One word, camel case in prose: Everything4Shell.
- Pronounced /ˈɛv.ri.θɪŋ.fɔː.ʃɛl/. Four syllables, as mandated.
- Never E4S on first reference. Always E4S by the third paragraph.
- Do not stretch the logo. The logo stretches you.
Boilerplate
The Shell Naming Authority is a parody standards body founded in 2026 to consolidate all vulnerability branding under a single suffix. It has no members, no funding, and no legitimacy. Everything4Shell is a satirical commentary on security marketing and is not a real vulnerability. The SNA is not affiliated with any vendor, foundation, government agency, or vulnerability database, and does not want to be.