CVE-2026-34723
Unauthenticated data exposure via Zammad get-started endpoint.
Is CVE-2026-34723 being exploited?
Not confirmed. CVE-2026-34723 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-34723?
CVE-2026-34723 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34723?
Yes. A fix has been recorded for CVE-2026-34723. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34723 affect?
CVE-2026-34723 affects Zammad <7.0.1, Zammad <6.5.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34723?
Patch to 7.0.1 or 6.5.4+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated access to sensitive internal data via the /getting-started endpoint; data exposure after setup.
Immediate action required
- affected< 6.5.4
- affected>= 7.0.0-alpha and < 7.0.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.