PatchSiren cyber security CVE debrief
CVE-2026-56723 zammad CVE debrief
CVE-2026-56723 is a vulnerability in Zammad, a web-based open-source helpdesk/customer support system. Prior to version 7.0.2, customers who can view a ticket can bypass article-level authorization and download attachments belonging to internal articles directly via the attachment download endpoint. This issue is fixed in version 7.0.2. The vulnerability allows unauthorized access to internal articles, potentially leading to information disclosure. Defenders should assess exposure and apply the fix to prevent potential unauthorized access.
- Vendor
- zammad
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Defenders responsible for Zammad installations, particularly those with customer-facing support systems, should assess exposure and apply the fix to prevent potential unauthorized access to internal articles.
Why it matters
CVE-2026-56723 is a vulnerability in Zammad that allows customers to bypass article-level authorization and download internal article attachments. Defenders should prioritize verifying exposure and applying the fix.
- Customers with ticket viewing access may be able to download internal article attachments
- The vulnerability can be exploited to bypass article-level authorization
- Fixing the issue requires updating to version 7.0.2
Technical summary
The vulnerability in Zammad allows customers who can view a ticket to bypass article-level authorization and download attachments belonging to internal articles directly via the attachment download endpoint. This issue is fixed in version 7.0.2. The vulnerability can lead to unauthorized access to internal articles, potentially resulting in information disclosure. Defenders should prioritize verifying exposure and applying the fix, as customers with ticket viewing access may be able to download internal article attachments.
Defensive priority
Defenders should prioritize verifying exposure and applying the fix, as customers with ticket viewing access may be able to download internal article attachments.
Recommended defensive actions
- Verify if the system is running a version prior to 7.0.2 and apply the fix
- Review and update access controls for ticket and article viewing
- Monitor for potential unauthorized access to internal articles
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix in version 7.0.2. However, additional information on exploitation, victims, or business impact is not available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-56723 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-56723
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-56723 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-56723
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/zammad/zammad/commit/e661d00efb3d2c4ef4af3a36ce79d7c724323f97
-
Source reference
Unverified legacy reference
URL: https://github.com/zammad/zammad/releases/tag/7.0.2
-
Source reference
Unverified legacy reference
URL: https://github.com/zammad/zammad/security/advisories/GHSA-374g-4f73-g7m7
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.