DEV Community

threataft
threataft

Posted on Originally published at threataft.com

CVE-2026-129955 & 129952: NodePress Ships With a Default Password AND a Default JWT Key

Two CVSS 9.8s landed in NodePress 8.5.1 this week — and they’re completely independent. That’s the part worth paying attention to.

CVE-2026-129955 is a default credentials flaw (CWE-1392). The admin account falls back to the password root when NP_ADMIN_DEFAULT_PASSWORD is unset. Base64-encode it, POST it to /admin/login, get an admin token.

CVE-2026-129952 is a default cryptographic key flaw (CWE-1394). The JWT signing secret falls back to nodepress-secret when NP_AUTH_JWT_SECRET is unset. Sign your own HS256 token with the default issuer, audience, and role: admin. Done — no login endpoint touched, no rate limit applies, nothing in your auth logs.

Why both matter together: fixing CVE-2026-129955 (setting the password env var) closes the login path and leaves the token path open. Operators who patch one and check the box have half a fix.

Two companion CVEs in the same disclosure:

CVE-2026-129953 — rate-limit bypass via spoofed X-Forwarded-For (trustProxy enabled)
CVE-2026-129954 — stored HTML injection in admin notification emails

The fix: NodePress 8.5.2 removes both fallbacks. Set NP_AUTH_JWT_SECRET to 32+ random bytes and treat a missing value as a boot failure. Rotate the secret after upgrading — tokens signed with the old default remain valid until the secret changes.

Full writeup with CVSS vectors, attack paths, log hunting guide, and mitigation checklist:
👉 https://threataft.com/articles/nodepress-cve-2026-129955-129952-auth-bypass-pair

Top comments (0)