Home / Security / Advisories / NTAP-20261014-0011

NTAP-20261014-0011 — CVE-2026-49844 IBM Db2 Vulnerability in NetApp Products

Published 2026-10-14 · Updated 2026-10-14 · Status: Interim · Exploitation: Public · Severity: MEDIUM 5.9 · ONTAP affected: No — other NetApp product

Official advisory: NTAP-20261014-0011 on security.netapp.com ↗. Affected versions, fixed releases, and workarounds live there — this page is a summary.

Product family: OnCommand family | other NetApp product | highest CVSS: 5.9

CVEs in this advisory

CVE-2026-49844 — MEDIUM · CVSS 5.9 · site index

What the CVE records say

CVE-2026-49844 — Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0. The fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity), MapMessage.asJson() emits the corresponding bare token. RFC 8259 does not permit these tokens, so a conformant parser rejects the resulting document. The defect is reachable only when both of the following conditions hold: * The application uses the message resolver https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message of JsonTemplateLayout or any other layout that relies on MapMessage.asJson() or MapMessage.getFormattedMessage(new String[]{"JSON"}). * The application logs a MapMessage that contains an attacker-controlled floating-point value. An attacker who can supply a non-finite value can cause the affected layout to emit malformed JSON, which may corrupt the enclosing log record or disrupt downstream log ingestion and parsing. Users are advised to upgrade to Apache Log4j API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values.

Impact

Successful exploitation of this vulnerability could lead to addition or modification of data.

Affected products

OnCommand Insight

References

https://www.ibm.com/support/pages/node/7291607 ↗

What to do

Compare your installed product and version against the affected list above and the official advisory's affected-versions table.
Apply the fixed release named in the official advisory, or the documented workaround if no fix ships yet.
Limit management-plane exposure (BMC/management interfaces, web UIs, SNMP) until patched.
Track follow-ups in the site CVE index and the security RSS feed.