For your digest
semantic-release: Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
semantic-release (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- semantic-release (npm): from 17.0.4, before 19.0.3
The fix
semantic-release (npm) fixed in 19.0.3
npmnpm install semantic-release@19.0.3pnpmpnpm add semantic-release@19.0.3yarnyarn add semantic-release@19.0.3bunbun add semantic-release@19.0.3Check what is installednpm ls semantic-releasePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency semantic-release to 19.0.3 or the nearest later release, to fix CVE-2022-31051. 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".