*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
CVE-2026-49978
Vulnerable Library - dompurify-2.5.6.tgz
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. It's written in JavaScript and works in all modern browsers (Safari, Opera (15+), Internet Explorer (10+), Firefox and Chrome - as well as almost anything else usin
Library home page: https://registry.npmjs.org/dompurify/-/dompurify-2.5.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/dompurify-npm-2.5.6-535512fe69-ef5fdc075e.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- isomorphic-dompurify-0.27.0.tgz
- ❌ dompurify-2.5.6.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Prior to 3.4.7, DOMPurify IN_PLACE sanitization could skip shadow contents attached to an element inside .content, allowing attacker-controlled markup such as event handlers, JavaScript URLs, or scripts to survive and execute when an application cloned and inserted the sanitized template. This issue is fixed in version 3.4.7.
Publish Date: 2026-07-14
URL: CVE-2026-49978
CVSS 3 Score Details (9.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: cure53/DOMPurify@ca30f07
Release Date: 2026-06-15
Fix Resolution: https://github.com/cure53/DOMPurify.git - 3.4.7
CVE-2025-7783
Vulnerable Library - form-data-4.0.0.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/form-data-npm-4.0.0-916facec2d-7264aa760a.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- isomorphic-dompurify-0.27.0.tgz
- jsdom-21.1.2.tgz
- ❌ form-data-4.0.0.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js.
This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-07-18
URL: CVE-2025-7783
CVSS 3 Score Details (8.7)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-fjxv-7rqg-78g4
Release Date: 2025-07-18
Fix Resolution: form-data - 3.0.4,https://github.com/form-data/form-data.git - v2.5.4,form-data - 4.0.4,https://github.com/form-data/form-data.git - v4.0.4,form-data - 2.5.4,https://github.com/form-data/form-data.git - v3.0.4
CVE-2026-44492
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios does not normalise IPv4-mapped IPv6 addresses. When NO_PROXY lists an IPv4 address such as 127.0.0.1 or 169.254.169.254, a request URL using the IPv4-mapped IPv6 form (::ffff:7f00:1, ::ffff:a9fe:a9fe) still routes through the configured proxy. Node.js resolves these addresses to the underlying IPv4 host, so the request reaches the internal service via the proxy rather than being blocked. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44492
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-pjwm-pj3p-43mv
Release Date: 2026-05-31
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 1.16.0,axios - 0.32.0
WS-2023-0439
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is vulnerable to Regular Expression Denial of Service (ReDoS). When a manipulated string is provided as input to the format method, the regular expression exhibits a time complexity of O(n^2). Server becomes unable to provide normal service due to the excessive cost and time wasted in processing vulnerable regular expressions.
Publish Date: 2026-05-20
URL: WS-2023-0439
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.mend.io/vulnerability-database/WS-2023-0439
Release Date: 2026-05-15
Fix Resolution: axios - 0.29.0,axios - 1.6.3,axios - 0.29.0,axios - 1.6.3
CVE-2026-48779
Vulnerable Library - ws-8.20.1.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-8.20.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/ws-npm-8.20.1-b0e0eae8d5-8c4d2b06dc.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- isomorphic-dompurify-0.27.0.tgz
- jsdom-21.1.2.tgz
- ❌ ws-8.20.1.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.
Publish Date: 2026-06-16
URL: CVE-2026-48779
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: websockets/ws@2b2abd458a1b
Release Date: 2026-06-16
Fix Resolution: https://github.com/websockets/ws.git - 7.5.11,https://github.com/websockets/ws.git - 8.21.0,https://github.com/websockets/ws.git - 6.2.4,https://github.com/websockets/ws.git - 5.2.5
CVE-2026-46625
Vulnerable Library - js-cookie-2.2.1.tgz
A simple, lightweight JavaScript API for handling cookies
Library home page: https://registry.npmjs.org/js-cookie/-/js-cookie-2.2.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/js-cookie-npm-2.2.1-e879cd2148-4387f5f569.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ js-cookie-2.2.1.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "proto" member is an own enumerable property, so the for…in enumerates it and the target[key] = source[key] write triggers the Object.prototype.proto setter on the fresh target ({}). The result is a per-instance prototype hijack: Object.prototype itself is untouched, but the merged attributes object now inherits attacker-controlled keys. Because the consuming set() function then enumerates the merged object with another for...in, every key the attacker placed on the polluted prototype lands in the resulting Set-Cookie string as an attribute pair. The attacker can set domain=, secure=, samesite=, expires=, and path= on cookies whose attributes the developer thought were locked down. This issue has been patched in version 3.0.7.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-06-10
URL: CVE-2026-46625
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-qjx8-664m-686j
Release Date: 2026-05-23
Fix Resolution: js-cookie - 3.0.7,https://github.com/js-cookie/js-cookie.git - v3.0.7
CVE-2026-44496
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Axios versions before 0.32.0 on the 0.x line and before 1.16.0 on the 1.x line build a regular expression from the configured XSRF cookie name without escaping regex metacharacters. In standard browser environments, an attacker who can influence the cookie name passed to axios can cause expensive regex backtracking while axios reads document.cookie. The practical impact is client-side availability degradation, such as freezing the affected browser tab while axios prepares a request. The issue does not affect ordinary Node.js HTTP adapter usage, React Native, or web workers, where axios does not read document.cookie. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44496
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-hfxv-24rg-xrqf
Release Date: 2026-06-04
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 0.32.0,axios - 1.16.0
CVE-2026-44487
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’s Node.js HTTP adapter may forward a Proxy-Authorization header to a redirected origin during specific proxy-to-direct redirect flows. This affects Node.js usage, where an initial HTTP request is sent through an authenticated HTTP proxy, redirects are followed, and the redirected URL is no longer proxied. Under affected redirect shapes, the final origin can receive the proxy credential that was intended only for the outbound proxy. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44487
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-p92q-9vqr-4j8v
Release Date: 2026-06-04
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 1.16.0,axios - 0.32.0
CVE-2026-44486
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’ Node.js HTTP adapter can leak proxy credentials to a redirect target in affected versions. When a request is sent through an authenticated proxy, Axios may add a Proxy-Authorization header. If Axios then follows a redirect and the redirected request is no longer sent through that proxy, the stale Proxy-Authorization header can remain on the redirected request and be sent to the redirect target. This affects Node.js's use of Axios with automatic redirects enabled and an authenticated proxy configuration. Browser adapters are not affected. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44486
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-j5f8-grm9-p9fc
Release Date: 2026-06-04
Fix Resolution: axios - 0.32.0,axios - 1.16.0,axios - 1.16.0,axios - 0.32.0
CVE-2026-25639
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to versions 0.30.3 and 1.13.5, the mergeConfig function in axios crashes with a TypeError when processing configuration objects containing proto as an own property. An attacker can trigger this by providing a malicious configuration object created via JSON.parse(), causing complete denial of service. This vulnerability is fixed in versions 0.30.3 and 1.13.5.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-02-09
URL: CVE-2026-25639
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: axios/axios@28c7215
Release Date: 2026-02-09
Fix Resolution: https://github.com/axios/axios.git - v1.13.5
CVE-2026-12143
Vulnerable Library - form-data-4.0.0.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/form-data-npm-4.0.0-916facec2d-7264aa760a.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- isomorphic-dompurify-0.27.0.tgz
- jsdom-21.1.2.tgz
- ❌ form-data-4.0.0.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the "field" argument to "FormData#append" and the "filename" option are concatenated verbatim into the "Content-Disposition" header without escaping carriage return (CR), line feed (LF), or double-quote (") characters. An application that passes attacker-controlled data as a field name or filename (for example, an API gateway that turns JSON object keys into multipart field names) allows the attacker to terminate the header line and inject additional headers, or to smuggle entire additional multipart parts, into the request the application forwards to a backend. This can let the attacker add or override form fields (e.g. set "is_admin=true") seen by the downstream parser. This is an instance of CWE-93 (CRLF injection). The fix escapes CR, LF, and """ as "%0D", "%0A", and "%22" in field names and filenames, matching the serialization browsers use per the WHATWG HTML multipart/form-data encoding algorithm. Exploitation requires the consuming application to use untrusted input as a field name or filename; applications that use only fixed/trusted field names are not affected. Fixed in 2.5.6, 3.0.5, and 4.0.6.
Publish Date: 2026-06-12
URL: CVE-2026-12143
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/form-data/form-data/security/advisories/GHSA-fjwh-7mfq-fhwh
Release Date: 2026-06-12
Fix Resolution: form-data - 4.0.6,form-data - 3.0.5,form-data - 2.5.6
CVE-2025-58754
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. When Axios starting in version 0.28.0 and prior to versions 0.30.2 and 1.12.0 runs on Node.js and is given a URL with the "data:" scheme, it does not perform HTTP. Instead, its Node http adapter decodes the entire payload into memory ("Buffer"/"Blob") and returns a synthetic 200 response. This path ignores "maxContentLength" / "maxBodyLength" (which only protect HTTP responses), so an attacker can supply a very large "data:" URI and cause the process to allocate unbounded memory and crash (DoS), even if the caller requested "responseType: 'stream'". Versions 0.30.2 and 1.12.0 contain a patch for the issue.
Publish Date: 2025-09-12
URL: CVE-2025-58754
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-4hjh-wcwx-xvwj
Release Date: 2025-09-12
Fix Resolution: https://github.com/axios/axios.git - v1.12.0,axios - 0.30.2,axios - 0.30.2,axios - 1.12.0,axios - 1.12.0
CVE-2025-27152
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
axios is a promise based HTTP client for the browser and node.js. The issue occurs when passing absolute URLs rather than protocol-relative URLs to axios. Even if baseURL is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios. This issue is fixed in 1.8.2.
Publish Date: 2025-03-07
URL: CVE-2025-27152
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-jr5f-v2jv-69x6
Release Date: 2025-03-07
Fix Resolution: axios - 0.30.0,axios - 1.8.2,axios - 1.8.2
CVE-2026-42035
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, a prototype pollution gadget exists in the Axios HTTP adapter (lib/adapters/http.js) that allows an attacker to inject arbitrary HTTP headers into outgoing requests. The vulnerability exploits duck-type checking of the data payload, where if Object.prototype is polluted with getHeaders, append, pipe, on, once, and Symbol.toStringTag, Axios misidentifies any plain object payload as a FormData instance and calls the attacker-controlled getHeaders() function, merging the returned headers into the outgoing request. The vulnerable code resides exclusively in lib/adapters/http.js. The prototype pollution source does not need to originate from Axios itself — any prototype pollution primitive in any dependency in the application's dependency tree is sufficient to trigger this gadget. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42035
CVSS 3 Score Details (7.4)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-6chq-wfr3-2hj9
Release Date: 2026-04-24
Fix Resolution: axios - 1.15.1,axios - 0.31.1,axios - 1.15.1,axios - 0.31.1
CVE-2026-42033
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept and modify every JSON response before the application sees it, or (b) fully hijack the underlying HTTP transport, gaining access to request credentials, headers, and body. The precondition is prototype pollution from a separate source in the same process. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42033
CVSS 3 Score Details (7.4)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-pf86-5x62-jrwf
Release Date: 2026-04-24
Fix Resolution: axios - 1.15.1,axios - 0.31.1,axios - 1.15.1,axios - 0.31.1
CVE-2026-42043
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, an attacker who can influence the target URL of an Axios request can use any address in the 127.0.0.0/8 range (other than 127.0.0.1) to completely bypass the NO_PROXY protection. This vulnerability is due to an incomplete for CVE-2025-62718, This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42043
CVSS 3 Score Details (7.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-pmwg-cvhr-8vh7
Release Date: 2026-04-24
Fix Resolution: axios - 0.31.1,axios - 1.15.1,axios - 1.15.1,axios - 0.31.1
CVE-2025-62718
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.
Publish Date: 2026-04-09
URL: CVE-2025-62718
CVSS 3 Score Details (7.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-3p68-rc4w-qgx5
Release Date: 2026-04-09
Fix Resolution: https://github.com/axios/axios.git - v1.15.0,axios - 1.15.0,axios - 0.31.0,axios - 0.31.0,axios - 1.15.0
CVE-2026-44495
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. From 0.19.0 to before 0.31.1 and 1.15.2, Axios contains prototype-pollution gadgets in request config processing. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. Axios does not itself create the prototype pollution. Exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request. This vulnerability is fixed in 0.31.1 and 1.15.2.
Publish Date: 2026-06-11
URL: CVE-2026-44495
CVSS 3 Score Details (7.0)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-3g43-6gmg-66jw
Release Date: 2026-05-31
Fix Resolution: axios - 1.15.2,axios - 0.31.1,axios - 0.31.1,axios - 1.15.2
CVE-2026-42038
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, he fix for no_proxy hostname normalization bypass is incomplete. When no_proxy=localhost is set, requests to 127.0.0.1 and [::1] still route through the proxy instead of bypassing it. The shouldBypassProxy() function does pure string matching — it does not resolve IP aliases or loopback equivalents. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42038
CVSS 3 Score Details (6.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-m7pr-hjqh-92cm
Release Date: 2026-04-24
Fix Resolution: axios - 0.31.1,axios - 1.15.1,axios - 0.31.1,axios - 1.15.1
CVE-2026-41239
Vulnerable Library - dompurify-2.5.6.tgz
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. It's written in JavaScript and works in all modern browsers (Safari, Opera (15+), Internet Explorer (10+), Firefox and Chrome - as well as almost anything else usin
Library home page: https://registry.npmjs.org/dompurify/-/dompurify-2.5.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/dompurify-npm-2.5.6-535512fe69-ef5fdc075e.zip
Dependency Hierarchy:
- @carbon/ibmdotcom-services-store-1.53.7.tgz (Root Library)
- ibmdotcom-utilities-1.53.0.tgz
- isomorphic-dompurify-0.27.0.tgz
- ❌ dompurify-2.5.6.tgz (Vulnerable Library)
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Summary | Field | Value | |:------|:------| | Severity | Medium | | Affected | DOMPurify "main" at ""883ac15"" (https://github.com/cure53/DOMPurify/tree/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6), introduced in v1.0.10 (""7fc196db"" (cure53/DOMPurify@7fc196d)) | "SAFE_FOR_TEMPLATES" strips "{{...}}" expressions from untrusted HTML. This works in string mode but not with "RETURN_DOM" or "RETURN_DOM_FRAGMENT", allowing XSS via template-evaluating frameworks like Vue 2. Technical Details DOMPurify strips template expressions in two passes: 1. Per-node — each text node is checked during the tree walk (""purify.ts:1179-1191"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1179-L1191)): // pass #1: runs on every text node during tree walk if (SAFE_FOR_TEMPLATES && currentNode.nodeType === NODE_TYPE.text) { content = currentNode.textContent; content = content.replace(MUSTACHE_EXPR, ' '); // {{...}} -> ' ' content = content.replace(ERB_EXPR, ' '); // <%...%> -> ' ' content = content.replace(TMPLIT_EXPR, ' '); // ${... -> ' ' currentNode.textContent = content; } 2. Final string scrub — after serialization, the full HTML string is scrubbed again (""purify.ts:1679-1683"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1679-L1683)). This is the safety net that catches expressions that only form after the DOM settles. The "RETURN_DOM" path returns before pass #2 ever runs (""purify.ts:1637-1661"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1637-L1661)): // purify.ts (simplified) if (RETURN_DOM) { // ... build returnNode ... return returnNode; // <-- exits here, pass #2 never runs } // pass #2: only reached by string-mode callers if (SAFE_FOR_TEMPLATES) { serializedHTML = serializedHTML.replace(MUSTACHE_EXPR, ' '); } return serializedHTML; The payload "{{constructor.constructor('alert(1)')()}}" exploits this: 3. Parser creates: "TEXT("{")" → "" → "TEXT("{payload}")" → "" → "TEXT("}")" — no single node contains "{{", so pass #1 misses it 4. "" is not allowed, so DOMPurify removes it but keeps surrounding text 5. The three text nodes are now adjacent — ".outerHTML" reads them as "{{payload}}", which Vue 2 compiles and executes
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-04-23
URL: CVE-2026-41239
CVSS 3 Score Details (6.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-crv5-9vww-q3g8
Release Date: 2026-04-22
Fix Resolution: dompurify - 3.4.0,dompurify - 3.4.0
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/dompurify-npm-2.5.6-535512fe69-ef5fdc075e.zip
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - dompurify-2.5.6.tgz
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. It's written in JavaScript and works in all modern browsers (Safari, Opera (15+), Internet Explorer (10+), Firefox and Chrome - as well as almost anything else usin
Library home page: https://registry.npmjs.org/dompurify/-/dompurify-2.5.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/dompurify-npm-2.5.6-535512fe69-ef5fdc075e.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Prior to 3.4.7, DOMPurify IN_PLACE sanitization could skip shadow contents attached to an element inside .content, allowing attacker-controlled markup such as event handlers, JavaScript URLs, or scripts to survive and execute when an application cloned and inserted the sanitized template. This issue is fixed in version 3.4.7.
Publish Date: 2026-07-14
URL: CVE-2026-49978
CVSS 3 Score Details (9.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: cure53/DOMPurify@ca30f07
Release Date: 2026-06-15
Fix Resolution: https://github.com/cure53/DOMPurify.git - 3.4.7
Vulnerable Library - form-data-4.0.0.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/form-data-npm-4.0.0-916facec2d-7264aa760a.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js.
This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-07-18
URL: CVE-2025-7783
CVSS 3 Score Details (8.7)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-fjxv-7rqg-78g4
Release Date: 2025-07-18
Fix Resolution: form-data - 3.0.4,https://github.com/form-data/form-data.git - v2.5.4,form-data - 4.0.4,https://github.com/form-data/form-data.git - v4.0.4,form-data - 2.5.4,https://github.com/form-data/form-data.git - v3.0.4
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios does not normalise IPv4-mapped IPv6 addresses. When NO_PROXY lists an IPv4 address such as 127.0.0.1 or 169.254.169.254, a request URL using the IPv4-mapped IPv6 form (::ffff:7f00:1, ::ffff:a9fe:a9fe) still routes through the configured proxy. Node.js resolves these addresses to the underlying IPv4 host, so the request reaches the internal service via the proxy rather than being blocked. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44492
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-pjwm-pj3p-43mv
Release Date: 2026-05-31
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 1.16.0,axios - 0.32.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is vulnerable to Regular Expression Denial of Service (ReDoS). When a manipulated string is provided as input to the format method, the regular expression exhibits a time complexity of O(n^2). Server becomes unable to provide normal service due to the excessive cost and time wasted in processing vulnerable regular expressions.
Publish Date: 2026-05-20
URL: WS-2023-0439
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://www.mend.io/vulnerability-database/WS-2023-0439
Release Date: 2026-05-15
Fix Resolution: axios - 0.29.0,axios - 1.6.3,axios - 0.29.0,axios - 1.6.3
Vulnerable Library - ws-8.20.1.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-8.20.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/ws-npm-8.20.1-b0e0eae8d5-8c4d2b06dc.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.
Publish Date: 2026-06-16
URL: CVE-2026-48779
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: websockets/ws@2b2abd458a1b
Release Date: 2026-06-16
Fix Resolution: https://github.com/websockets/ws.git - 7.5.11,https://github.com/websockets/ws.git - 8.21.0,https://github.com/websockets/ws.git - 6.2.4,https://github.com/websockets/ws.git - 5.2.5
Vulnerable Library - js-cookie-2.2.1.tgz
A simple, lightweight JavaScript API for handling cookies
Library home page: https://registry.npmjs.org/js-cookie/-/js-cookie-2.2.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/js-cookie-npm-2.2.1-e879cd2148-4387f5f569.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "proto" member is an own enumerable property, so the for…in enumerates it and the target[key] = source[key] write triggers the Object.prototype.proto setter on the fresh target ({}). The result is a per-instance prototype hijack: Object.prototype itself is untouched, but the merged attributes object now inherits attacker-controlled keys. Because the consuming set() function then enumerates the merged object with another for...in, every key the attacker placed on the polluted prototype lands in the resulting Set-Cookie string as an attribute pair. The attacker can set domain=, secure=, samesite=, expires=, and path= on cookies whose attributes the developer thought were locked down. This issue has been patched in version 3.0.7.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-06-10
URL: CVE-2026-46625
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-qjx8-664m-686j
Release Date: 2026-05-23
Fix Resolution: js-cookie - 3.0.7,https://github.com/js-cookie/js-cookie.git - v3.0.7
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Axios versions before 0.32.0 on the 0.x line and before 1.16.0 on the 1.x line build a regular expression from the configured XSRF cookie name without escaping regex metacharacters. In standard browser environments, an attacker who can influence the cookie name passed to axios can cause expensive regex backtracking while axios reads document.cookie. The practical impact is client-side availability degradation, such as freezing the affected browser tab while axios prepares a request. The issue does not affect ordinary Node.js HTTP adapter usage, React Native, or web workers, where axios does not read document.cookie. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44496
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-hfxv-24rg-xrqf
Release Date: 2026-06-04
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 0.32.0,axios - 1.16.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’s Node.js HTTP adapter may forward a Proxy-Authorization header to a redirected origin during specific proxy-to-direct redirect flows. This affects Node.js usage, where an initial HTTP request is sent through an authenticated HTTP proxy, redirects are followed, and the redirected URL is no longer proxied. Under affected redirect shapes, the final origin can receive the proxy credential that was intended only for the outbound proxy. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44487
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-p92q-9vqr-4j8v
Release Date: 2026-06-04
Fix Resolution: axios - 1.16.0,axios - 0.32.0,axios - 1.16.0,axios - 0.32.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’ Node.js HTTP adapter can leak proxy credentials to a redirect target in affected versions. When a request is sent through an authenticated proxy, Axios may add a Proxy-Authorization header. If Axios then follows a redirect and the redirected request is no longer sent through that proxy, the stale Proxy-Authorization header can remain on the redirected request and be sent to the redirect target. This affects Node.js's use of Axios with automatic redirects enabled and an authenticated proxy configuration. Browser adapters are not affected. This vulnerability is fixed in 0.32.0 and 1.16.0.
Publish Date: 2026-06-11
URL: CVE-2026-44486
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-j5f8-grm9-p9fc
Release Date: 2026-06-04
Fix Resolution: axios - 0.32.0,axios - 1.16.0,axios - 1.16.0,axios - 0.32.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to versions 0.30.3 and 1.13.5, the mergeConfig function in axios crashes with a TypeError when processing configuration objects containing proto as an own property. An attacker can trigger this by providing a malicious configuration object created via JSON.parse(), causing complete denial of service. This vulnerability is fixed in versions 0.30.3 and 1.13.5.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-02-09
URL: CVE-2026-25639
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: axios/axios@28c7215
Release Date: 2026-02-09
Fix Resolution: https://github.com/axios/axios.git - v1.13.5
Vulnerable Library - form-data-4.0.0.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/form-data-npm-4.0.0-916facec2d-7264aa760a.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the "field" argument to "FormData#append" and the "filename" option are concatenated verbatim into the "Content-Disposition" header without escaping carriage return (CR), line feed (LF), or double-quote (") characters. An application that passes attacker-controlled data as a field name or filename (for example, an API gateway that turns JSON object keys into multipart field names) allows the attacker to terminate the header line and inject additional headers, or to smuggle entire additional multipart parts, into the request the application forwards to a backend. This can let the attacker add or override form fields (e.g. set "is_admin=true") seen by the downstream parser. This is an instance of CWE-93 (CRLF injection). The fix escapes CR, LF, and """ as "%0D", "%0A", and "%22" in field names and filenames, matching the serialization browsers use per the WHATWG HTML multipart/form-data encoding algorithm. Exploitation requires the consuming application to use untrusted input as a field name or filename; applications that use only fixed/trusted field names are not affected. Fixed in 2.5.6, 3.0.5, and 4.0.6.
Publish Date: 2026-06-12
URL: CVE-2026-12143
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/form-data/form-data/security/advisories/GHSA-fjwh-7mfq-fhwh
Release Date: 2026-06-12
Fix Resolution: form-data - 4.0.6,form-data - 3.0.5,form-data - 2.5.6
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. When Axios starting in version 0.28.0 and prior to versions 0.30.2 and 1.12.0 runs on Node.js and is given a URL with the "data:" scheme, it does not perform HTTP. Instead, its Node http adapter decodes the entire payload into memory ("Buffer"/"Blob") and returns a synthetic 200 response. This path ignores "maxContentLength" / "maxBodyLength" (which only protect HTTP responses), so an attacker can supply a very large "data:" URI and cause the process to allocate unbounded memory and crash (DoS), even if the caller requested "responseType: 'stream'". Versions 0.30.2 and 1.12.0 contain a patch for the issue.
Publish Date: 2025-09-12
URL: CVE-2025-58754
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-4hjh-wcwx-xvwj
Release Date: 2025-09-12
Fix Resolution: https://github.com/axios/axios.git - v1.12.0,axios - 0.30.2,axios - 0.30.2,axios - 1.12.0,axios - 1.12.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
axios is a promise based HTTP client for the browser and node.js. The issue occurs when passing absolute URLs rather than protocol-relative URLs to axios. Even if baseURL is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios. This issue is fixed in 1.8.2.
Publish Date: 2025-03-07
URL: CVE-2025-27152
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-jr5f-v2jv-69x6
Release Date: 2025-03-07
Fix Resolution: axios - 0.30.0,axios - 1.8.2,axios - 1.8.2
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, a prototype pollution gadget exists in the Axios HTTP adapter (lib/adapters/http.js) that allows an attacker to inject arbitrary HTTP headers into outgoing requests. The vulnerability exploits duck-type checking of the data payload, where if Object.prototype is polluted with getHeaders, append, pipe, on, once, and Symbol.toStringTag, Axios misidentifies any plain object payload as a FormData instance and calls the attacker-controlled getHeaders() function, merging the returned headers into the outgoing request. The vulnerable code resides exclusively in lib/adapters/http.js. The prototype pollution source does not need to originate from Axios itself — any prototype pollution primitive in any dependency in the application's dependency tree is sufficient to trigger this gadget. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42035
CVSS 3 Score Details (7.4)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-6chq-wfr3-2hj9
Release Date: 2026-04-24
Fix Resolution: axios - 1.15.1,axios - 0.31.1,axios - 1.15.1,axios - 0.31.1
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept and modify every JSON response before the application sees it, or (b) fully hijack the underlying HTTP transport, gaining access to request credentials, headers, and body. The precondition is prototype pollution from a separate source in the same process. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42033
CVSS 3 Score Details (7.4)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-pf86-5x62-jrwf
Release Date: 2026-04-24
Fix Resolution: axios - 1.15.1,axios - 0.31.1,axios - 1.15.1,axios - 0.31.1
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, an attacker who can influence the target URL of an Axios request can use any address in the 127.0.0.0/8 range (other than 127.0.0.1) to completely bypass the NO_PROXY protection. This vulnerability is due to an incomplete for CVE-2025-62718, This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42043
CVSS 3 Score Details (7.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-pmwg-cvhr-8vh7
Release Date: 2026-04-24
Fix Resolution: axios - 0.31.1,axios - 1.15.1,axios - 1.15.1,axios - 0.31.1
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.
Publish Date: 2026-04-09
URL: CVE-2025-62718
CVSS 3 Score Details (7.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-3p68-rc4w-qgx5
Release Date: 2026-04-09
Fix Resolution: https://github.com/axios/axios.git - v1.15.0,axios - 1.15.0,axios - 0.31.0,axios - 0.31.0,axios - 1.15.0
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. From 0.19.0 to before 0.31.1 and 1.15.2, Axios contains prototype-pollution gadgets in request config processing. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. Axios does not itself create the prototype pollution. Exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request. This vulnerability is fixed in 0.31.1 and 1.15.2.
Publish Date: 2026-06-11
URL: CVE-2026-44495
CVSS 3 Score Details (7.0)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: Low
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-3g43-6gmg-66jw
Release Date: 2026-05-31
Fix Resolution: axios - 1.15.2,axios - 0.31.1,axios - 0.31.1,axios - 1.15.2
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/axios-npm-0.27.2-dbe3a48aea-2efaf18dd0.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, he fix for no_proxy hostname normalization bypass is incomplete. When no_proxy=localhost is set, requests to 127.0.0.1 and [::1] still route through the proxy instead of bypassing it. The shouldBypassProxy() function does pure string matching — it does not resolve IP aliases or loopback equivalents. This vulnerability is fixed in 1.15.1 and 0.31.1.
Publish Date: 2026-04-24
URL: CVE-2026-42038
CVSS 3 Score Details (6.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-m7pr-hjqh-92cm
Release Date: 2026-04-24
Fix Resolution: axios - 0.31.1,axios - 1.15.1,axios - 0.31.1,axios - 1.15.1
Vulnerable Library - dompurify-2.5.6.tgz
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. It's written in JavaScript and works in all modern browsers (Safari, Opera (15+), Internet Explorer (10+), Firefox and Chrome - as well as almost anything else usin
Library home page: https://registry.npmjs.org/dompurify/-/dompurify-2.5.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/dompurify-npm-2.5.6-535512fe69-ef5fdc075e.zip
Dependency Hierarchy:
Found in HEAD commit: 1b0acefa65abc11bbdc46d2dc34868c7af29ef68
Found in base branch: main
Vulnerability Details
Summary | Field | Value | |:------|:------| | Severity | Medium | | Affected | DOMPurify "main" at ""883ac15"" (https://github.com/cure53/DOMPurify/tree/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6), introduced in v1.0.10 (""7fc196db"" (cure53/DOMPurify@7fc196d)) | "SAFE_FOR_TEMPLATES" strips "{{...}}" expressions from untrusted HTML. This works in string mode but not with "RETURN_DOM" or "RETURN_DOM_FRAGMENT", allowing XSS via template-evaluating frameworks like Vue 2. Technical Details DOMPurify strips template expressions in two passes: 1. Per-node — each text node is checked during the tree walk (""purify.ts:1179-1191"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1179-L1191)): // pass #1: runs on every text node during tree walk if (SAFE_FOR_TEMPLATES && currentNode.nodeType === NODE_TYPE.text) { content = currentNode.textContent; content = content.replace(MUSTACHE_EXPR, ' '); // {{...}} -> ' ' content = content.replace(ERB_EXPR, ' '); // <%...%> -> ' ' content = content.replace(TMPLIT_EXPR, ' '); // ${... -> ' ' currentNode.textContent = content; } 2. Final string scrub — after serialization, the full HTML string is scrubbed again (""purify.ts:1679-1683"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1679-L1683)). This is the safety net that catches expressions that only form after the DOM settles. The "RETURN_DOM" path returns before pass #2 ever runs (""purify.ts:1637-1661"" (https://github.com/cure53/DOMPurify/blob/883ac15d47f907cb1a3b5a152fe90c4d8c10f9e6/src/purify.ts#L1637-L1661)): // purify.ts (simplified) if (RETURN_DOM) { // ... build returnNode ... return returnNode; // <-- exits here, pass #2 never runs } // pass #2: only reached by string-mode callers if (SAFE_FOR_TEMPLATES) { serializedHTML = serializedHTML.replace(MUSTACHE_EXPR, ' '); } return serializedHTML; The payload "{{constructor.constructor('alert(1)')()}}" exploits this: 3. Parser creates: "TEXT("{")" → "" → "TEXT("{payload}")" → "" → "TEXT("}")" — no single node contains "{{", so pass #1 misses it 4. "" is not allowed, so DOMPurify removes it but keeps surrounding text 5. The three text nodes are now adjacent — ".outerHTML" reads them as "{{payload}}", which Vue 2 compiles and executes
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-04-23
URL: CVE-2026-41239
CVSS 3 Score Details (6.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-crv5-9vww-q3g8
Release Date: 2026-04-22
Fix Resolution: dompurify - 3.4.0,dompurify - 3.4.0