dbcve.org
ZammadApplication

CVE-2026-34248

MEDIUM · 5.7 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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, customers in shared organizations (means they can see each other's tickets) could see fields which are not intended for customers - including fields not intended for them at all (e.g. priority, custom ticket attributes for internal purposes). This was the case when a customer opened a ticket from another user of the same shared organization. They are not able to modify these field. This vulnerability is fixed in 7.0.1.

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

In Zammad versions prior to 7.0.1, customers within shared organizations (where users can see each other's tickets) could view internal-only ticket fields such as priority and custom ticket attributes not intended for customer visibility. This information disclosure occurred when accessing tickets from other users in the same shared organization.

MitigationUpgrade Zammad to version 7.0.1 or later to remediate this information disclosure vulnerability.

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:= 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Check installed Zammad version
    Run the command: zammad run rails r "puts Zammad::Version.get". Alternatively, check the About page in the web UI or inspect the Gemfile.lock for the zammad gem version.
    Affected if The installed version is exactly 7.0.0
  2. Verify shared organizations feature is in use
    In the Zammad admin UI, navigate to Organizations and check if any organizations have the 'Shared' option enabled. Alternatively, query the database: SELECT id, name, shared FROM organizations WHERE shared = true;
    Affected if There exists at least one organization with shared access enabled
  3. Confirm customer-level users exist in shared organizations
    In the admin UI, check users assigned to shared organizations and verify their roles include 'Customer' or are not 'Admin'. Alternatively, query: SELECT u.id, u.login, o.name as org_name, o.shared FROM users u JOIN organizations o ON u.organization_id = o.id WHERE o.shared = true AND u.role_id NOT IN (SELECT id FROM roles WHERE name = 'Admin');
    Affected if There are users with Customer role assigned to shared organizations
  4. Inspect ticket field visibility settings
    In the admin UI, go to Object Manager and examine custom ticket field configurations. Check fields for the 'shown::Customer' or 'visible_for_customer' attribute values. Look for internal-only fields like priority, custom attributes that should be hidden from customers.
    Affected if Internal-only ticket fields (priority, custom internal attributes) are configured and shared organizations with customer users exist in version 7.0.0

A user is affected if Zammad version is exactly 7.0.0 AND they have shared organizations configured with customer-level users who can view internal ticket fields that should be hidden.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zammad to version 7.0.1 or later to remediate this information disclosure vulnerability.

Recommended fix High confidence

7.0.1

  1. 1. Create a complete backup of the current Zammad 7.0.0 installation including database and all configuration files
  2. 2. Stop the Zammad service before performing the upgrade
  3. 3. Upgrade Zammad to version 7.0.1 by following the official Zammad upgrade documentation for your deployment method
  4. 4. After upgrade, restart the Zammad service
  5. 5. Verify the upgrade was successful by logging in and confirming the application functions normally
  6. 6. Test the fix by logging in as a customer in a shared organization and confirming they can no longer see internal-only fields (priority, custom ticket attributes) when viewing another user's ticket in the same organization

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34248 — 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-34248 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