Home / Security / Advisories / NTAP-20261021-0015

NTAP-20261021-0015 — CVE-2025-49128 Jackson-Core Vulnerability in NetApp Products

Published 2026-10-21 · Updated 2026-10-21 · Status: Interim · Exploitation: Public · Severity: MEDIUM 4.0 · ONTAP affected: Yes

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

Product family: NetApp Console / BlueXP · SolidFire / NetApp HCI · ONTAP · SnapCenter  |  ONTAP-relevant  |  highest CVSS: 4.0

CVEs in this advisory

What the CVE records say

CVE-2025-49128 — Jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. Starting in version 2.0.0 and prior to version 2.13.0, a flaw in jackson-core's `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible information disclosure in systems using pooled or reused buffers, like Netty or Vert.x. This issue was silently fixed in jackson-core version 2.13.0, released on September 30, 2021, via PR #652. All users should upgrade to version 2.13.0 or later. If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.

Impact

Successful exploitation of this vulnerability could lead to disclosure of sensitive information.

Affected products

References

What to do

  1. Check the affected products listed above against the official advisory's affected-versions table — that is where the exact ONTAP 9 release, ONTAP tool, or management product versions are named.
  2. If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
  3. If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
  4. Harden in parallel: security hardening baseline and ransomware protection on ONTAP.

Related reading

Browse all ONTAP CVEs → · Security hub