← Back
OSV-2026-987

Vulnerability in binutils (OSV-2026-987)

Summary

vulnerability in binutils (OSV-2026-987). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7e5ab72bd1d8fd5fa532bae67208e85ec4412230` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **OSV-2026-987** has been found in binutils. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade binutils to **7e5ab72bd1d8fd5fa532bae67208e85ec4412230** or later. If unsure, ask your IT team or search "binutils OSV-2026-987" on the vendor's site.
OSV-2026-987 (binutils) — Patched: `7e5ab72bd1d8fd5fa532bae67208e85ec4412230` — 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** (unclassified) exists in binutils.
📍 Affected scope
binutils — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7e5ab72bd1d8fd5fa532bae67208e85ec4412230**.
🛡️ 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 'binutils' .` 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 'binutils' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade binutils to 7e5ab72bd1d8fd5fa532bae67208e85ec4412230

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

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

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

Affected packages

OSS-Fuzz binutils
[{"repo":"git:\/\/sourceware.org\/git\/binutils-gdb.git","type":"GIT","events":[{"introduced":"e814012b2b108743e21b7ef2799310a0f4e0a86d"},{"fixed":"7e5ab72bd1d8fd5fa532bae67208e85ec4412230"},{"introduced":"9542d1b3a05477c415d870b7b652cdde75a5c8ea"}]}]

References

🍪 About cookies

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

Details →