CVE-2026-35514
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 · uneditedChartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In version 4.9.0, the endpoint POST /user/invited does not validate any invite token, authentication header, or session. Any unauthenticated attacker can call this endpoint directly to create a fully active account and receive a valid JWT — even when the instance has existing users and signupRestricted is enabled. This bypass is distinct from the normal registration endpoint (POST /user) which enforces signupRestricted and sets active: false pending verification. This issue has been patched in version 5.0.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 confidenceThe POST /user/invited endpoint in Chartbrew 4.9.0 lacks any authentication, invite token validation, or session checks, allowing unauthenticated attackers to create fully active user accounts with valid JWTs. This bypasses signupRestricted settings that normally restrict new registrations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 if Chartbrew is deployed in your environmentCheck your application inventory or running services for Chartbrew instances. Look for web applications serving Chartbrew frontend or API endpoints.Affected if Chartbrew is running in your environment
-
Determine the installed Chartbrew versionCheck the version number of your Chartbrew installation. This is typically visible in package.json (if self-hosted), the application UI footer, or by querying the API version endpoint if available. Compare your version against the affected range: 4.9.0Affected if Your Chartbrew version is 4.9.0 or falls within the affected range prior to 5.0.0
-
Verify the /user/invited endpoint is accessibleSend a POST request to your Chartbrew API at /user/invited endpoint without providing any authentication headers, invite tokens, or session cookies. Observe if the request is accepted and processed.Affected if The endpoint accepts the request without requiring authentication, invite token validation, or session verification
-
Check if signupRestricted setting is configuredReview your Chartbrew configuration or database settings for the signupRestricted option. This setting normally restricts new user registrations.Affected if signupRestricted is enabled but account creation via /user/invited still succeeds, indicating the bypass is active
You are affected if you run Chartbrew version 4.9.0 (or any version prior to 5.0.0) and the /user/invited endpoint accepts unauthenticated POST requests to create active user accounts.
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 · scopedUpgrade Chartbrew to version 5.0.0 which contains the patch for this authentication bypass vulnerability.
5.0.0
- Upgrade Chartbrew from version 4.9.0 to version 5.0.0 or later. This will apply the patch that adds proper authentication validation to the POST /user/invited endpoint, preventing unauthenticated account creation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35514 — 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-35514 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