⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.5

How to Fix CVE-2026-42044: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

Last verified: 2026-05-25

CVE-2026-42044 is a cwe-915: improperly controlled modification of dynamically-determined object attributes in axios axios. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance
SeverityCVSS 6.5 - Medium
Actively exploited?Not currently in the CISA KEV catalog
Affectedaxios >= 1.0.0, < 1.15.2
Fixed inSee vendor advisory
Type (CWE)CWE-915: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes

What is CVE-2026-42044?

CVE-2026-42044 is a cwe-915: improperly controlled modification of dynamically-determined object attributes flaw in axios axios. It carries a CVSS base score of 6.5 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: Axios is a promise based HTTP client for the browser and Node.js. From 1.0.0 to before 1.15.2, he Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution in the application's dependency tree to be escalated into surgical, invisible modification of all JSON API responses , including privilege escalation, balance manipulation, and authorization bypass. The default transformResponse function at lib/defaults/index.js:124 calls JSON.parse(data, this.parseReviver), where this is the merged config object. Because parseReviver is not present in Axios defaults, not validated by assertOptions, and not subject to any constraints, a polluted Object.prototype.parseReviver function is called for every key-value pair in every JSON response, allowing the attacker to selectively modify individual values while leaving the rest of the response intact.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of axios matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-42044

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for axios.

macOS update


softwareupdate --list
sudo softwareupdate -i -a -R
sw_vers -productVersion

After applying the patch

  1. Restart the service or device so the patched binary loads.
  2. Confirm the running version matches the Fixed in row using the verification command below.
  3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-42044 being exploited in the wild?

As of 2026-05-25, CVE-2026-42044 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-42044?

The CVSS base score is 6.5 (Medium).

What version fixes this?

The vendor advisory names the patched build. See the References section.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*