CVE-2026-25639 remediation guide

axios axios, Red Hat Ansible Automation Platform 2.6 for RHEL 9, multicluster engine for Kubernetes 2.1

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.

Open CVE record

Productaxios axios, Red Hat Ansible Automation Platform 2.6 for RHEL 9, multicluster engine for Kubernetes 2.1

Affected versions>= >= 1.0.0, < 1.13.5, >= < 0.30.3, < 0.30.3, >= 1.0.0 < 1.13.5

Fixed versions0.30.3, 1.13.5

Priority basisReview · CVSS 7.5 · EPSS 2.50%

Identify the affected asset

Confirm whether axios axios, Red Hat Ansible Automation Platform 2.6 for RHEL 9, multicluster engine for Kubernetes 2.1 is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 1.0.0, < 1.13.5, >= < 0.30.3, < 0.30.3, >= 1.0.0 < 1.13.5. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 0.30.3, 1.13.5. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.