Vulnerability in protobufjs (CVE-2026-44289)
Summary
Vulnerability in protobufjs (CVE-2026-44289). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.0.2 or later.
Original description
The description as published by the source.
Summary
protobufjs could recurse without a depth limit while decoding nested protobuf data. This affected both skipping unknown group fields and generated decoding of nested message fields.
A crafted protobuf binary payload could cause the JavaScript call stack to be exhausted during decoding.
Impact
An attacker who can provide protobuf binary data decoded by an application may be able to crash the process or otherwise cause decoding to fail with a stack overflow.
This affects applications that decode untrusted protobuf binary input with affected versions.
Preconditions
- The application must decode protobuf binary data influenced by an attacker.
- The crafted input must contain deeply nested protobuf structures, such as nested group tags or nested message fields.
- The affected decoder path must process the crafted input.
Workarounds
Avoid decoding untrusted protobuf binary data with affected versions. If immediate upgrade is not possible, reject excessively nested messages at an outer protocol boundary where feasible, or isolate protobuf decoding in a process that can be safely restarted.
Source: GitHub Security Advisories (Global) 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-44289 has been found in protobufjs.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade protobufjs to 8.0.2 or later.
If unsure, ask your IT team or search "protobufjs CVE-2026-44289" on the vendor's site.
CVE-2026-44289 (protobufjs) — CWE-674 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.0.2 — apply immediately
Workaround: Avoid decoding untrusted protobuf binary data with affected versions.
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.
A vulnerability (CWE-674) exists in protobufjs.
Check the vendor advisory for the affected versions of protobufjs.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 8.0.2.
Workaround: Avoid decoding untrusted protobuf binary data with affected versions.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'protobufjs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'protobufjs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
protobufjsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Avoid decoding untrusted protobuf binary data with affected versions.パッチが適用されるまでの応急処置として、Avoid decoding untrusted protobuf binary data with affected versions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade protobufjs to 8.0.2ステージング環境で 8.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch security-advisories@github.com
- web github.com
- web github.com
- web github.com
- web access.redhat.com
- web bugzilla.redhat.com
- web security.access.redhat.com
- web access.redhat.com
- web access.redhat.com