分析待ちCVE-2026-44295

CVE-2026-44295: Code Injection in protobuf.js 2.x

プラットフォーム

nodejs

コンポーネント

protobufjs

修正版

2.0.2

CVE-2026-44295 affects versions 2.0.0 through 2.0.1 of protobuf.js, a JavaScript library for encoding and decoding data structures. This vulnerability allows an attacker to inject malicious JavaScript code by crafting a malicious schema or JSON descriptor. The vulnerability is fixed in version 2.0.2 and users are strongly advised to upgrade immediately to prevent potential code execution.

影響と攻撃シナリオ翻訳中…

The core of this vulnerability lies in the static code generation process within protobuf.js. When generating JavaScript code from a protobuf schema, the library fails to adequately sanitize names used for namespaces, enums, services, and derived types. An attacker can craft a malicious schema containing specially crafted names that, when processed by pbjs, result in the generation of JavaScript code containing arbitrary commands. This injected code could then be executed within the context of the application using protobuf.js, potentially leading to complete compromise of the system. The blast radius extends to any application relying on this library for data serialization, particularly those handling untrusted input.

悪用の状況翻訳中…

This vulnerability was published on 2026-05-13. Currently, there are no publicly available exploits or active campaigns targeting this vulnerability. Its severity is rated HIGH (CVSS: 8.7), indicating a significant risk. The vulnerability is not currently listed on KEV or EPSS, suggesting a low to medium probability of exploitation in the near term, but proactive patching is still highly recommended.

脅威インテリジェンス

エクスプロイト状況

概念実証不明
CISA KEVNO
インターネット露出

CISA SSVC

悪用状況none
自動化可能no
技術的影響total

CVSS ベクトル

脅威インテリジェンス· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N8.7HIGHAttack VectorNetwork攻撃者がターゲットに到達する方法Attack ComplexityLow悪用に必要な条件Privileges RequiredLow攻撃に必要な認証レベルUser InteractionRequired被害者の操作が必要かどうかScopeChanged影響コンポーネント外への波及ConfidentialityHigh機密データ漏洩のリスクIntegrityHigh不正データ改ざんのリスクAvailabilityNoneサービス障害のリスクnextguardhq.com · CVSS v3.1 基本スコア
これらのメトリクスの意味は?
Attack Vector
ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
Attack Complexity
低 — 特別な条件不要。安定して悪用可能。
Privileges Required
低 — 有効なユーザーアカウントがあれば十分。
User Interaction
必要 — 被害者がファイルを開く、リンクをクリックするなどのアクションが必要。
Scope
変化あり — 攻撃が脆弱なコンポーネントを超えて他のシステムに波及可能。
Confidentiality
高 — 機密性の完全喪失。全データが読み取り可能。
Integrity
高 — 任意のデータの書き込み・変更・削除が可能。
Availability
なし — 可用性への影響なし。

影響を受けるソフトウェア

コンポーネントprotobufjs
ベンダーprotobufjs
最小バージョン2.0.0
最大バージョン>= 2.0.0, < 2.0.2
修正版2.0.2

弱点分類 (CWE)

タイムライン

  1. 予約済み
  2. 公開日

緩和策と回避策翻訳中…

The primary mitigation is to upgrade to protobuf.js version 2.0.2 or later, which includes the necessary sanitization fixes. If upgrading is not immediately feasible, consider implementing input validation on protobuf schemas before processing them with pbjs. This could involve whitelisting allowed characters or patterns in names. As a temporary workaround, consider using a Web Application Firewall (WAF) to filter requests containing potentially malicious protobuf schemas. While not a complete solution, it can provide an additional layer of defense. After upgrading, confirm the fix by generating code from a known malicious schema and verifying that the generated JavaScript does not contain the injected code.

修正方法翻訳中…

Actualice la biblioteca protobuf.js a la versión 2.0.2 o superior, o a la versión 1.2.1 o superior si está utilizando una versión anterior a 2.0.0. Esto solucionará la vulnerabilidad de inyección de código al sanear correctamente los nombres de los esquemas.

よくある質問翻訳中…

What is CVE-2026-44295 — Code Injection in protobuf.js?

CVE-2026-44295 is a HIGH severity vulnerability in protobuf.js versions 2.0.0–2.0.1 that allows attackers to inject malicious JavaScript code through crafted protobuf schemas, potentially leading to code execution.

Am I affected by CVE-2026-44295 in protobuf.js?

You are affected if you are using protobuf.js versions 2.0.0 through 2.0.1. Check your project dependencies to determine if you are using a vulnerable version.

How do I fix CVE-2026-44295 in protobuf.js?

Upgrade to protobuf.js version 2.0.2 or later to resolve this vulnerability. If upgrading is not immediately possible, implement input validation on protobuf schemas.

Is CVE-2026-44295 being actively exploited?

Currently, there are no publicly known exploits or active campaigns targeting CVE-2026-44295, but proactive patching is still recommended due to its HIGH severity.

Where can I find the official protobuf.js advisory for CVE-2026-44295?

Refer to the official protobuf.js GitHub repository for updates and advisories: https://github.com/protocolbuffers/protobufjs

あなたのプロジェクトは影響を受けていますか?

依存関係ファイルをアップロードすれば、このCVEや他のCVEがあなたに影響するか即座にわかります。

scanZone.liveBadgescanZone.eyebrow

今すぐ試す — アカウント不要

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

手動スキャンSlack/メールアラートContinuous monitoringホワイトラベルレポート

依存関係ファイルをドラッグ&ドロップ

composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...