Skip to content
Fencer Vulns
high 7.5

CVE-2026-110747 json

jackson-dataformat-protobuf: integer overflow in ProtobufParser._readStringKey() allows OutOfMemoryError from an 8-byte payload

published 2026-10-28 12 d ago modified 2026-11-06 2 d ago also EUVD-2026-111531

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

ProtobufParser._readStringKey() reads the length prefix of a protobuf map entry's string key into an attacker-controlled int and then checks (_inputPtr + len) <= _inputEnd using signed arithmetic. For values near Integer.MAX_VALUE the addition overflows to a negative value and the check passes even when the input contains no key data. The parser then calls _finishShortText(len), which expands the text buffer to the declared length via TextBuffer.expandCurrentSegment and Arrays.copyOf, throwing OutOfMemoryError: Requested array size exceeds VM limit.

An 8-byte malformed message containing a map entry with a declared key length of 0x7FFFFFFF is sufficient. Configured StreamReadConstraints, including maxStringLength, maxNameLength, maxDocumentLength and maxNestingDepth, do not prevent the failure. Applications running with -XX:+ExitOnOutOfMemoryError terminate the JVM.

This is the same integer-overflow pattern addressed for other call sites in the remediation associated with CVE-2026-104016 and CVE-2026-104017; the map-key call site was corrected on the 3.x branches only, leaving the corresponding 2.x branches unguarded. Release lines 2.18, 2.19 and 2.20 do not contain _readStringKey() and are not affected by this vector. No privileges or user interaction beyond the ability to submit data for parsing are required. The 3.0 release line and 3.1.0-3.1.5 / 3.2.0-3.2.1 do not contain _readStringKey() and are therefore not affected; the method first appears in 3.1.6 and 3.2.2, mirroring its introduction at 2.21.6 on the 2.x side.

Patch / fix

  • FasterXML jackson-dataformat-protobuf 2.21.8, 2.22.4, 3.1.8, 3.2.4
  • jackson-dataformats-binary Debian 14 2.22.4-1

debian advisories DEBIAN-CVE-2026-110747

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-110747 updated cvss 7.5

com.fasterxml.jackson.dataformat/jackson-dataformat-protobuf: jackson-dataformat-protobuf: Denial of Service via integer overflow in map key parsing

  • Red Hat build of Apache Camel 4 for Quarkus 3 jackson-dataformat-protobuf 2.21.7.redhat-00001 Red Hat build of Apache Camel for Spring Boot 4 jackson-dataformat-protobuf 2.21.7.redhat-00001
    affected: workaround, no fix available
  • Red Hat Fuse 7 jackson-dataformat-protobuf 2.21.7.redhat-00001
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Build of Apache Camel 3.33.4.SP1 jackson-dataformat-protobuf 2.21.8.redhat-00001
    fixed: vendor fix RHSA-2026:91304
  • Red Hat Build of Apache Camel 3.33.4.SP1 jimfs 1.1, jna 5.8.0, bcel 6.7.0, gax 2.74.1, icu4j 78.2, joni 2.2.6, +1616 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 d ago

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • FasterXML jackson-dataformat-protobuf

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.