Loading story…
A critical vulnerability, tracked as CVE-2026-21440, has been identified in the multipart file handling component of the AdonisJS web framework. This flaw allows remote attackers to exploit a path traversal weakness, enabling arbitrary file writes to any location on the server filesystem. The vulnerability affects @adonisjs/bodyparser through version 10.1.1 and 11.x prerelease versions prior to 11.0.0-next.6, and has been assigned a CVSS 4.0 critical severity rating.
The issue has been addressed in patched releases: @adonisjs/bodyparser versions 10.1.2 and 11.0.0-next.6. Organizations using AdonisJS are strongly advised to update to the latest secure versions to mitigate the risk of remote code execution and potential server compromise. No specific affected product table has been published, but the vulnerability is confirmed to be remotely exploitable and poses a significant threat to unpatched deployments.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-21440 was publicly disclosed as a critical path traversal vulnerability with CVSS 9.2, allowing unauthenticated remote attackers to write arbitrary files on affected servers. Public advisories warned that the issue could lead to remote code execution depending on server configuration.
AdonisJS released fixes for CVE-2026-21440 in @adonisjs/bodyparser version 10.1.2 and 11.0.0-next.6. The vulnerability affects versions through 10.1.1 and prerelease 11.x versions before 11.0.0-next.6.
Security researcher Hunter Wodzenski (also referred to as Wodzen) discovered and reported a path traversal vulnerability in the @adonisjs/bodyparser package used by AdonisJS multipart file handling. The flaw stems from unsafe handling of client-supplied filenames in MultipartFile.move(), enabling arbitrary file writes.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourcethehackernews.com
Open sourcesecurityonline.info
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
OpenBMB ChatDev through version **2.2.0** is affected by **`CVE-2026-58166`**, a critical unauthenticated path traversal flaw in its file upload handler that lets remote attackers write or delete arbitrary files on the server. The vulnerability stems from the `POST` uploads session endpoint, where a malicious multipart filename containing traversal sequences or an absolute path is passed into `save_upload_file` without proper sanitization, allowing attacker-controlled filesystem paths to be used during upload and cleanup operations. The issue is rated **CVSS 3.1 9.1 (Critical)**, with a listed **CVSS 4.0 8.8 (High)**, and is considered remotely exploitable without authentication. The flaw was fixed in commit **`4fd4da6`**, and affected organizations should update to a patched release and enforce strict validation and sanitization of upload filenames and paths to prevent arbitrary file write or deletion.
Jul 1, 2026
Researchers disclosed multiple high-severity vulnerabilities in the open-source **Voyager** admin package for Laravel, warning that flaws in versions **1.8.0 and earlier** can be chained to achieve **remote code execution** and potentially full system compromise. The reported issues include **CVE-2024-55417**, an arbitrary file upload weakness caused by insufficient MIME-type validation, and **CVE-2024-55416**, a reflected **XSS** flaw in the `/admin/compass` component that can help attackers reach code execution in administrative contexts. The disclosures also describe a file path manipulation issue that can enable unauthorized file read and deletion, expanding the impact beyond code execution to broader application and server compromise. Public reporting said no security update was available at the time of notice, and defenders were urged to treat Voyager deployments as exposed, restrict or avoid use of the package until patches are released, and assess Laravel environments for signs of malicious uploads, admin-panel abuse, and tampering with application files.
Jul 24, 2026
A critical vulnerability in the Axios HTTP client library, tracked as **`CVE-2026-40175`**, allows attackers to turn polluted JavaScript object properties into malicious HTTP headers and abuse outbound requests for **SSRF**, **request smuggling**, and potential **remote code execution**. Researchers said the flaw stems from improper header handling in Axios’s HTTP adapter and unsafe config merging, which can let `Object.prototype` values containing CRLF characters be injected into requests. The issue can be chained with prototype pollution in other npm packages to target internal services, including the AWS EC2 metadata endpoint at `169.254.169.254`, potentially bypassing **IMDSv2** and exposing cloud credentials or broader infrastructure. A public proof-of-concept was released alongside disclosure, raising urgency for defenders even though active exploitation had not been confirmed at the time of reporting. The flaw affects Axios versions before **`1.13.2`**, while maintainers said **`1.15.0`** introduces strict header validation that blocks CRLF-based header injection; organizations were urged to upgrade and audit dependencies such as **`body-parser`**, **`qs`**, and **`minimist`** for prototype pollution paths. One report cited internet-wide estimates of more than **48,000** potentially exposed instances, underscoring the risk of unauthorized internal access and possible full cloud compromise.
Jun 29, 2026