CVE-2024-39338 — axios
MEDIUMCVE-2024-39338 is a medium-severity (CVSS 4) Server-Side Request Forgery (SSRF) vulnerability in axios. 1 public exploit reference exists, so weaponization risk is real. A fix is available for axios — see the affected versions and patch details below.
Server-Side Request Forgery in axios
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.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-39338.
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-2024-39338 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,238 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 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | axios | ≥ 1.3.2&&< 1.7.4 | 1.7.4npm install axios@1.7.4 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
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.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39338 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-2024-39338 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-39338. 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.
This vulnerability is rated as IMPORTANT because it can be exploited remotely with low complexity and without user interaction, it poses a significant risk to confidentiality.
| Product | Fixed in | Advisory |
|---|---|---|
| Discovery 1 for RHEL 9 | discovery/discovery-server-rhel9:1.12.0-1 | RHSA-2025:1249 |
| NETWORK-OBSERVABILITY-1.7.0-RHEL-9 | network-observability/network-observability-cli-rhel9:v1.7.0-67 | RHSA-2024:8014 |
| OpenShift-Pipelines-1.16-RHEL-8 | openshift-pipelines/pipelines-chains-controller-rhel8:v1.16.0-6 | RHEA-2024:7870 |
| Red Hat Migration Toolkit for Containers 1.8 | rhmtc/openshift-migration-ui-rhel8:v1.8.4-10 | RHSA-2024:7164 |
| Red Hat OpenShift Container Platform 4.17 | openshift4/ose-console-rhel9:v4.17.0-202411050935.p0.gbba7284.assembly.stream.el9 | RHSA-2024:8981 |
| Red Hat OpenShift Container Platform 4.18 | openshift4/aws-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.g088dcaf.assembly.stream.el9 | RHSA-2024:6122 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/code-rhel8:3.16-20 | RHSA-2024:6667 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/grafana-rhel8:2.4.10-3 | RHSA-2024:6209 |
Frequently Asked Questions
Is CVE-2024-39338 in your dependencies?
O3 Security finds CVE-2024-39338 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.