Advisory

GHSA-75px-5xx7-5xc7

Also known as: CVE-2026-44291

Summary

protobuf.js: Code generation gadget after prototype pollution

Details

Summary

protobufjs used plain objects with inherited prototypes for internal type lookup tables used by generated encode and decode functions. If Object.prototype had already been polluted, those lookup tables could resolve attacker-controlled inherited properties as valid protobuf type information.

This could cause attacker-controlled strings to be emitted into generated JavaScript code.

Impact

An attacker who can first trigger a prototype pollution vulnerability may be able to influence generated protobufjs encode or decode functions in a way that can lead to arbitrary JavaScript execution.

This issue requires a separate prototype pollution primitive before protobufjs is invoked.

Applications without a reachable prototype pollution primitive are not directly exploitable through this issue alone.

Preconditions

  • The application or one of its dependencies must allow an attacker to pollute Object.prototype.
  • The polluted property must affect protobufjs internal type lookup behavior.
  • The application must use protobufjs functionality that generates encode or decode code for affected types.
  • The generated code path must be reached after the prototype pollution has occurred.

Workarounds

Avoid running affected versions in applications where attacker-controlled input can pollute Object.prototype. If immediate upgrade is not possible, remove or mitigate reachable prototype pollution primitives and isolate schema/message processing from untrusted application state.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-12 15:01 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

protobufjs

npm · All systems

Affected

  • introduced 0, fixed 7.5.6 (semver)

Fixed versions

7.5.6

Fix

protobufjs

npm · All systems

Affected

  • introduced 8.0.0, fixed 8.0.2 (semver)

Fixed versions

8.0.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences