Turkey2Nap logo: a sleeping turkey with a shell prompt >_ z Z

CVE-1621-1126 · ALSO TRACKED AS TURKEY4NAP · PUBLISHED 2026-11-21 · STATUS: DISPUTED BY VENDOR

Turkey2Nap

Unauthenticated Remote Nap Execution (RNE) via a stomach buffer overflow in the Thanksgiving Dinner runtime.

9.2
CVSS 4.0 · CNA
10.0
Researcher's blog
9.8
CVSS 3.1
11.0
Grandma
0.00042
EPSS · 4th percentile

TL;DR

Every version of Thanksgiving Dinner since 1621 lets an unauthenticated attacker (a relative) send a crafted payload (a second helping) to /couch and achieve Remote Nap Execution. No user interaction is required. The user will, in fact, stop interacting.

There is no patch. Mitigations exist. Exploitation in the wild has been observed. Mass exploitation is expected Thursday, within 15 minutes of kickoff.

01Am I affected?

Answer six questions. Our scanner runs entirely in your browser. No data leaves the table.

02Technical details

The Thanksgiving Dinner runtime copies incoming food into a fixed-size stomach buffer without checking the Serving-Size header. The buffer holds one plate. It was sized in 1621 and has never been reviewed. A second helping overflows it, overwrites the return address for "go help with the dishes," and control passes to the Recliner subsystem.

The vulnerable code path is reachable before the host's own application logic ("I should help with the dishes") gets a chance to run.

An SBOM was requested. The vendor provided Grandma's recipe card, last updated 1974. It lists "butter (some)."

Example exploit request:

POST /couch HTTP/1.1
Host: living-room.local
Content-Type: application/x-gravy
Serving-Size: 2
X-Forwarded-For: grandma
Transfer-Encoding: stuffed

{"helping": 2, "gravy": "yes", "rolls": 4, "pie": ["pumpkin", "pecan", "apple"]}

Resulting crash, captured from a host in the wild:

Exception in thread "afternoon" dinner.runtime.StomachBufferOverflowError: buffer full (capacity=1 plate, requested=2)
    at dinner.runtime.Digestion.copyToStomach(Digestion.java:1621)
    at dinner.runtime.Plate.secondHelping(Plate.java:2)
    at dinner.ui.Recliner.recline(Recliner.java:180)
    at football.Broadcast.thirdQuarter(Broadcast.java:3)
    at human.Consciousness.restingMyEyes(Consciousness.java:Zzz)
Caused by: gravy.BoatException: boat empty
    ... 4 more

Vendor statement: the Thanksgiving Dinner maintainers dispute this CVE, saying turkey has about as much tryptophan as chicken and the root cause is "carbohydrate load and the third quarter." We have rated the vendor's statement CVSS 0.0.

03Affected versions

ComponentAffectedFixed in
Thanksgiving Dinner1621 – 2026No fix available. Next scheduled patch: Pie Tuesday, Dec 8. The vendor does not ship out-of-band.
Stuffing≤ 2.xEnd of life. No patch planned.
GravyallWon't fix (working as intended)
Leftovers2026.11.27Inherits the vulnerability
Friendsgivingall forksDownstream. Check with your friends.
Plant-based roast—Not affected*

* Different exploit chain, same nap.

04Timeline

  1. Vulnerable code introduced in the initial commit (Plymouth).
  2. A core maintainer (Grandma) finds the issue during an internal audit. The ticket is closed as WONTFIX: "it's tradition."
  3. Drumstick-5.6 rediscovers the flaw as part of the Patch the Plate initiative.
  4. Exploitation in the wild observed at an early Friendsgiving, nine days before the planned disclosure.
  5. Vendor notified. Coordinated disclosure scheduled for Thursday at kickoff.
  6. Aunt Linda posts the proof-of-concept video to the family group chat, followed by "is this the right chat?" Embargo broken.
  7. Advisory published early. turkey2nap.org registered. The logo is finished before any patch exists. Added to the Known Exploited Vegetation catalog, remediation due before dessert.
  8. Mass exploitation expected within 15 minutes of kickoff.

05Mitigations & patches

If you cannot patch, follow the guidance from the National Nap Security Centre: take yourself offline. Lie down. Close the blinds. Put your phone face down.

06Indicators of compromise

TypeValue
SHA-256 ("I'm just resting my eyes")5fd45b00f48461ec5fe1dd8454990d06f2512dc1251aa5421d5ac8cf0f580a1b
SHA-256 ("a second helping")578c0c939017891df5c6ebe415a64d29cfe7a416944e6690ffe4ebf447be08f6
Endpoint/couch, /recliner, /floor-in-front-of-the-fireplace

07FAQ

Why is it called Turkey2Nap?
Because CVE-1621-1126 doesn't fit on a hoodie.
Is this the same as Turkey4Nap?
Yes. A second team named it 40 minutes later. Your scanner will report both, as separate criticals.
Is my uncle vulnerable?
Your uncle is the proof of concept.
What's the real CVSS score?
Yes.
Why is the EPSS score so high on Thursday?
EPSS estimates the chance of exploitation in the next 30 days. This one needs about four hours.
Isn't the tryptophan thing a myth?
Yes. The vendor's statement says so too. The exploit still works.
Was this found by AI?
It was found by Drumstick-5.6, a frontier AI model. It has also been independently rediscovered every year by roughly 280 million people.
My VP just emailed "are we affected??"
Reply "investigating." It holds until Monday.
What's our SLA?
Critical: 7 days. Thanksgiving is in 5. Leftovers are in 6. Ask for an exception.

08Credits

A note from the author

This has been a tough month for people in vulnerability management. I hope this makes you smile a little, as much as it made me smile when it came up in a meeting.

— Jerry