CVE-2026-44290 describes a Denial of Service (DoS) vulnerability affecting protobufjs versions up to 7.5.5. This vulnerability arises from improper handling of schema option paths, allowing attackers to corrupt process-wide JavaScript constructors. Successful exploitation can lead to a persistent denial of service, impacting the application's functionality and potentially affecting other processes.
影響と攻撃シナリオ翻訳中…
The core of this vulnerability lies in protobufjs's option handling mechanism. When processing protobuf schemas or JSON descriptors, the parser incorrectly traverses inherited object properties. A malicious actor can craft a schema or descriptor that exploits this flaw, causing the parser to write to properties on global JavaScript constructors, such as Object, Array, or String. This corruption effectively breaks the fundamental building blocks of the JavaScript runtime, leading to unpredictable behavior and application crashes. The impact is persistent; the corruption remains until the process is restarted, resulting in a prolonged denial of service. This differs from transient DoS attacks as it requires no ongoing exploitation.
悪用の状況翻訳中…
CVE-2026-44290 was published on 2026-05-12. The vulnerability's severity is rated as HIGH (CVSS 7.5). Currently, there are no publicly available Proof-of-Concept (POC) exploits. The vulnerability is not listed on KEV or EPSS, indicating a low to medium probability of active exploitation at this time. Monitor security advisories and threat intelligence feeds for any updates regarding exploitation attempts.
脅威インテリジェンス
エクスプロイト状況
CVSS ベクトル
これらのメトリクスの意味は?
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- なし — 認証不要。資格情報なしで悪用可能。
- User Interaction
- なし — 自動かつ無音の攻撃。被害者は何もしない。
- Scope
- 変化なし — 影響は脆弱なコンポーネントのみ。
- Confidentiality
- なし — 機密性への影響なし。
- Integrity
- なし — 完全性への影響なし。
- Availability
- 高 — 完全なクラッシュまたはリソース枯渇。完全なサービス拒否。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 公開日
緩和策と回避策翻訳中…
The primary mitigation for CVE-2026-44290 is to upgrade to a patched version of protobufjs. While a specific fixed version is not yet available, monitoring the project's release notes is crucial. In the interim, implement strict schema validation to prevent the parsing of untrusted or potentially malicious protobuf schemas and JSON descriptors. This can involve whitelisting allowed schema structures or using a schema validation library. Consider implementing a Web Application Firewall (WAF) or proxy to inspect and filter incoming protobuf data, blocking requests containing suspicious schema constructs. Carefully review any third-party libraries or components that utilize protobufjs and ensure they are not vulnerable to this issue.
修正方法翻訳中…
公式パッチはありません。回避策を確認するか、アップデートを監視してください。
よくある質問翻訳中…
What is CVE-2026-44290 — DoS in protobufjs?
CVE-2026-44290 is a high-severity Denial of Service vulnerability in protobufjs versions up to 7.5.5. A crafted protobuf schema can corrupt JavaScript constructors, leading to application crashes and a persistent denial of service.
Am I affected by CVE-2026-44290 in protobufjs?
You are affected if you are using protobufjs versions 7.5.5 or earlier. Review your project dependencies to determine if you are using a vulnerable version.
How do I fix CVE-2026-44290 in protobufjs?
Upgrade to a patched version of protobufjs as soon as it becomes available. In the meantime, implement strict schema validation and consider WAF rules to filter malicious protobuf data.
Is CVE-2026-44290 being actively exploited?
Currently, there are no publicly known exploits or reports of active exploitation. However, the vulnerability's severity warrants immediate attention and mitigation.
Where can I find the official protobufjs advisory for CVE-2026-44290?
Refer to the protobufjs project's official website and GitHub repository for updates and advisories related to CVE-2026-44290: https://protobufjs.org/
今すぐ試す — アカウント不要
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.
依存関係ファイルをドラッグ&ドロップ
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...