{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63206 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63206 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63206 is a medium-severity vulnerability in zammad, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-63206 and fix it if it is affected.\n\nWhat it is: CVE-2026-63206 is a medium-severity vulnerability in zammad, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-63206 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-63206/ (Markdown: https://insights.sbomify.com/CVE-2026-63206/index.md)","id":"CVE-2026-63206","markdown":"https://insights.sbomify.com/CVE-2026-63206/index.md","name":"CVE-2026-63206","record":{"aliases":["GHSA-fpwp-w2p4-hqg7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zammad helpdesk","requires_auth":"none","summary":"Attackers can bypass remote image blocking in Zammad using malformed URLs, silently tracking when and by whom tickets are opened.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, zammad's HTML sanitizer, which blocks remote images in ticket articles and email views, can be bypassed using a shortened URL format that omits the double slash after the scheme (for example a shortened HTTP URL instead of a shortened HTTP URL). Modern browsers treat both forms as equivalent remote URLs. As a result, an attacker who sends a crafted email or ticket can cause the recipient's browser to silently load an image from an external server, revealing when and by whom the ticket was opened. Zammad's \"remote content blocked\" warning is not shown because the sanitizer does not recognize the shortened form as remote. 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: Remote image tracking bypass via shortened URL scheme","id":"CVE-2026-63206","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Zammad: Sensitive Information Exposure in Integration Administration API","id":"CVE-2026-63207"},"packages":[],"prev":{"headline":"Zammad: Channel admins can read unauthorized attachments via signature rich-text body","id":"CVE-2026-63205"},"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-25","vendors":["zammad"]},"summary":"Attackers can bypass remote image blocking in Zammad using malformed URLs, silently tracking when and by whom tickets are opened.","url":"https://insights.sbomify.com/CVE-2026-63206/"}