{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63205 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63205 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63205 is a medium-severity missing authorization vulnerability in zammad, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63205 and fix it if it is affected.\n\nWhat it is: CVE-2026-63205 is a medium-severity missing authorization vulnerability in zammad, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63205 in the wild and no public exploit code.\n\nAffected product: zammad. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63205/ (Markdown: https://insights.sbomify.com/CVE-2026-63205/index.md)","id":"CVE-2026-63205","markdown":"https://insights.sbomify.com/CVE-2026-63205/index.md","name":"CVE-2026-63205","record":{"aliases":["GHSA-pp8r-x7pp-5qj5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zammad helpdesk system","requires_auth":"high_privilege","summary":"Channel admins can read unauthorized ticket attachments by referencing them in email signature HTML, bypassing access controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when creating or updating an email signature, Zammad processes inline images referenced in the signature body. If a signature body contains an HTML img tag pointing to any existing attachment, the system copies that attachment into a new signature-owned record, without checking whether the user has permission to access the original attachment. The newly created copy is then downloadable by the same channel-admin user, because attachment access is determined by the copy's owner (the signature), not the original object (e.g., a ticket or knowledge-base article). This allows a user with any of the admin.channel_email, admin.channel_google, admin.channel_microsoft365, or admin.channel_microsoft_graph permissions to read attachments they would otherwise be denied access to, such as ticket attachments belonging to groups they are not a member of. This issue is fixed in version 7.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zammad: Channel admins can read unauthorized attachments via signature rich-text body","id":"CVE-2026-63205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Zammad: Remote image tracking bypass via shortened URL scheme","id":"CVE-2026-63206"},"packages":[],"prev":{"headline":"Zammad: Authenticated agents can read AI summary error messages from inaccessible tickets","id":"CVE-2026-63204"},"products":["zammad"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["zammad"]},"summary":"Channel admins can read unauthorized ticket attachments by referencing them in email signature HTML, bypassing access controls.","url":"https://insights.sbomify.com/CVE-2026-63205/"}