[Aikido] Fix security issue in axios via minor version upgrade from 1.13.4 to 1.19.0

[aikido-autofix]

---

Summary / Description

Upgrade axios to fix critical security vulnerabilities including proxy bypass/SSRF, prototype pollution MITM attacks, credential header leakage on redirects, and sensitive data exposure in error serialization.

Security Impact — CVE vulnerabilities fixed by this PR

✅ 18 CVEs resolved by this upgrade

This PR will resolve the following CVEs:

Issue	Severity	Description
CVE-2025-62718	HIGH	[axios] Improper hostname normalization in NO_PROXY rule checking allows requests to loopback addresses (localhost., [::1]) to bypass proxy protections, enabling proxy bypass and potential SSRF attacks against internal services. This vulnerability permits attackers to reach sensitive services despite configured NO_PROXY protections.
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.
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.
CVE-2026-40175	HIGH	[axios] A prototype pollution vulnerability in a third-party dependency can be exploited to inject unsanitized header values into outbound HTTP requests. This allows attackers to manipulate request headers, potentially leading to request smuggling, cache poisoning, or other header-based attacks.
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-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-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.
CVE-2026-25639	MEDIUM	[axios] The mergeConfig function crashes with a TypeError when processing configuration objects containing proto as an own property, allowing attackers to trigger denial of service. An attacker can exploit this by providing a malicious configuration object created via JSON.parse().
GHSA-42h9-826w-cgv3	MEDIUM	[axios] Uncontrolled recursion in formDataToJSON when processing deeply nested FormData field names causes stack overflow, resulting in denial of service for applications converting untrusted FormData to JSON.
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-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.
GHSA-mwf2-3pr3-8698	LOW	[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.
AIKIDO-2026-10819	LOW	[axios] A regular expression vulnerability in browser cookie parsing allowed metacharacters in cookie names to cause incorrect matching or excessive CPU consumption. The vulnerability was fixed by switching to literal string comparison instead of regex-based matching.

Breaking Changes & Upgrade Impact — prefer Warnings / Cautions / ⚠️ sections over implementation sections (upgrade risks, breaking changes, manual migration steps)

⚠️ Breaking changes analysis not available for: axios

Fix Details / Technical Implementation (detailed write-up of what was changed and why)

🤖 Remediation details

Bump axios to resolve multiple high/medium/low severity vulnerabilities

Short summary

This PR remediates 18 CVEs and advisories affecting axios, a direct runtime dependency declared in the root package.json. The fix updates the declared version range in package.json and refreshes yarn.lock so the resolved version moves from the vulnerable 1.13.4 to 1.19.0.

axios

axios is a direct dependency in the root package.json under dependencies. The declared range was ^1.13.4, which resolved to 1.13.4—a version affected by 18 advisories spanning SSRF, header injection, credential leakage, and related issues. The range was narrowed to ^1.18.0 (the minimum that satisfies all patched-version specs across the full advisory set), and yarn install resolved it to 1.19.0, the latest compatible release. No parent bumps, transitive walks, or resolutions overrides were required because axios is already a direct dependency.

Version changes

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

[gitstream-cm]

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 250/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.

[pr-auditor]

✅ Security Analysis Results

Great news! No security issues found in this pull request.

Analysis Summary:

• 📁 Files reviewed: 2
• ✅ No security vulnerabilities detected

---

💡 Trigger a new security scan by commenting @pr-auditor rescan on this PR.

Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page