CVE-2026-44293: protobufjs: Code injection through bytes field defaults in generated toObject code
protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs generated JavaScript for toObject conversion could include an unsafe expression derived from a schema-controlled bytes field default value. A crafted descriptor with a non-string default value for a bytes field could cause attacker-controlled code to be emitted into the generated conversion function. This vulnerability is fixed in 7.5.6 and 8.0.2.
Security readout for executives and security teams
Plain-English summary
A malicious protobuf descriptor can make vulnerable protobuf.js versions generate and run attacker-controlled JavaScript during object conversion. Successful exploitation could compromise the application process and its data. Exposure depends on an attacker being able to influence schema or descriptor content, including a non-string default for a bytes field.
Executive priority
Prioritize remediation for internet-facing or multi-tenant services that accept externally influenced protobuf definitions. Treat other affected deployments as a scheduled high-priority upgrade. The potential impact is process-level code execution, but the documented preconditions make this less urgent than an unauthenticated, broadly exploited vulnerability.
Technical view
CVE-2026-44293 is a CWE-94 code-injection flaw in protobuf.js toObject code generation. A crafted descriptor containing a bytes field with a non-string default can place an unsafe expression into generated JavaScript. The affected ranges are below 7.5.6 and 8.0.0 through 8.0.1; fixes are available in 7.5.6 and 8.0.2.
Likely exposure
Highest risk exists where applications load, compile, or otherwise process protobuf descriptors influenced by untrusted or lower-trust users. Applications using affected versions only with fixed, trusted schemas have a reduced attack path, but should still upgrade. Dependency inventories must account for transitive and bundled copies.
Exploitation context
The CVSS 4.0 score is 7.7 with network reachability, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impacts. Attack preparation is required. The supplied sources do not identify CISA KEV listing or report active exploitation.
Researcher notes
Assessment should trace descriptor provenance, not merely protobuf message provenance. The critical condition is a schema-controlled bytes default represented as a non-string value reaching toObject JavaScript generation. The supplied record establishes the vulnerable behavior and fixed versions, but provides no evidence of exploitation in the wild or details about affected downstream products beyond referenced Red Hat advisories.
Mitigation direction
Upgrade protobuf.js versions below 7.5.6 to version 7.5.6 or later.
Upgrade protobuf.js 8.0.0 or 8.0.1 to version 8.0.2 or later.
Prevent untrusted parties from supplying or modifying protobuf schemas and descriptors.
Review applicable Red Hat advisories when protobuf.js arrives through Red Hat-packaged products.
Validation and detection
Inventory direct, transitive, bundled, and vendored protobuf.js versions across production and build environments.
Confirm no deployed instance is below 7.5.6 or within versions 8.0.0 through 8.0.1.
Identify workflows that compile descriptors or invoke generated toObject conversion logic.
Verify schema and descriptor sources are trusted, authenticated, and protected against unauthorized modification.
Rebuild and redeploy artifacts after upgrading, then confirm runtime dependency versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
16Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.