CVE
NodePress auth bypass via hardcoded JWT signing key
Affects NodePress through 8.5.1 on default installs where NP_AUTH_JWT_SECRET is unset, so the hardcoded fallback signing key is used. No vendor rating or fixed version is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
NodePress, a product from surmon-china, has an authentication bypass that lets a remote attacker reach administrator functions without logging in. The attacker can forge login tokens using a hardcoded default signing key, then manage articles, comments, options, and files as an administrator.
Original description
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.
Who should check
Teams running surmon-china NodePress v8.5.1 and earlier, especially default installs without NP_AUTH_JWT_SECRET set
“Affected: surmon-china/nodepress v8.5.1 and earlier”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Workaround: No fix is listed, so the available step is to set NP_AUTH_JWT_SECRET so the built-in fallback secret is not used. The facts do not describe any other workaround.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129952 (NodePress through 8.5.1 Authentication Bypass via Default JWT Signing Secret), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129952 (entry last updated 2026-11-16):
Affected:
- surmon-china NodePress: through 8.5.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Default install that boots without NP_AUTH_JWT_SECRET set, so the built-in JWT secret is used (source: https://github.com/surmon-china/nodepress/issues/143)
- Attacker forges HS256 JWTs signed with the hardcoded 'nodepress-secret' fallback key (source: https://www.vulncheck.com/advisories/nodepress-through-8.5.1-authentication-bypass-via-default-jwt-signing-secret)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129952 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129952 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surmon-china/nodepress/issues/143
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/app.config.ts#L62-L72
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/core/auth/auth.module.ts#L17-L29
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/main.ts#L44-L60
- https://www.vulncheck.com/advisories/nodepress-through-8.5.1-authentication-bypass-via-default-jwt-signing-secret
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129952
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129952"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- surmon-china NodePress
through 8.5.1
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Report
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129952
Is CVE-2026-129952 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When NP_AUTH_JWT_SECRET is not set, NodePress signs login tokens with a hardcoded 'nodepress-secret' fallback key. A party who knows this key can forge HS256 JWTs and gain unauthenticated administrator access to article, comment, options, and file management APIs.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-129952?
NodePress: through 8.5.1.Source: cve.now feed data
Am I affected, and how do I check?
NodePress through version 8.5.1 is affected, on default installs where NP_AUTH_JWT_SECRET and NP_ADMIN_DEFAULT_PASSWORD are not set. To check a setup, look at the environment variables the server runs with and see whether NP_AUTH_JWT_SECRET is set.Source: github.com, vulncheck.com
How do I fix CVE-2026-129952?
The checked facts name no fixed version and no vendor patch identifier. The condition the advisory describes is NP_AUTH_JWT_SECRET being unset, so setting it removes the fallback key.Source: github.com, vulncheck.com
What if there's no patch?
No fix is listed, so the available step is to set NP_AUTH_JWT_SECRET so the built-in fallback secret is not used. The facts do not describe any other workaround.Source: github.com, vulncheck.com