CVE-2026-29063: Immutable.js provides many Persistent Immutable data structures

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADEDOWNGRADEUPGRADE

CVE-2026-29063 is a critical-severity flaw (CVSS 9.8) affecting immutable, 3scale api management platform, advanced cluster management for kubernetes. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Immutable.js provides many Persistent Immutable data structures. Prior to versions 3.8.3, 4.3.7, and 5.1.5, Prototype Pollution is possible in immutable via the mergeDeep(), mergeDeepWith(), merge(), Map.toJS(), and Map.toObject() APIs. This issue has been patched in versions 3.8.3, 4.3.7, and 5.1.5.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-1321, CWE-915
Published	2026-03-06
Last modified	2026-10-30

Publisher (CNA): GitHub, Inc. · Vendor: immutable-js · redhat

Last updated 2026-10-30 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-06 19:16 UTCPublished CVE record published
2026-10-30 13:16 UTCUpdated Record last modified

immutable-js immutable UPGRADE

Affected: >= 3.0.0 and < 3.8.3 · >= 4.0.0 and < 4.3.8 · >= 5.0.0 and < 5.1.5

Fixed in: 3.8.3, 4.3.8, 5.1.5

Safe to downgrade to: a release before 3.0.0

1. Check installed version

npm ls immutable

2. UPGRADE to 3.8.3

npm install immutable@">=3.8.3"

3. If no update is available yet, DOWNGRADE to a release before 3.0.0

npm view immutable versions npm install immutable@"<3.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat 3scale api management platform DOWNGRADE

Affected: 2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy 3scale-api-management-platform || rpm -q 3scale-api-management-platform || 3scale-api-management-platform --version

2. No fixed release: DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison 3scale-api-management-platform sudo apt install 3scale-api-management-platform=<VERSION_BEFORE_2.0> sudo apt-mark hold 3scale-api-management-platform

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list 3scale-api-management-platform sudo dnf downgrade 3scale-api-management-platform-<VERSION_BEFORE_2.0> sudo dnf versionlock add 3scale-api-management-platform

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat advanced cluster management for kubernetes UPGRADE

Affected: >= 2.14 and < 2.14.3 · >= 2.15 and < 2.15.2 · >= 2.16 and < 2.16.1

Fixed in: 2.14.3, 2.15.2, 2.16.1

Safe to downgrade to: a release before 2.14

1. Check installed version

apt-cache policy advanced-cluster-management-for-kubernetes || rpm -q advanced-cluster-management-for-kubernetes || advanced-cluster-management-for-kubernetes --version

2. UPGRADE to 2.14.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade advanced-cluster-management-for-kubernetes

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade advanced-cluster-management-for-kubernetes

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.14 (Debian / Ubuntu)

apt-cache madison advanced-cluster-management-for-kubernetes sudo apt install advanced-cluster-management-for-kubernetes=<VERSION_BEFORE_2.14> sudo apt-mark hold advanced-cluster-management-for-kubernetes

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list advanced-cluster-management-for-kubernetes sudo dnf downgrade advanced-cluster-management-for-kubernetes-<VERSION_BEFORE_2.14> sudo dnf versionlock add advanced-cluster-management-for-kubernetes

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat advanced cluster security UPGRADE

Affected: >= 4.8.0 and < 4.8.11 · >= 4.9.0 and < 4.9.6

Fixed in: 4.8.11, 4.9.6

Safe to downgrade to: a release before 4.8.0

1. Check installed version

apt-cache policy advanced-cluster-security || rpm -q advanced-cluster-security || advanced-cluster-security --version

2. UPGRADE to 4.8.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade advanced-cluster-security

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade advanced-cluster-security

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.8.0 (Debian / Ubuntu)

apt-cache madison advanced-cluster-security sudo apt install advanced-cluster-security=<VERSION_BEFORE_4.8.0> sudo apt-mark hold advanced-cluster-security

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list advanced-cluster-security sudo dnf downgrade advanced-cluster-security-<VERSION_BEFORE_4.8.0> sudo dnf versionlock add advanced-cluster-security

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat advanced cluster security UPGRADE

Affected: >= 4.10.0 and < 4.10.2

Fixed in: 4.10.2

Safe to downgrade to: a release before 4.10.0

1. Check installed version

apt-cache policy advanced-cluster-security || rpm -q advanced-cluster-security || advanced-cluster-security --version

2. UPGRADE to 4.10.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade advanced-cluster-security

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade advanced-cluster-security

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.10.0 (Debian / Ubuntu)

apt-cache madison advanced-cluster-security sudo apt install advanced-cluster-security=<VERSION_BEFORE_4.10.0> sudo apt-mark hold advanced-cluster-security

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list advanced-cluster-security sudo dnf downgrade advanced-cluster-security-<VERSION_BEFORE_4.10.0> sudo dnf versionlock add advanced-cluster-security

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat ansible automation platform DOWNGRADE

Affected: 2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy ansible-automation-platform || rpm -q ansible-automation-platform || ansible-automation-platform --version

2. No fixed release: DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison ansible-automation-platform sudo apt install ansible-automation-platform=<VERSION_BEFORE_2.0> sudo apt-mark hold ansible-automation-platform

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ansible-automation-platform sudo dnf downgrade ansible-automation-platform-<VERSION_BEFORE_2.0> sudo dnf versionlock add ansible-automation-platform

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.

npm · immutable · FIXED · 5.1.5 · vulnerable: >= 5.0.0, < 5.1.5 · source

npm install immutable@">=5.1.5" npm ls immutable

Fedora 46 · conan · FIXED · 2.31.0-1.fc46 · FEDORA-2026-ba58084ab5 · source

sudo dnf upgrade --advisory=FEDORA-2026-ba58084ab5

Fedora ELN · tesseract · FIXED · 5.5.4-1.eln159 · FEDORA-2026-866cf60ee6 · source

sudo dnf upgrade --advisory=FEDORA-2026-866cf60ee6

Debian 12 · node-immutable · NO FIX YET

Debian 13 · node-immutable · NO FIX YET

RHEL 10 · grafana · NO FIX YET

RHEL 8 · grafana · NOT AFFECTED

RHEL 8 · mozjs60 · NOT AFFECTED

RHEL 8 · pcs · NOT AFFECTED

RHEL 9 · gjs · DEFERRED

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Write-up: github.com/immutable-js/immutable-js/security/advisories/GHSA-wf6x-7x77-mvgw

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-29063?

immutable: upgrade to 3.8.3, 4.3.8, 5.1.5; 3scale api management platform: downgrade or apply the listed mitigation; advanced cluster management for kubernetes: upgrade to 2.14.3, 2.15.2, 2.16.1. Exact commands for each OS are on this page.

Is CVE-2026-29063 being exploited?

CVE-2026-29063 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-29063 affect?

CVE-2026-29063 affects immutable, 3scale api management platform, advanced cluster management for kubernetes. Severity is critical (CVSS 9.8). Immutable.js provides many Persistent Immutable data structures. Prior to versions 3.8.3, 4.3.7, and 5.1.5, Prototype Pollution is possible in immutable via the mergeDeep(), mergeDeepWith(), merge(), Map.toJS(), and Map.toObject() APIs. Thi

How urgent is CVE-2026-29063?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Kubernetes vulnerabilities · Ansible vulnerabilities

Related CVEs

CVE-2026-59880 HIGH 7.5 UPGRADE Immutable.js provides many Persistent Immutable data structures
CVE-2026-59879 HIGH 7.5 UPGRADE Immutable.js provides many Persistent Immutable data structures

References

← Back to latest CVEs