← Back
CVE-2026-45799 high CVSS 7.5

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

Summary

vulnerability in com.squareup.wire:wire-runtime-jvm (CVE-2026-45799). Risk of unauthorized operations or information disclosure. Exploitable via ``IOException``. Mitigation: upgrade to `7.0.0-alpha03` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-45799** has been found in com.squareup.wire:wire-runtime-jvm. Attackers can target a specific entry point like ``IOException`` 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-jvm to **7.0.0-alpha03** or later. If unsure, ask your IT team or search "com.squareup.wire:wire-runtime-jvm CVE-2026-45799" on the vendor's site.
CVE-2026-45799 (com.squareup.wire:wire-runtime-jvm) — CWE-129 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `IOException` / `ProtocolException` / `master` / `LENGTH_DELIMITED` Patched: `7.0.0-alpha03` — 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-129) exists in com.squareup.wire:wire-runtime-jvm. Attackers reach the vulnerable code path via ``IOException`` without authentication.
📍 Affected scope
com.squareup.wire:wire-runtime-jvm — . Attack surface: `IOException` / `ProtocolException` / `master` / `LENGTH_DELIMITED`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.0.0-alpha03**.
🛡️ 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. Run `grep -r 'com.squareup.wire:wire-runtime-jvm' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify
    grep -r 'com.squareup.wire:wire-runtime-jvm' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.squareup.wire:wire-runtime-jvm` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade com.squareup.wire:wire-runtime-jvm to 7.0.0-alpha03

    ステージング環境で 7.0.0-alpha03 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

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

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →