CVE-2026-34072
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCr*nMaster (cronmaster) is a Cronjob management UI with human readable syntax, live logging and log history for cronjobs. Prior to version 2.2.0, an authentication bypass in middleware allows unauthenticated requests with an invalid session cookie to be treated as authenticated when the middleware’s session-validation fetch fails. This can result in unauthorized access to protected pages and unauthorized execution of privileged Next.js Server Actions. This issue has been patched in version 2.2.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCr*nMaster prior to version 2.2.0 contains an authentication bypass in its middleware where unauthenticated requests with invalid session cookies are incorrectly treated as authenticated when the middleware's session-validation fetch fails. This allows attackers to access protected pages and execute privileged Next.js Server Actions without valid credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cronmaster installation and versionLocate the Cronmaster installation directory and check the package.json, version file, or application metadata for the installed version number. Common locations include the project root, package-lock.json, or the application's 'about'/info endpoint.Affected if The installed version is lower than 2.2.0
-
Verify middleware component is in useExamine the application's middleware configuration files (such as middleware.ts, middleware.js, or equivalent) to determine if the Cronmaster session-validation middleware is imported and active.Affected if The session-validation middleware from Cronmaster is present and enabled in the application
-
Confirm session validation fetch is configuredReview the middleware configuration to check if the session-validation fetch functionality is implemented, particularly looking for fetch calls to validate session cookies.Affected if The middleware contains session-validation fetch logic that could fail
-
Test protected endpoint accessibilitySend an HTTP request to a protected page or privileged Server Action endpoint with an invalid or missing session cookie, observing whether the request succeeds despite invalid credentials.Affected if Requests with invalid session cookies are accepted and return protected content without authentication
A user is affected if Cronmaster version is below 2.2.0 and the vulnerable session-validation middleware is enabled in their environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.0
Upgrade to version 2.2.0 which contains the patch for this vulnerability.
2.2.0
- 1. Identify the current installed version of Cronmaster (cronmaster) in your environment
- 2. Upgrade Cronmaster to version 2.2.0 or later
- 3. Verify the upgrade was successful by checking the installed version
- 4. Test that the authentication middleware properly validates sessions after the upgrade
- 5. Confirm that invalid session cookies are now rejected rather than treated as authenticated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data