Finding and attribution
Zammad 6.5.2 interpolates an unvalidated block-level operator into SQL in selector-based API search, allowing a low-privilege customer to extract sensitive database records.
Product: Zammad. AI system: GitHub Security Lab Taskflow Agent. Team / organization: GitHub Security Lab.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): GHSL explicitly credits its Taskflow Agent and manual verification by Peter Stöckli and Man Yue Mo. Reported 2026-02-17; Zammad released the patch in v7.0.0 on 2026-03-04. No CVE was assigned in the cited evidence.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The advisory documents the finding and its disclosure/remediation state. It does not claim exploitation in the wild.
Remediation status: fix documented. Fixed in Zammad 7.0.0; vendor advisory ZAA-2026-06 also lists 6.5.3 as fixed.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 6 Mar 2026. AI attribution dated 6 Mar 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: data disclosure.
Prerequisites / affected scope: A low-privilege customer can extract arbitrary Zammad database data, including credentials, tickets and personal data..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Fixed in Zammad 7.0.0; vendor advisory ZAA-2026-06 also lists 6.5.3 as fixed.