Event JSON
{
"id": "b71cc74b863ceef6d1e2fbb899660781305fdad6faed4a11399291e6ae737381",
"pubkey": "147789618a35dc102206f5d9b7013c3ff7816066b3abf98d4c7fae852410df8d",
"created_at": 1793110269,
"kind": 1,
"tags": [
[
"proxy",
"https://shellsharks.social/@shellsharks/117513274637882092",
"web"
],
[
"proxy",
"https://shellsharks.social/users/shellsharks/statuses/117513274637882092",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://shellsharks.social/users/shellsharks/statuses/117513274637882092",
"pink.momostr"
],
[
"-"
]
],
"content": "CVE-2026-11497 having a bit of an identity crisis…\n\n- Imperva coined the initial term, “Node2Shell” (https://www.imperva.com/blog/node2shell-from-brotli-data-to-remote-code-execution/)\n- Aikido tried to turn it into “HTTP2Shell” (https://www.aikido.dev/blog/python-packages-vulnerable-node2shell-brotli-cve-2026-111497)\n- Not satisfied with either of those, someone came up with “Broccoli2Shell” 🥦 (https://broccoli2shell.com)\n- And now, super late to the game, humorless Tenable has decided to label it “Brotli2Shell” (https://www.tenable.com/blog/brotli2shell-frequently-asked-questions-for-google-brotli-decoder-cve-2026-111497)\n\nSame vuln, 4 different names (so far). Yeesh…",
"sig": "454e6a6be1cde6c563a49ce3cb6eabbeca598a5021244685be1f481161c177d35d7cbecc386ef68695a827bfd4962a78d09f474d2d4920834b0432678acbf64d"
}