CriticalGHSA-xq3m-2v4x-88ggCVE-2026-41242

Arbitrary code execution in protobufjs

Published 16 Apr 2026 · Updated 10 Sept 2026

Affected packages

Affected
>=8.0.0 <8.0.1
Fixed in
8.0.1
Update to the fixed version for your release line, for example:npm install protobufjs@8.0.1
Affected
<7.5.5
Fixed in
7.5.5
Update to the fixed version for your release line, for example:npm install protobufjs@7.5.5

Details

Summary

protobufjs could execute generated JavaScript code derived from protobuf schema metadata. When loading a crafted JSON descriptor, schema-controlled type names and type references could reach runtime code generation without sufficient validation.

Impact

An attacker who can provide a malicious protobuf definition or JSON descriptor to an application may be able to execute arbitrary JavaScript in the context of the process using protobufjs.

This requires control over the protobuf schema or descriptor being loaded. Applications that only decode messages using trusted, application-defined schemas are not directly affected by this issue.

Preconditions

  • The application must allow an attacker to control or influence a protobuf definition or JSON descriptor.
  • The application must load that definition through protobufjs reflection APIs such as descriptor loading.
  • The affected generated-code path must be reached, for example by performing an operation on the loaded type.

Workarounds

Do not load protobuf definitions or JSON descriptors from untrusted sources with affected versions. If untrusted schemas must be accepted, validate or restrict them before loading and run schema processing in an isolated environment.

Is GHSA-xq3m-2v4x-88gg in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected protobufjs, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.