LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25639: Axios affected by Denial of Service via __proto__ Key in mergeConfig

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios can crash when it handles a specially shaped configuration object. If an application lets untrusted data become Axios configuration, an unauthenticated attacker may be able to cause denial of service. The vendor fixed this in Axios 0.30.3 and 1.13.5.

Executive priority

Treat this as a high-priority availability issue for internet-facing services that use Axios with user-influenced configuration. Patch promptly, but prioritize based on whether untrusted input can reach Axios config paths.

Technical view

Before Axios 0.30.3 and 1.13.5, mergeConfig throws a TypeError when processing configuration objects with __proto__ as an own property, including objects created from JSON.parse. The CVSS 3.1 score is 7.5, reflecting network reachability, low complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely in Node.js or browser applications using Axios below 0.30.3 or versions 1.0.0 through 1.13.4, especially where user-controlled JSON or request data can influence Axios configuration or wrapper options.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. The described abuse path is denial of service through malicious configuration input, not data theft or code execution. Practical risk depends on whether attackers can control data passed into Axios configuration merging.

Researcher notes

Key research question is reachability: vulnerable versions alone are not enough to prove exploitable denial of service. Focus analysis on mergeConfig call paths, Axios wrappers, parsed JSON inputs, and whether a thrown TypeError can crash a worker, request handler, or client workflow.

Mitigation direction

  • Upgrade Axios to 0.30.3 or 1.13.5 or later.
  • Review lockfiles and SBOMs for direct and transitive Axios versions.
  • Prevent untrusted JSON or request data from becoming Axios configuration.
  • Validate or strip dangerous configuration keys before merging user-influenced objects.
  • Check Red Hat advisories for downstream package guidance where applicable.

Validation and detection

  • Identify deployed services and frontend bundles that include Axios.
  • Confirm package manifests, lockfiles, and built artifacts use fixed Axios versions.
  • Trace application paths where JSON.parse output can reach Axios configuration.
  • Review internal HTTP client wrappers that merge caller-provided options.
  • Use SCA results to verify no vulnerable Axios dependency remains.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1287: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-754: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25639 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
48Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-25639Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPaxios: Axios affected by Denial of Service via __proto__ Key in mergeConfig
other:Red Hat severity ratingcvssV3_1
  • 2026-02-09T21:00:49.280Z: Reported to Red Hat.
  • 2026-02-09T20:11:22.374Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.0.0, < 1.13.5, < 0.30.3Listed
Weakness

CWE details

CWE-1287CWE-754

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1287 · source CWE mapping

Improper Validation of Specified Type of Input

Improper Validation of Specified Type of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs