BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-44490High confidence

Axios: DoS & Header Injection via Prototype Pollution Read-Side Gadgets in axios merge functions

axios · axios

Official source article: GitHub GHSA-898C-Q2CR-XWHG ↗. Check the applicable product and release in the original source.

4.8MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 101 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 11 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.33% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs axios axios and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 101 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-axiosAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · sourcenode-axiosAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian forkyforky · sourcenode-axiosVendor fix publishedDebian records a fixed source-package version for this release.1.16.0-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · sourcenode-axiosVendor fix publishedDebian records a fixed source-package version for this release.1.16.0-1Debian Security Tracker ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · esm-appsnode-axiosUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 4 Nov 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmaxios>= 1.0.0, < 1.16.01.16.0GitHub advisory ↗upstream repository advisory · 12 Jun 2026
npmaxios<= 0.31.10.32.0GitHub advisory ↗upstream repository advisory · 12 Jun 2026
npmaxiosSEMVER: introduced 1.0.0; fixed 1.16.01.16.0OSV record ↗aggregator derived · 10 Sep 2026
npmaxiosSEMVER: introduced 0; fixed 0.32.00.32.0OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-44490 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityaxios: Axios: Information disclosure and denial of service due to prototype pollution
99 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • axios as a component of Cryostat 4
  • cryostat-openshift-console-plugin-npm as a component of Cryostat 4
  • gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3
  • mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8
  • mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8
  • rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers
  • multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes
  • network-observability/network-observability-console-plugin-pf4-rhel9 as a component of Network Observability Operator
  • network-observability/network-observability-console-plugin-pf5-rhel9 as a component of Network Observability Operator
  • network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator
  • openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines
  • openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines
Summary
A flaw was found in Axios, a promise-based HTTP client. This vulnerability, known as prototype pollution, allows an upstream dependency to modify the fundamental behavior of JavaScript objects. When this occurs, Axios can unknowingly incorporate these altered values, leading to two potential consequences. This can result in sensitive information being inadvertently included in network requests, or cause application instability and crashes, leading to a denial of service.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-36260

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 101 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487), axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 1.16.0.

What

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487), axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 1.16.0.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487), axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 1.16.0.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-1321 ↗

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-1321Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3307IBM MQ Appliance (Axios Node.js): Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM MQ Appliance ausnutzen, um beliebigen Programmcode auszuführen, Server-Side Request Forgery (SSRF) durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2923Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye, und Jira): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2460Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Avis du CERT-FR

d?id=CVE-2026-43828 Référence CVE CVE-2026-43871 https://www.cve.org/CVERecord?id=CVE-2026-43871 Référence CVE CVE-2026-43951 https://www.cve.org/CVERecord?id=CVE-2026-43951 Référence CVE CVE-2026-44119 https://www.cve.org/CVERecord?id=CVE-2026-44119 Référence CVE CVE-2026-44185 https://www.cve.org/CVERecord?id=CVE-2026-44185 Référence CVE CVE-2026-44186 https://www.cve.org/CVERecord?id=CVE-2026-44186 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=CVE-2026-44492 Référence CVE CVE-2026-44494 https://www.cve.org/CVERecord?id=CVE-2026-44494 Référence CVE CVE-2026-44495 https://www.cve.org/CVERecord?id=CVE-2026-44495 Référence CVE CVE-2026-44496 https://www.cve.org/CVERecord?id=CVE-2026-44496 Référence CVE CVE-2026-44572 https://www.cve.org/CVERecord?id=CVE-2026-44572 Référence CVE CVE-2026-44573 https://www.cve.org/CVERecord?id=CVE-2026-44573 Référence CVE CVE-2026-44576 https://www.cve.org/CVERecord?id=CVE-2026-44576 Référence CVE CVE-2026-44577 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-43827 Référence CVE CVE-2026-43828 https://www.cve.org/CVERecord?id=CVE-2026-43828 Référence CVE CVE-2026-43868 https://www.cve.org/CVERecord?id=CVE-2026-43868 Référence CVE CVE-2026-4410 https://www.cve.org/CVERecord?id=CVE-2026-4410 Référence CVE CVE-2026-44248 https://www.cve.org/CVERecord?id=CVE-2026-44248 Référence CVE CVE-2026-44249 https://www.cve.org/CVERecord?id=CVE-2026-44249 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=CVE-2026-44492 Référence CVE CVE-2026-44494 https://www.cve.org/CVERecord?id=CVE-2026-44494 Référence CVE CVE-2026-44495 https://www.cve.org/CVERecord?id=CVE-2026-44495 Référence CVE CVE-2026-44496 https://www.cve.org/CVERecord?id=CVE-2026-44496 Référence CVE CVE-2026-44598 https://www.cve.org/CVERecord?id=CVE-2026-44598 Référence CVE CVE-2026-45205 https://www.cve.org/CVERecord?id=CVE-2026-45205 Référence CVE CVE-2026-45416 https://www.cve.org/CVERecord?id=CVE-2026-45416 Référence CVE CVE-2026-45623 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-44293 Référence CVE CVE-2026-44294 https://www.cve.org/CVERecord?id=CVE-2026-44294 Référence CVE CVE-2026-44405 https://www.cve.org/CVERecord?id=CVE-2026-44405 Référence CVE CVE-2026-44417 https://www.cve.org/CVERecord?id=CVE-2026-44417 Référence CVE CVE-2026-44431 https://www.cve.org/CVERecord?id=CVE-2026-44431 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44489 https://www.cve.org/CVERecord?id=CVE-2026-44489 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=CVE-2026-44492 Référence CVE CVE-2026-44494 https://www.cve.org/CVERecord?id=CVE-2026-44494 Référence CVE CVE-2026-44496 https://www.cve.org/CVERecord?id=CVE-2026-44496 Référence CVE CVE-2026-44618 https://www.cve.org/CVERecord?id=CVE-2026-44618 Référence CVE CVE-2026-44728 https://www.cve.org/CVERecord?id=CVE-2026-44728 Référence CVE CVE-2026-44930 https://www.cve.org/CVERecord?id=CVE-2026-44930 Référence CVE CVE-2026-44990 https://www.cve.org/CVERecord?id=CVE-2026-44990 Référence CVE CVE-2026-45149 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-44024 Référence CVE CVE-2026-44025 https://www.cve.org/CVERecord?id=CVE-2026-44025 Référence CVE CVE-2026-44160 https://www.cve.org/CVERecord?id=CVE-2026-44160 Référence CVE CVE-2026-44161 https://www.cve.org/CVERecord?id=CVE-2026-44161 Référence CVE CVE-2026-4424 https://www.cve.org/CVERecord?id=CVE-2026-4424 Référence CVE CVE-2026-44431 https://www.cve.org/CVERecord?id=CVE-2026-44431 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=CVE-2026-44492 Référence CVE CVE-2026-44494 https://www.cve.org/CVERecord?id=CVE-2026-44494 Référence CVE CVE-2026-44495 https://www.cve.org/CVERecord?id=CVE-2026-44495 Référence CVE CVE-2026-44496 https://www.cve.org/CVERecord?id=CVE-2026-44496 Référence CVE CVE-2026-44930 https://www.cve.org/CVERecord?id=CVE-2026-44930 Référence CVE CVE-2026-4519 https://www.cve.org/CVERecord?id=CVE-2026-4519 Référence CVE CVE-2026-45292 https://www.cve.org/CVERecord?id=CVE-2026-45292 Référence CVE CVE-2026-45505 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0934Multiples vulnérabilités dans les produits Atlassian

d?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-42264 https://www.cve.org/CVERecord?id=CVE-2026-42264 Référence CVE CVE-2026-42581 https://www.cve.org/CVERecord?id=CVE-2026-42581 Référence CVE CVE-2026-42583 https://www.cve.org/CVERecord?id=CVE-2026-42583 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=CVE-2026-44492 Référence CVE CVE-2026-44494 https://www.cve.org/CVERecord?id=CVE-2026-44494 Référence CVE CVE-2026-44495 https://www.cve.org/CVERecord?id=CVE-2026-44495 Référence CVE CVE-2026-44496 https://www.cve.org/CVERecord?id=CVE-2026-44496 Référence CVE CVE-2026-44705 https://www.cve.org/CVERecord?id=CVE-2026-44705 Référence CVE CVE-2026-46625 https://www.cve.org/CVERecord?id=CVE-2026-46625 Référence CVE CVE-2026-47838 https://www.cve.org/CVERecord?id=CVE-2026-47838 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=C

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019866axios projectのaxiosにおけるオブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性

AxiosはブラウザとNode.js向けのPromiseベースのHTTPクライアントであり、特定のバージョンにプロトタイプ汚染の脆弱性が存在します。この問題により、悪意のある依存関係を通じてObject.prototypeが汚染されると、axiosの設定やヘッダーに不正な値が含まれ、通信に影響を与える可能性があります。また、汚染されたプロパティにアクセスするとTypeErrorが発生することもあります。この脆弱性はバージョン0.32.0および1.16.0で修正されました。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0325Kwetsbaarheden verholpen in Atlassian producten

Axios versions prior to 1.16.0, including 1.15.2 and earlier, are vulnerable to prototype pollution that enables arbitrary HTTP header injection, sensitive data leakage, and denial-of-service crashes due to unsafe merging of object properties.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official vendor articles2 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 11 Jun 2026 · Last source change 11 Jun 2026, 17:23 UTC · CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-36260
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    axios as a component of Cryostat 4; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; network-observability/network-observability-console-plugin-pf4-rhel9 as a component of Network Observability Operator; network-observability/network-observability-console-plugin-pf5-rhel9 as a component of Network Observability Operator; network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/kiali-operator-bundle as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9-operator as a component of OpenShift Service Mesh 3; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; rhacm2/console-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 4; axios as a component of Red Hat AMQ Broker 7; ansible-automation-platform-26/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; and 67 more
    After
    axios as a component of Cryostat 4; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; network-observability/network-observability-console-plugin-pf4-rhel9 as a component of Network Observability Operator; network-observability/network-observability-console-plugin-pf5-rhel9 as a component of Network Observability Operator; network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/kiali-operator-bundle as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9-operator as a component of OpenShift Service Mesh 3; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; rhacm2/console-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 4; axios as a component of Red Hat AMQ Broker 7; ansible-automation-platform-26/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; and 69 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-44490 · cve.blacktree.nl