fix(security): fix security issue in axios via minor version upgrade from 1.15.0 to 1.19.0

[aikido-autofix]

Upgrade axios to fix critical MITM, prototype pollution, credential leakage, and header injection vulnerabilities affecting HTTP requests and authentication.

⚠️ Breaking changes analysis not available for: axios

✅ 14 CVEs resolved by this upgrade

This PR will resolve the following CVEs:

Issue	Severity	Description
CVE-2026-44494	HIGH	[axios] Prototype pollution vulnerability allows escalation to Man-in-the-Middle attacks by injecting a malicious proxy into the prototype chain, enabling interception and modification of all HTTP traffic including authentication credentials. An attacker can read and alter all application HTTP communications through a compromised dependency.
AIKIDO-2026-10741	HIGH	[axios] An HTTP client vulnerability allows prototype pollution through loose object merging, sensitive data exposure via error serialization, and improper proxy/socket handling that could lead to information disclosure or unauthorized access.
AIKIDO-2026-10823	HIGH	[axios] HTTP adapter incorrectly routes HTTPS traffic through HTTP proxies in cleartext instead of using CONNECT tunnels, allowing proxies to observe sensitive request metadata and payloads that should be encrypted.
AIKIDO-2026-291630	HIGH	[axios] Cross-origin redirects leak custom credential headers like X-API-Key and AWS tokens to unintended hosts, allowing attackers to steal sensitive authentication data. This information disclosure vulnerability affects shared environments where secret headers are set by default.
AIKIDO-2026-10509	HIGH	[axios] Prototype pollution vulnerability allows attackers to inject malicious headers into requests through unsafe FormData detection and header merging, potentially enabling authorization bypass or request manipulation.
GHSA-f4gw-2p7v-4548	MEDIUM	[axios] Axios does not treat 0.0.0.0 as a local address when evaluating NO_PROXY rules, allowing requests to 0.0.0.0 to be routed through configured proxies instead of bypassing them. This enables SSRF attacks when attackers control request URLs and the proxy can reach local services.
GHSA-7q8q-rj6j-mhjq	MEDIUM	[axios] Prototype pollution in nested request options allows inherited Object.prototype properties to inject malicious Authorization headers and manipulate query strings when applications pass placeholder objects like auth: {} or paramsSerializer: {}. This enables credential exfiltration and request tampering when another component has already polluted the prototype chain.
GHSA-jqh4-m9w3-8hp9	MEDIUM	[axios] The fetch adapter fails to enforce maxBodyLength limits on WHATWG ReadableStream request bodies with unknown sizes, allowing attackers to bypass upload size restrictions and cause unexpected network egress or resource exhaustion.
GHSA-mmx7-hfxf-jppx	MEDIUM	[axios] Prototype pollution read-side gadgets in axios allow attackers who pollute Object.prototype to hijack requests by injecting malicious data, proxy settings, or parameter serializers into bodyless methods and low-level adapter calls. This can result in credential theft, request body injection, traffic redirection, or URL manipulation depending on the attack vector.
GHSA-mwf2-3pr3-8698	MEDIUM	[axios] Streamed request bodies bypass maxBodyLength enforcement when sent over HTTP/2, allowing attackers to transmit arbitrarily large payloads and exhaust resources or bypass configured egress limits. This affects Node.js applications forwarding untrusted streams to HTTP/2 endpoints.
GHSA-pmv8-rq9r-6j72	MEDIUM	[axios] Uncontrolled recursion in formDataToJSON allows attackers to crash the process by submitting FormData with deeply nested bracket-delimited field names, causing stack exhaustion and denial of service.
AIKIDO-2026-38469	MEDIUM	[axios] Malformed HTTP/HTTPS URLs without // (e.g., https:internal.example) were silently normalized instead of rejected, allowing attackers to bypass URL allowlists or WAF checks and reach unintended hosts. The fix now throws an error for invalid scheme URLs before normalization.
AIKIDO-2026-10820	MEDIUM	[axios] Request size limits were not enforced in the fetch adapter, allowing responses and bodies to exceed configured limits, potentially causing denial of service or memory exhaustion. The vulnerability has been fixed to properly reject oversized responses and bodies.
AIKIDO-2026-10822	LOW	[axios] A prototype pollution vulnerability in the formDataToJSON helper allows attackers to pollute Object.prototype through specially crafted multipart field names, potentially enabling remote code execution or other malicious actions.

🔗 Related Tasks

• https://linear.app/lifi-linear/issue/AIK-6/major-upgrade-for-axios
• https://linear.app/lifi-linear/issue/AIK-50/aikido-fix-security-issue-in-axios-via-minor-version-upgrade-from-1150

🤖 Remediation details

Fix axios security vulnerabilities by updating to patched version

axios was declared as a direct dependency at ^1.15.0 (resolving to 1.15.0) in the root package.json. Multiple high- and medium-severity advisories affect axios versions below 1.18.0. The declared specifier was bumped to ^1.18.0 and the lockfile was refreshed, resolving to 1.19.0.

axios

axios is a direct dependency in the root package.json, previously declared at ^1.15.0 and resolving to 1.15.0. Fourteen advisories (ranging from LOW to HIGH severity) cover various ranges within the 1.x line, with the highest patched floor being 1.18.0. The specifier was updated to ^1.18.0 and pnpm install --lockfile-only was run, causing pnpm to resolve axios to 1.19.0, which satisfies every patched version requirement. No overrides were needed.

Version changes

Package	From	To	Why updated
axios	^1.15.0 (resolved 1.15.0)	^1.18.0 (resolved 1.19.0)	Direct CVE fix