CVE-2025-58754 is a high-severity (CVSS 7.5) CWE-770 vulnerability in axios. A fix is available for axios — see the affected versions and patch details below.
Axios is vulnerable to DoS attack through lack of data size check
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-58754.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-58754 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
axiosnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | axios | ≥ 1.0.0&&< 1.12.0 | 1.12.0npm install axios@1.12.0 |
| 📦npm | axios | ≥ 0.28.0&&< 0.30.2 | 0.30.2npm install axios@0.30.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for axios, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update axios to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58754 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-58754 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-58754. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Availability impact is limited to the application which bundles axios and not the host Red Hat system.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | ansible-builder-0:3.1.1-1.el8ap | RHSA-2025:23069 |
| Multicluster Global Hub 1.6.5 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1773650060 | RHSA-2026:6226 |
| Red Hat Advanced Cluster Management for Kubernetes 2.12 | rhacm2/acm-grafana-rhel9:v2.12 | RHSA-2025:19961 |
| Red Hat Advanced Cluster Management for Kubernetes 2.12 | rhacm2/acm-grafana-rhel9:v2.12 | RHSA-2025:22684 |
| Red Hat Advanced Cluster Management for Kubernetes 2.13 | rhacm2/acm-grafana-rhel9:1767570373 | RHSA-2026:0627 |
| Red Hat Advanced Cluster Management for Kubernetes 2.13 | rhacm2/acm-grafana-rhel9:1767570373 | RHSA-2026:0718 |
| Red Hat Advanced Cluster Management for Kubernetes 2.14 | rhacm2/acm-grafana-rhel9:v2.14 | RHSA-2025:19335 |
| Red Hat Advanced Cluster Security 4.7 | advanced-cluster-security/rhacs-main-rhel8:4.7 | RHSA-2025:19804 |
Frequently Asked Questions
Is CVE-2025-58754 in your dependencies?
O3 Security finds CVE-2025-58754 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.