Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63126 high CVSS 7.5

Vulnerability in com.squareup.wire:wire-runtime (CVE-2026-63126)

Summary

Vulnerability in com.squareup.wire:wire-runtime (CVE-2026-63126). Risk of unauthorized operations or information disclosure. Exploitable via ProtoReader32. Mitigation: upgrade to 7.0.0-alpha04 or later.

Original description

The description as published by the source.

Wire's protobuf decoders did not consistently validate attacker-controlled length-delimited sizes against the current reader bounds before computing cursor, limit, or pointer positions.

In the Kotlin runtime, ProtoAdapter.decode(ByteArray) and ProtoAdapter.decode(ByteString) use the ProtoReader32 fast path implemented by ByteArrayProtoReader32. In ByteArrayProtoReader32.internalNextLengthDelimited(), Wire read an untrusted varint length into an Int and rejected only negative values. A length such as 2147483647 is non-negative, so it passed that check, but pos + length overflowed the signed 32-bit cursor and produced a negative limit. The following if (limit > pushedLimit) guard did not catch this because the overflowed value was negative.

That invalid limit then reached string, bytes, skip, and scalar-reading paths as an invalid byte count or invalid range. Instead of failing as a checked decode error such as IOException, malformed input could throw unchecked runtime exceptions including IllegalArgumentException and ArrayIndexOutOfBoundsException. Applications commonly treat malformed protobuf input as an expected decode failure; unchecked runtime exceptions escaping that boundary can crash request handling or the process.

The original report is a sibling of the negative-length skipped-group bug fixed as CVE-2026-45799. It is not the same bug. The length in this advisory is positive, and the overflow occurs when setting a length-delimited message…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-63126 has been found in com.squareup.wire:wire-runtime.
Attackers can target a specific entry point like ProtoReader32 over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade com.squareup.wire:wire-runtime to 7.0.0-alpha04 or later.
If unsure, ask your IT team or search "com.squareup.wire:wire-runtime CVE-2026-63126" on the vendor's site.

CVE-2026-63126 (com.squareup.wire:wire-runtime) — CWE-190 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ProtoReader32 / ByteArrayProtoReader32 / Int / limit
Patched: 7.0.0-alpha04 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-190) exists in com.squareup.wire:wire-runtime. Attackers reach the vulnerable code path via ProtoReader32 without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of com.squareup.wire:wire-runtime. Attack surface: ProtoReader32 / ByteArrayProtoReader32 / Int / limit.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.0.0-alpha04.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.squareup.wire:wire-runtime を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.squareup.wire:wire-runtime to 7.0.0-alpha04

    ステージング環境で 7.0.0-alpha04 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.squareup.wire:wire-runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-alpha04"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details