CVE-2026-129952 is a critical authentication bypass in NodePress through version 8.5.1. On deployments that never set their own JWT secret, unauthenticated remote attackers can forge administrator JWTs using the hardcoded nodepress-secret fallback key.
What Is It
NodePress (surmon-china/nodepress) uses a hardcoded JWT signing secret, nodepress-secret, as a fallback when no secret is configured. According to the NVD description, attackers can sign HS256 bearer tokens with this key and set the default issuer, audience, and role admin. A deployment that never set its own secret accepts these forged tokens, which gives the attacker administrator access without any credentials.
VulnCheck reported the flaw and classifies it as CWE-1394 (use of a default cryptographic key). The NVD references link to the relevant lines in the v8.5.1 source: app.config.ts, auth/auth.module.ts, and main.ts.
Why It Matters
- CVSS 3.1: 9.8 CRITICAL (
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) - CVSS 4.0: 9.3 CRITICAL
The attack works over the network. It needs no privileges and no user interaction, and its complexity is low. Against an affected deployment that relies on the fallback key, a forged token reaches the administrator-only APIs for managing articles, comments, options, and files. The impact on confidentiality, integrity, and availability is rated high.
This CVE has no CISA KEV entry, so KEV does not confirm active exploitation at this time. NVD lists the record's status as "Deferred."
What's Vulnerable
- Vendor: surmon-china
- Product: NodePress
- Affected versions: 0 through 8.5.1 inclusive (semver)
- Package:
pkg:github/surmon-china/nodepress
Exploitation requires that the deployment never set its own JWT secret, so it falls back to the default nodepress-secret key. The record lists no CPEs.
Patch Status
The supplied NVD and VulnCheck data does not name a fixed version, and there is no KEV entry, so no CISA required action or due date applies. A GitHub issue (#143) on the project repository is among the references. Operators running NodePress 8.5.1 or earlier should check the project and the VulnCheck advisory for remediation guidance. They should also make sure their deployment sets its own JWT secret and does not rely on the default nodepress-secret signing key.