Back Redpacketsecurity CVE Alert: CVE-2026-121451 – amir1376 – ab-download
AB Download Manager before 1.11.2 contains a cross-site request forgery vulnerability in its unauthenticated browser-integration API that allows remote attackers to write attacker-chosen files to arbitrary paths. A malicious web page can send a text/plain request to /start-headless-download with crafted folder and name values, placing payloads in startup folders for code execution on login.
**Risk verdict:** This is a high-impact, remotely triggerable weakness requiring a user to visit a malicious page; KEV, SSVC exploitation, PoC and EPSS data were not supplied, so active exploitation and urgency cannot be confirmed.
**Why this matters:** Successful abuse could compromise the user’s workstation, expose local data, or disrupt operations. Attackers may seek persistence or a foothold for credential theft and further access, particularly where the machine can reach sensitive internal services.
**Most likely attack path:** An attacker lures a user into opening a crafted web page while the desktop application is running and its local integration interface is reachable. No attacker account or elevated privilege is needed; user interaction is required, while the stated scope indicates impact is confined to the vulnerable host rather than automatically extending to other systems.
**Who is most exposed:** Users running desktop download-management software with browser integration enabled are the principal concern, especially on shared, privileged, or business-critical workstations.
Look for unexpected files created in startup-related or other unusual directories by the application.
Review application and endpoint telemetry for requests to its local integration service, especially downloads with anomalous names or destinations.
Check for newly added startup entries and processes launched from user-writable paths.
Investigate browser visits to suspicious sites preceding unusual file creation.
Mitigation and prioritisation
Upgrade to the vendor’s fixed release; prioritise deployment across affected endpoints.
Until updated, disable browser integration or stop the application where operationally feasible.
Restrict local access to the integration service and block untrusted web content from reaching local services.
Validate endpoint integrity and remove unauthorised files or persistence mechanisms; test changes before broad rollout.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
