Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Axios Cross-Site Request Forgery VulnerabilityGHSA-wf5p-g6vw-rhxx

MEDIUMFix: axios/axios#6028

GHSA-wf5p-g6vw-rhxx is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) 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.

Also known asCVE-2023-45857
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-wf5p-g6vw-rhxx.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk
0.00%0.35%0.70%1.06%0.1%0.6%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-wf5p-g6vw-rhxx by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

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.

180Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
axiosnpm
70.2Mdownloads / week

Description

An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmaxios≥ 1.0.0&&< 1.6.01.6.0npm install axios@1.6.0
📦npmaxios≥ 0.8.1&&< 0.28.00.28.0npm install axios@0.28.0

Affected Products

1 product · 1 configurations
Application
axiosaxios
1 version
1.5.1
Exploits & PoCs
1

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 dependency
  1. Detect

    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.

  2. Fix

    Update axios to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wf5p-g6vw-rhxx is resolved across your whole dependency graph.

  3. 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.

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.

Red HatModerate

For Red Hat Advanced Cluster Management for Kubernetes (RHACM), the affected container was deprecated in ACM 2.5 version which is not anymore supported. Following versions of this product are not impacted by this issue.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-wf5p-g6vw-rhxx (CC BY 4.0)
ProductFixed inAdvisory
Migration Toolkit for Runtimes 1 on RHEL 8axiosRHSA-2024:3920
MTA-6.2-RHEL-9mta/mta-windup-addon-rhel9:6.2.3-2RHSA-2024:3989
MTA-7.0-RHEL-9mta/mta-cli-rhel9:7.0.3-16RHSA-2024:3316
Red Hat Advanced Cluster Security 4.7advanced-cluster-security/rhacs-central-db-rhel8:4.7.0-4RHSA-2025:2876
Red Hat Ansible Automation Platform 2.4 for RHEL 8automation-controller-0:4.5.5-2.el8apRHSA-2024:1640
Red Hat Migration Toolkit for Containers 1.8rhmtc/openshift-migration-ui-rhel8:v1.8.3-4RHSA-2024:1925
RHEL-8-CNV-4.12container-native-virtualization/kubevirt-console-plugin:v4.12.12-7RHSA-2024:4269
RHEL-9-CNV-4.13container-native-virtualization/kubevirt-console-plugin-rhel9:v4.13.10-387RHSA-2024:5314

Frequently Asked Questions

An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
O3 Security · Impact-Aware SCA

Is GHSA-wf5p-g6vw-rhxx in your dependencies?

Find it across npm, including transitive dependencies.

Axios Cross-Site Request Forgery Vulnerability