CVE-2026-44288: CWE-176: Improper Handling of Unicode Encoding in protobufjs protobuf.js
protobuf.js versions prior to 7.5.6 and between 8.0.0 and 8.0.2 contain a vulnerability in their UTF-8 decoding implementation. The minimal UTF-8 decoder accepted overlong UTF-8 byte sequences and decoded them to canonical characters instead of replacing them. This behavior may allow an attacker to bypass application-level checks that inspect raw bytes before protobuf string decoding.
AI Analysis
Technical Summary
protobuf.js, a JavaScript library for compiling protobuf definitions, included a minimal UTF-8 decoder that improperly handled overlong UTF-8 byte sequences by decoding them to their canonical characters rather than rejecting or replacing them. This improper handling (CWE-176) could allow an attacker who controls protobuf binary input to bypass application-level byte inspections that occur before string decoding, potentially causing the application to accept strings containing characters that were not present in the raw byte stream. The issue affects protobuf.js versions before 7.5.6 and versions from 8.0.0 up to but not including 8.0.2. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity) with network attack vector, low attack complexity, no privileges or user interaction required, and impacts integrity but not confidentiality or availability. No known exploits are reported in the wild. The vulnerability is fixed in protobuf.js versions 7.5.6 and 8.0.2.
Potential Impact
This vulnerability allows an attacker who can supply protobuf binary data to bypass application-level checks that inspect raw bytes before protobuf string decoding. This could lead to integrity issues where the application processes strings containing unexpected characters, potentially affecting application logic or security controls relying on raw byte inspection. There is no impact on confidentiality or availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Upgrading protobuf.js to version 7.5.6 or later (for the 7.x series) or to version 8.0.2 or later (for the 8.x series) resolves this vulnerability. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is fixed in these versions. Users should update to these fixed versions to mitigate the risk. No additional mitigation steps are indicated.
CVE-2026-44288: CWE-176: Improper Handling of Unicode Encoding in protobufjs protobuf.js
Description
protobuf.js versions prior to 7.5.6 and between 8.0.0 and 8.0.2 contain a vulnerability in their UTF-8 decoding implementation. The minimal UTF-8 decoder accepted overlong UTF-8 byte sequences and decoded them to canonical characters instead of replacing them. This behavior may allow an attacker to bypass application-level checks that inspect raw bytes before protobuf string decoding.
CVSS v3.1
Score 5.3medium
Affected software
pkg:npm/protobufjs/protobuf.jsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
protobuf.js, a JavaScript library for compiling protobuf definitions, included a minimal UTF-8 decoder that improperly handled overlong UTF-8 byte sequences by decoding them to their canonical characters rather than rejecting or replacing them. This improper handling (CWE-176) could allow an attacker who controls protobuf binary input to bypass application-level byte inspections that occur before string decoding, potentially causing the application to accept strings containing characters that were not present in the raw byte stream. The issue affects protobuf.js versions before 7.5.6 and versions from 8.0.0 up to but not including 8.0.2. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity) with network attack vector, low attack complexity, no privileges or user interaction required, and impacts integrity but not confidentiality or availability. No known exploits are reported in the wild. The vulnerability is fixed in protobuf.js versions 7.5.6 and 8.0.2.
Potential Impact
This vulnerability allows an attacker who can supply protobuf binary data to bypass application-level checks that inspect raw bytes before protobuf string decoding. This could lead to integrity issues where the application processes strings containing unexpected characters, potentially affecting application logic or security controls relying on raw byte inspection. There is no impact on confidentiality or availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Upgrading protobuf.js to version 7.5.6 or later (for the 7.x series) or to version 8.0.2 or later (for the 8.x series) resolves this vulnerability. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is fixed in these versions. Users should update to these fixed versions to mitigate the risk. No additional mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-05T17:39:31.112Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a049717cbff5d8610e00324
Added to database: 05/13/2026, 15:21:59 UTC
Last enriched: 05/20/2026, 19:10:14 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 77
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.