Vulnerability · CVE-2026-104016
ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _inputEnd and then, on the fast path, calling _finishShortText(len).
Published Oct 28, 2026 · catalog updated Nov 2, 2026 · ProtobufParser parses length-prefixed protobuf
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-104016. EPSS is 0.68%. Act only if a listed version of ProtobufParser parses length-prefixed protobuf is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (ProtobufParser parses length-prefixed protobuf).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.68%
- Remediation
- Advisory link
- Affected products
- Debian:14 jackson-dataformats-binary
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Debian:14 jackson-dataformats-binary0 → 2.22.4-1
How to fix CVE-2026-104016
Upgrade
CVE-2026-104016 lists a fix boundary at 2.22.4-1. Compare the installed build with that boundary before you change production.
Version check
Fixed in 2.22.4-1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-104016. EPSS is 0.68%. Act only if a listed version of ProtobufParser parses length-prefixed protobuf is installed.
Which versions are affected?
Compare what you have installed with 0 → 2.22.4-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.68%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 28, 2026 · Tenable CVE Database
Detected
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) reache
Nov 2, 2026 · OpenSSF OSV / OSV Scanner
Fix available
jackson-dataformats-binary fixed in 2.22.4-1
Nov 2, 2026 · OpenSSF OSV / OSV Scanner
Fix available
jackson-dataformats-binary fixed in 2.22.4-1
Nov 2, 2026 · OpenSSF OSV / OSV Scanner
Updated
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) reache
Sources
- CVE.orgVulnerability recordCVE-2026-104016
Official CVE identifier
cve.org - OpenSSF OSV / OSV ScannerPackage advisoryDEBIAN-CVE-2026-104016osv.dev
- Tenable CVE DatabaseVulnerability recordCVE-2026-104016
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) reache
tenable.com
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- OpenSSF OSV / OSV ScannerNov 2, 2026
- CVE.orgOct 28, 2026
- Tenable CVE DatabaseOct 28, 2026