Loading story…
A high-severity vulnerability tracked as CVE-2026-73654 affects Trigger.dev versions 3.3.8 through 4.5.5, allowing prototype pollution through the PUT /api/v1/runs/:runId/metadata endpoint. The flaw lets an attacker with a normal environment API key supply malicious metadata keys such as __proto__, constructor, or prototype, which are passed into JSONHeroPath().set() and can modify Object.prototype in the shared web application process. The resulting corruption can cascade across tenants, causing Prisma query failures, Prometheus label corruption, broken worker authentication, and process-wide denial of service.
The issue is classified as CWE-1321 and carries a CVSS v3.1 score vector of **AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H``**, reflecting low-complexity network exploitation with high availability impact. Trigger.dev fixed the vulnerability in **version 4.5.6** by adding input validation, including isSafeMetadataKeychecks and filtering of dangerous path segments before metadata reaches the path resolver. For self-hosted deployments that cannot patch immediately, recommended interim defenses include WAF rules that inspect HTTPPUT` requests to the metadata endpoint and block JSON payloads containing unsafe prototype-related keys.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
The CVE entry states the issue was newly received by security-advisories@github.com on August 13, 2026, and references a GitHub Security Advisory under GHSA-p28v-f755-9qrg. The advisory covers a Trigger.dev prototype pollution vulnerability that can lead to cross-tenant process-wide denial of service.
Trigger.dev addressed a prototype pollution flaw in the PUT /api/v1/runs/:runId/metadata endpoint in version 4.5.6. The fix adds validation and filtering for unsafe metadata key segments such as __proto__, constructor, and prototype before they reach the path resolver.
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.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
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.
Two critical prototype pollution vulnerabilities, **CVE-2026-48713** and **CVE-2026-48714**, were disclosed in the widely used Node.js internationalization components **`i18next-fs-backend`** and **`i18next-http-middleware`**. The bugs allow attacker-controlled missing translation keys to traverse unsafe path segments such as `__proto__`, `constructor`, and `prototype`, potentially writing arbitrary properties into **`Object.prototype`**. In affected deployments, successful exploitation can trigger application crashes, corrupt translation behavior, poison configuration, and bypass property-based security checks. The primary backend flaw affects **`i18next-fs-backend`** versions before **`2.6.6`**, while the middleware flaw affects **`i18next-http-middleware`** versions before **`3.9.7`** and can help remote input reach the vulnerable backend path by failing to block dotted payloads such as `__proto__.polluted`. Exploitation depends on applications exposing **`missingKeyHandler`** or similar **`saveMissing`** functionality to untrusted users with key splitting enabled. Maintainers patched the issues by blocking unsafe path traversal, and defenders are advised to upgrade immediately, restrict missing-key routes to trusted users, disable missing-key persistence for untrusted input, or set **`keySeparator`** to **`false`** where appropriate.
Jun 29, 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
A high-severity flaw in the Axios HTTP client, tracked as **`CVE-2026-67320`**, can cause Node.js applications to send requests through an attacker-controlled proxy when the Node HTTP adapter is used and **prototype pollution** has already compromised `Object.prototype`. The issue stems from request configuration hardening being undone by common interceptor patterns such as object spreading or `Object.assign`, allowing a polluted `proxy` property to be inherited through the prototype chain. Affected versions are **`0.31.1` through `0.32.9`** and **`1.15.2` through `1.17.9`**, with fixes released in **`0.33.0`** and **`1.18.0`**. Successful exploitation can expose plaintext HTTP traffic, including **Authorization headers**, Basic auth credentials from `config.auth`, request methods, full URLs, `Host` headers, and request bodies, while also enabling attackers to return manipulated responses to the application. Italian authorities reported that a **proof-of-concept exploit is now publicly available**, increasing the urgency for organizations using vulnerable Axios versions in Node.js environments to patch promptly. The advisory notes there is no demonstrated browser impact and no HTTPS header or body disclosure under normal TLS validation.
Aug 3, 2026