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/
立即试用 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...