Vulnerability in protobufjs (CVE-2026-44288)
Summary
Vulnerability in protobufjs (CVE-2026-44288). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.0.2 or later.
Original description
The description as published by the source.
protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs includes a minimal UTF-8 decoder that accepted overlong UTF-8 byte sequences and decoded them to their canonical characters instead of replacing them. An attacker who can provide protobuf binary data decoded through the affected UTF-8 path may be able to bypass application-level checks that inspect raw bytes before protobuf string decoding. For example, bytes that do not contain certain ASCII characters could decode to strings containing those characters. This vulnerability is fixed in 7.5.6 and 8.0.2.
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-44288 has been found in protobufjs.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade protobufjs to 8.0.2 or later.
If unsure, ask your IT team or search "protobufjs CVE-2026-44288" on the vendor's site.
CVE-2026-44288 (protobufjs) — CWE-176 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.0.2 — apply immediately
Workaround: Avoid relying only on byte-level filtering before protobuf string decoding 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-176) exists in protobufjs.
Check the vendor advisory for the affected versions of protobufjs.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 8.0.2.
Workaround: Avoid relying only on byte-level filtering before protobuf string decoding 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 relying only on byte-level filtering before protobuf string decoding with affected versions.パッチが適用されるまでの応急処置として、Avoid relying only on byte-level filtering before protobuf string decoding 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 github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com