← Back
CVE-2026-44291
high
CVSS 8.1
Vulnerability in protobufjs (CVE-2026-44291)
Summary
vulnerability in protobufjs (CVE-2026-44291). Successful exploitation can lead to full system takeover. Exploitable via ``Object.prototype``. Mitigation: upgrade to `8.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44291** has been found in protobufjs.
Attackers can target a specific entry point like ``Object.prototype`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade protobufjs to **8.0.2** or later.
If unsure, ask your IT team or search "protobufjs CVE-2026-44291" on the vendor's site.
CVE-2026-44291 (protobufjs) — CWE-1321 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Object.prototype`
Patched: `8.0.2` — apply immediately
Workaround: Avoid running affected versions in applications where attacker-controlled input can pollute `Object.prototype`.
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-1321) exists in protobufjs. Attackers reach the vulnerable code path via ``Object.prototype`` without authentication.
📍 Affected scope
protobufjs — . Attack surface: `Object.prototype`.
🔥 Severity
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **8.0.2**.
🛡️ Workaround
Workaround: Avoid running affected versions in applications where attacker-controlled input can pollute `Object.prototype`.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Avoid running affected versions in applications where attacker-controlled input can pollute `Object.prototype`.パッチが適用されるまでの応急処置として、Avoid running affected versions in applications where attacker-controlled input can pollute `Object.prototype`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade protobufjs to 8.0.2ステージング環境で 8.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
protobufjs
[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.0.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44291
- package https://github.com/protobufjs/protobuf.js
- web https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-75px-5xx7-5xc7
- web https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.5.6
- web https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.0.2
- web https://github.com/advisories/GHSA-75px-5xx7-5xc7