On November 16 and 17, 2026, VulnCheck (acting as CNA) filed five critical CVEs in NVD against open source projects you run yourself: the Cloud Commander web file manager, the NodePress blog backend, TridotsTech's go1cms CMS and the OpenFunction serverless platform for Kubernetes. Four can be exploited with no account at all. The fifth turns a plain permission to create Kubernetes resources into root on the node.
| CVE | Product | Versions | Flaw | CVSS 3.1 (VulnCheck) | Authentication | NVD status |
|---|---|---|---|---|---|---|
| CVE-2026-130072 | Cloud Commander | before 19.21.4 | Missing authentication + path traversal (CWE-306) | 9.1 | None | Received |
| CVE-2026-129955 | NodePress | through 8.5.1 | Default admin password (CWE-1392) | 9.8 | None | Deferred |
| CVE-2026-129952 | NodePress | through 8.5.1 | Default JWT signing key (CWE-1394) | 9.8 | None | Deferred |
| CVE-2026-130071 | go1cms | master through commit 7f68d05, version-3 before ead8da3 | Missing authentication (CWE-306) | 9.8 | None | Received |
| CVE-2026-130587 | OpenFunction | through 1.2.0 | Missing authorization (CWE-862) | 9.9 | Permission to create Function / Serving | Received |
VulnCheck also publishes CVSS 4.0 scores: 9.4 for OpenFunction, 9.3 for NodePress and go1cms, and 8.8 for Cloud Commander (which drops it to High). No CPE configuration, no NIST analysis, and no CISA KEV listing for any of them at the time of writing.
NodePress: two keys left in the door
NodePress is a Node.js blog backend (the surmon-china/nodepress project). Through 8.5.1, two hardcoded defaults are enough to become an administrator:
- CVE-2026-129955: if
NP_ADMIN_DEFAULT_PASSWORDisn't set, the admin password isroot. Sending base64-encodedroottoPOST /admin/loginreturns an admin token. - CVE-2026-129952: the JWT signing key falls back to
nodepress-secretwhen it isn't configured. An attacker can sign their own HS256 token with the default issuer and audience and theadminrole, then call admin-only APIs for articles, comments, options and files.
Both are as much about configuration as code: an instance deployed with its own password and JWT secret doesn't go down these paths. But nothing forces you to set them, and the 9.8 rating describes the default case. NVD names no fixed version; issue 143 on the repository is the one to watch.
Cloud Commander: renaming any file without logging in
Cloud Commander (cloudcmd) is a Node.js web file manager. Before 19.21.4, the PUT /rename route is handled before the authentication middleware. An unauthenticated attacker can pass absolute or ../ paths in the from and to arrays and move any file the Node.js process can reach, outside the configured root.
The description focuses on data loss and denial of service, which is why the vector has no confidentiality impact. Moving arbitrary files could go further depending on what the process can write. That's speculation on our part; the CVE doesn't describe it. Version 19.21.4 fixes the issue (fix commit and release are referenced).
go1cms: editing any document, user accounts included
go1cms is an open source CMS from TridotsTech. Its update_doc method is guest-whitelisted and saves the supplied fields with ignore_permissions=True. An unauthenticated attacker picks a doctype, a name and arbitrary fields, which means they can edit User records to escalate privileges, take over accounts or tamper with business data.
There's no version number for the fix. Affected code is the master branch through commit 7f68d05 and the version-3 branch before commit ead8da3, which carries the fix.
OpenFunction: from creating a function to owning the Kubernetes node
OpenFunction is a FaaS platform for Kubernetes. Through 1.2.0, Function and Serving resources accept an unrestricted PodSpec template. A tenant who can only create those resources in their namespace can set privileged, hostNetwork, hostPID or a hostPath that mounts the node's root filesystem, and take over the node.
This is a multi-tenancy failure: the controller creates the pods with its own permissions and skips the guardrails that would apply if the tenant created the pod directly. That explains the S:C in the vector, since the impact escapes the namespace. NVD names no fixed version; issue 532 on the OpenFunction/OpenFunction repository is referenced.
Affected versions
| Product | Affected | Fix per NVD |
|---|---|---|
| Cloud Commander | before 19.21.4 | 19.21.4 |
| NodePress | through 8.5.1 | not stated |
| go1cms | master through 7f68d05, version-3 before ead8da3 | commit ead8da3 (version-3 branch) |
| OpenFunction | through 1.2.0 | not stated |
These bounds come from VulnCheck's descriptions, not from NIST analysis. For NodePress and OpenFunction, a version past the bound isn't automatically fixed: check the project repository before concluding.
Detection
- NodePress: successful
POST /admin/logincalls from unknown addresses. Above all, confirm thatNP_ADMIN_DEFAULT_PASSWORDand the JWT secret are actually set in the environment. - Cloud Commander:
PUT /renamerequests with no session, paths containing../or starting with/, files that went missing or moved. - go1cms:
update_doccalls with no session, recent changes toUserrecords (roles, emails, passwords). - OpenFunction:
FunctionorServingresources whose pod template containsprivileged: true,hostNetwork,hostPIDorhostPath.
Mitigation
1. Update what can be updated
Cloud Commander to 19.21.4; go1cms to a version-3 branch build that includes commit ead8da3.
2. NodePress: set the secrets
Set a strong admin password and JWT secret, then restart. Changing the secret invalidates any token forged with the default value.
3. OpenFunction: enforce Pod Security Standards
Apply the restricted profile (Pod Security Admission) or a Kyverno / Gatekeeper policy to tenant namespaces so privileged pods are rejected no matter who creates them. Also limit who can create Function and Serving resources.
4. Don't expose these tools
A web file manager or a CMS back office has no place on the public internet: put it behind a VPN, an IP allowlist or reverse-proxy authentication.
5. If the instance was exposed
For NodePress and go1cms, assume accounts and content may have been altered and review them. For OpenFunction, rebuild any node whose filesystem a tenant could have mounted.
This batch follows right on from Dokploy, sysPass, NginxPulse and Vvveb, published two days earlier: tools set up quickly, rarely updated, and often more exposed than anyone thinks.
Why continuous monitoring matters for self-hosted tools
These projects often get installed outside the official inventory: a file manager for a quick fix, a project blog, a serverless platform someone was testing. None has an NVD CPE configuration yet, so a standard product search won't surface them.
With cveo.tech, add those tools to your inventory with their version and get an alert as soon as a CVE affects them, even before NIST analysis.