CVE-2026-104016

jackson-dataformat-protobuf: signed integer overflow in string-length paths allows unbounded array allocation and OutOfMemoryError

Published Oct 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _inputEnd and then, on the fast path, calling _finishShortText(len). Both use 32-bit signed integer arithmetic. When an attacker supplies a varint decoding to a length near Integer.MAX_VALUE, _inputPtr + len overflows to a negative value, the bounds check passes, and _finishShortText(len) reaches TextBuffer.expandCurrentSegment(len), which performs Arrays.copyOf with no cap and throws OutOfMemoryError: Requested array size exceeds VM limit.



The JVM refuses arrays larger than Integer.MAX_VALUE - 8 before consulting available heap, so -Xmx tuning does not mitigate the issue. StreamReadConstraints.maxStringLength and maxDocumentLength do not gate this path: a 33-byte payload is far below any document-length cap and the string-length check does not fire before the allocation. This was confirmed empirically against shipping artifacts with maxStringLength, maxDocumentLength and maxNestingDepth all configured.



A February 2026 hardening commit added the equivalent overflow guard to the packed-array-length and message-length paths but left the string-length call sites unguarded. No privileges or user interaction beyond the ability to submit data for parsing are required.

Analysis

AI-generated

Technical impact

A signed integer overflow in the protobuf parser’s string-length handling allows an attacker to craft a payload with a length field that, when added to the input pointer using 32‑bit arithmetic, overflows to a negative value. The bounds check mistakenly passes, and the parser attempts to allocate a text buffer of that overflowed size. The resulting OutOfMemoryError can terminate the parsing thread or the JVM, denying service to legitimate users. The flaw does not provide privilege escalation or exploit code execution.

Affected Systems

The vulnerability exists in the FasterXML jackson-dataformat-protobuf library. All releases built before the February 2026 hardening commit remain vulnerable. The issue is unaffected by StreamReadConstraints settings or other configuration options, and has been verified in shipping artifacts despite those safeguards.

Risk and Exploitability

With a CVSS score of 7.5 the severity is high, though no EPSS score is published and the flaw is not listed in the CISA KEV catalog. Attackers only need the ability to submit a malicious protobuf payload to any service that parses data with the vulnerable library. The lack of privilege or user interaction requirements, combined with the ability to trigger the error remotely, makes the risk significant for publicly exposed services.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade jackson-dataformat-protobuf to a release containing the February 2026 hardening commit that adds an overflow guard to string-length parsing.
  • If an immediate upgrade is infeasible, validate the payload size before passing it to the parser and enforce an application‑level maximum on the number of bytes that can be parsed, rejecting any payload that would require an allocation exceeding this limit.
  • Implement network or application‑layer throttling to limit the rate of requests that contain large or malformed protobuf data, and monitor logs for OutOfMemoryError events to detect ongoing exploitation attempts.

Generated by OpenCVE AI on October 28, 2026 at 01:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _inputEnd and then, on the fast path, calling _finishShortText(len). Both use 32-bit signed integer arithmetic. When an attacker supplies a varint decoding to a length near Integer.MAX_VALUE, _inputPtr + len overflows to a negative value, the bounds check passes, and _finishShortText(len) reaches TextBuffer.expandCurrentSegment(len), which performs Arrays.copyOf with no cap and throws OutOfMemoryError: Requested array size exceeds VM limit. The JVM refuses arrays larger than Integer.MAX_VALUE - 8 before consulting available heap, so -Xmx tuning does not mitigate the issue. StreamReadConstraints.maxStringLength and maxDocumentLength do not gate this path: a 33-byte payload is far below any document-length cap and the string-length check does not fire before the allocation. This was confirmed empirically against shipping artifacts with maxStringLength, maxDocumentLength and maxNestingDepth all configured. A February 2026 hardening commit added the equivalent overflow guard to the packed-array-length and message-length paths but left the string-length call sites unguarded. No privileges or user interaction beyond the ability to submit data for parsing are required.
Title jackson-dataformat-protobuf: signed integer overflow in string-length paths allows unbounded array allocation and OutOfMemoryError
Weaknesses CWE-190
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Subscriptions

No data.

Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

Sources

Status
PUBLISHED
Assigner
HeroDevs
Published
Updated
Nov 4, 2026, 8:20 PM
Reserved
Oct 1, 2026, 4:52 PM
Status
Deferred
Published
Oct 28, 2026, 12:17 AM
Modified
Nov 4, 2026, 9:17 PM
Severity
Important
Public date
Oct 27, 2026, 11:52 PM