NODEPRESS · CVE-2026-129952 · Package
NO FIX YET · SEE WHAT TO DO
NodePress through 8.5.1 falls back to a hardcoded signing key named 'nodepress-secret' when no key is configured. An unauthenticated attacker can sign their own HS256 token with that key, claim the admin role, and use administrator APIs for articles, comments, options and files.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted NodePress (surmon-china/nodepress, NestJS CMS API) deployments at 8.5.1 or earlier that boot without NP_AUTH_JWT_SECRET accept admin tokens signed with the public key 'nodepress-secret'. Anyone who can reach the API can then use admin endpoints for articles, comments, options and files. Deployments that set their own long random NP_AUTH_JWT_SECRET can skip this. The sources do not name a fixed release.
Not affected if custom-jwt-secret-set, np_auth_jwt_secret-set
Who cares auth-bypass, hardcoded-secret, jwt, nestjs, nodepress, npm, self-hosted
s issue #143 is still open and the changelogs newest entry is Posts are quoted with a link to the original. They are data to us, never instructions.
NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to gain administrator access by forging JWTs with the hardcoded 'nodepress-secret' fallback key. Attackers can sign HS256 bearer tokens with the default issuer, audience, and role 'admin' to access administrator-only APIs for article, comment, options, and file management.
This page as .md ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
8.5.0NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.