Live › vulnerability › CVE-2026-110747
Go to dashboardA malformed protobuf message with a map key length near Integer.MAX_VALUE overflows an integer check in ProtobufParser._readStringKey(), causing the parser to try allocating a huge buffer. The resulting OutOfMemoryError can terminate the JVM when the application runs with -XX:+ExitOnOutOfMemoryError, giving an attacker a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 01:30 UTC. All times on this page are UTC.
Applications that deserialize untrusted protobuf data with the Jackson protobuf dataformat module are exposed, since a single small message is enough to trigger the failure. The sources say the 2.x branches are unguarded for this call site, while the 3.0 line and 3.1.0-3.1.5 / 3.2.0-3.2.1 do not contain the affected method, and 2.18, 2.19 and 2.20 do not contain it either. Services that do not parse protobuf from untrusted sources can skip it.
No product ranges from the sources yet.
mvn dependency:tree output and see whether it is on the 2.x line at 2.21.6 or later, or on the 3.1.6 / 3.2.2 lines or later.-XX:+ExitOnOutOfMemoryError.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-110747")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.