# CVE-2026-44295: protobufjs-cli: Code injection in pbjs static output from crafted schema names

> Attackers can execute arbitrary code by providing crafted schema names to the protobufjs CLI static code generator.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** CLEANSTART-2026-XA34946, GHSA-6r35-46g8-jcw9

## What is CVE-2026-44295?

CVE-2026-44295 is a high-severity code injection vulnerability in protobufjs protobuf.js, published on 13 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.2.1 and 2.0.2, pbjs static code generation could emit unsafe JavaScript identifiers derived from schema-controlled names. When generating static JavaScript from a crafted schema or JSON descriptor, certain namespace, enum, service, or derived full names could be written into the generated output without sufficient sanitization. This vulnerability is fixed in 1.2.1 and 2.0.2.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-44295?

4 open source packages ship an affected version, including protobufjs-cli. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `protobufjs-cli` | npm | All versions | 1.2.1 |
| `protobufjs-cli` | npm | All versions | 1.2.1 |
| `protobufjs-cli` | npm | From 2.0.0 | 2.0.2 |
| `protobufjs-cli` | npm | From 2.0.0 | 2.0.2 |

Products: Protobufjs Project Protobufjs-Cli.

## How do I fix CVE-2026-44295?

Upgrade protobufjs-cli to a fixed version for your release line: 1.2.1 or 2.0.2.

## Is CVE-2026-44295 being exploited?

There is no known exploitation of CVE-2026-44295 in the wild and no public exploit code.

## Other vulnerabilities in protobufjs protobuf.js

- [CVE-2026-54271](https://insights.sbomify.com/CVE-2026-54271/): protobufjs-cli: Code injection in pbjs static output from crafted JSON descriptor names (high 8.2)
- [CVE-2026-42290](https://insights.sbomify.com/CVE-2026-42290/): protobufjs-cli: OS Command Injection (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44295 and fix it if it is affected.

What it is: CVE-2026-44295 is a high-severity code injection vulnerability in protobufjs protobuf.js, published on 13 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44295 in the wild and no public exploit code.

Affected packages and fixed versions:
- protobufjs-cli (npm): affected all versions; fixed in 1.2.1
- protobufjs-cli (npm): affected all versions; fixed in 1.2.1
- protobufjs-cli (npm): affected from 2.0.0; fixed in 2.0.2
- protobufjs-cli (npm): affected from 2.0.0; fixed in 2.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44295/ (Markdown: https://insights.sbomify.com/CVE-2026-44295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44295
- OSV: https://osv.dev/vulnerability/CVE-2026-44295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44295/
Summaries are generated and may contain mistakes; the official description above is the record.