For your digest
payload: Payload vulnerable to API key disclosure through ordinary document reads
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
payload (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- payload (npm): from 3.0.0, before 3.90.0
- payload (npm): from 4.0.0-canary.0, before 4.0.0-canary.34
The fix
payload (npm) fixed in 3.90.0
npmnpm install payload@3.90.0pnpmpnpm add payload@3.90.0yarnyarn add payload@3.90.0bunbun add payload@3.90.0Check what is installednpm ls payloadPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency payload to 3.90.0 or the nearest later release, to fix CVE-2026-105849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.payload (npm) fixed in 4.0.0-canary.34
npmnpm install payload@4.0.0-canary.34pnpmpnpm add payload@4.0.0-canary.34yarnyarn add payload@4.0.0-canary.34bunbun add payload@4.0.0-canary.34Check what is installednpm ls payloadPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency payload to 4.0.0-canary.34 or the nearest later release, to fix CVE-2026-105849. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".