Most recent entries from all

CLEANSTART-2026-QX07300 — Security fix for CVE-2026-54271 applied in: azure-functions-node 4.1052.200-r0

2026-10-03T05:20:24.993828+00:00

Affected: CleanStart: azure-functions-node

Security vulnerability affects the azure-functions-node package. This issue is resolved in later releases. See references for vulnerability details.

EUVD-2026-329214

2026-10-03T05:20:24.993880+00:00

EUVD-2026-329214

fkie_cve-2026-54271

2026-10-03T05:20:24.993896+00:00

protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.3.2 and 2.5.0, a previous fix for unsafe name handling in pbjs static / static-module code generation was incomplete. Affected versions of protobufjs-cli could still emit unsafe JavaScript references when generating static output from crafted JSON descriptor input. The common case of parsing schemas from .proto files is not affected. This is a bypass of CVE-2026-44295. An attacker who can provide or influence pre-parsed JSON descriptors passed to pbjs static code generation may be able to cause generated JavaScript output to contain attacker-controlled code. The injected code may execute if the generated file is later executed or imported and an affected generated API path is invoked. This vulnerability is fixed in 1.3.2 and 2.5.0.

GHSA-pr59-h9ph-3fr8 — protobufjs-cli: Code injection in pbjs static output from crafted JSON descriptor names

2026-10-03T05:20:24.993929+00:00

Affected: npm: protobufjs-cli

## Summary

A previous fix for unsafe name handling in `pbjs` static / static-module code generation was incomplete. Affected versions of `protobufjs-cli` could still emit unsafe JavaScript references when generating static output from crafted JSON descriptor input. The common case of parsing schemas from `.proto` files is not affected.

This is a bypass of GHSA-6r35-46g8-jcw9 / CVE-2026-44295.

## Impact

An attacker who can provide or influence pre-parsed JSON descriptors passed to `pbjs` static code generation may be able to cause generated JavaScript output to contain attacker-controlled code.

The injected code may execute if the generated file is later executed or imported and an affected generated API path is invoked.

## Preconditions

* The application or build process must run `pbjs` static code generation on a pre-parsed JSON descriptor influenced by an attacker. * The generated JavaScript file must subsequently be executed or imported. * An affected generated API path must be invoked.

## Workarounds

Do not run affected versions of `pbjs` static or static-module generation on untrusted JSON descriptors. If untrusted JSON descriptors must be accepted, validate descriptor-derived names before code generation and reject names that could not have been produced by parsing a valid `.proto` file. Running code generation in an isolated environment can reduce impact.