Answer in brief
CVE-2026-63126 records a High severity (CVSS 7.5) vulnerability in Wire: Unauthenticated decoder crash via 32-bit length integer overflow in ByteArrayProtoReader32 (incomplete fix of CVE-2026-45799). The current sources do not mark it as known exploited. The current feed maps square/wire (generic), com.squareup.wire:wire-runtime (maven), com.squareup.wire:wire-runtime (maven), com.squareup.wire:wire-runtime (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps square/wire (generic), com.squareup.wire:wire-runtime (maven), com.squareup.wire:wire-runtime (maven), com.squareup.wire:wire-runtime (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| square/wiregeneric | <6.4.5 || >=7.0.0-alpha01 <7.0.0-alpha04 | 6.4.5, 7.0.0-alpha04 |
| com.squareup.wire:wire-runtimemaven | <=6.4.4 | 6.4.5 |
| com.squareup.wire:wire-runtimemaven | >=7.0.0-alpha01,<7.0.0-alpha04 | 7.0.0-alpha04 |
| com.squareup.wire:wire-runtimemaven | >=0 <6.4.5 | 6.4.5 |
| com.squareup.wire:wire-runtimemaven | >=7.0.0-alpha01 <7.0.0-alpha04 | 7.0.0-alpha04 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
Wire provides gRPC and protocol buffers for Android, Kotlin, Swift, and Java. Prior to 6.4.5 and 7.0.0-alpha04, Wire protobuf readers do not consistently validate attacker-controlled lengths against the current logical message boundary before advancing cursors, pointers, limits, slices, or allocations. In Kotlin, ProtoAdapter.decode(ByteArray) and ProtoAdapter.decode(ByteString) use ByteArrayProtoReader32.internalNextLengthDelimited(), where a positive oversized length can wrap pos + length to a negative limit and escape the existing negative-length check. Related ProtoReader, ReadBuffer.readVarint(), ReadBuffer.verifyAdditional(count:), packed-repeated, nested-message, and ProtoDecoder.decodeSizeDelimited(_:from:) paths can cross logical boundaries, perform pointer arithmetic, reserve capacity, or convert an unrepresentable size before proving the requested bytes exist. An attacker who supplies malformed protobuf bytes can cause unchecked exceptions, traps, out-of-bounds behavior, or excessive allocation, resulting in denial of service without known confidentiality, integrity, or code-execution impact. This issue is fixed in versions 6.4.5 and 7.0.0-alpha04.
Quoted source text, attributed separately from HOL analysis.