dbcve.org
ZammadApplication

CVE-2026-34723

HIGH · 7.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 6.5.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, unauthenticated remote attackers were able to access the getting started endpoint to get access to sensitive internal entity data, even after the system setup was completed. This vulnerability is fixed in 7.0.1 and 6.5.4.

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 confidence

Zammad helpdesk system contains an authentication bypass vulnerability where the getting started endpoint remains accessible to unauthenticated users after system setup is complete. Attackers can exploit this to retrieve sensitive internal entity data without any credentials.

MitigationUpgrade Zammad to version 7.0.1 or 6.5.4 or later to remediate the improper access controls on the getting started endpoint.

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
ZammadApplication
Affected:< 6.5.4= 7.0.0

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zammad version
    Check the version via the web interface footer, or run command: zammad --version, or check the package manager (dpkg -l | grep zammad or rpm -q zammad)
    Affected if version is less than 6.5.4 or exactly 7.0.0
  2. Verify if system initial setup is complete
    Log in to the Zammad web interface as an admin. If you can access the admin panel and the system has users configured, setup is complete.
    Affected if system has completed initial setup (has users, admin account configured)
  3. Test unauthenticated access to getting started endpoint
    Open a browser incognito window and navigate to /getting_started (or /onboarding) endpoint of your Zammad installation without providing any login credentials
    Affected if the page loads and displays content instead of redirecting to a login page

You are affected if your Zammad version is below 6.5.4 or exactly 7.0.0 AND the getting started endpoint is accessible without authentication after initial system setup has been completed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.4 or later
Fixed in 6.5.4
Interim mitigation

Upgrade Zammad to version 7.0.1 or 6.5.4 or later to remediate the improper access controls on the getting started endpoint.

Recommended fix High confidence

Upgrade to Zammad 6.5.4 (LTS) or 7.0.1 (stable)

  1. 1. Identify current Zammad version by checking the application or /api/v1/health endpoint
  2. 2. Create a complete backup of the Zammad database and application files
  3. 3. Review the Zammad 6.5.4 or 7.0.1 release notes for any known issues or migration requirements
  4. 4. For self-hosted installations: stop the Zammad service before upgrading
  5. 5. Upgrade Zammad to version 6.5.4 (LTS) or 7.0.1 (stable) using the appropriate package manager or source installation method (e.g., apt-get update && apt-get install zammad, or using the official install scripts)
  6. 6. Restart the Zammad service after upgrade completes
  7. 7. Verify the upgrade was successful by checking the application health endpoint
  8. 8. Test that the getting started endpoint now properly requires authentication and returns appropriate access control responses

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zammad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34723 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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