{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56725 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56725 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56725 is a high-severity denial of service vulnerability in zammad, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56725 and fix it if it is affected.\n\nWhat it is: CVE-2026-56725 is a high-severity denial of service vulnerability in zammad, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56725 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-56725/ (Markdown: https://insights.sbomify.com/CVE-2026-56725/index.md)","id":"CVE-2026-56725","markdown":"https://insights.sbomify.com/CVE-2026-56725/index.md","name":"CVE-2026-56725","record":{"aliases":["GHSA-45cx-9mrq-mmcj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Zammad helpdesk","requires_auth":"none","summary":"Unauthenticated attackers can cause denial of service in Zammad by sending requests to an unprotected import endpoint that blocks server workers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary An unauthenticated request to POST /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly two minutes. The import_check and import_status actions are missing the setup_done_response guard that other actions in the same controller carry, so they execute on fully set-up production instances. The action enters a retry loop against a blank OTRS endpoint, sleeping for 30 s + 45 s between attempts. Impact An unauthenticated remote attacker denies service to a production Zammad instance. Each request costs almost nothing and forces ~115 seconds of server-side blocking. A few requests per second saturate the Puma worker pool. The condition persists as long as the traffic continues. No account, valid import configuration, or target knowledge beyond the hostname is needed. CSRF token is trivially obtained from any prior GET response. This issue is fixed in version 7.0.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: Denial of Service via OTRS Import Controller","id":"CVE-2026-56725","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Zammad: Missing authorization check in GitHub + GitLab integration allows cross-ticket data leak","id":"CVE-2026-56726"},"packages":[],"prev":{"headline":"Zammad: Incorrect implementation of permission checks in the knowledge base module","id":"CVE-2026-56724"},"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["zammad"]},"summary":"Unauthenticated attackers can cause denial of service in Zammad by sending requests to an unprotected import endpoint that blocks server workers.","url":"https://insights.sbomify.com/CVE-2026-56725/"}