Protobuf Maven Plugin protocDigest is ignored when using protoc from PATH

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

1.0 · CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The expected protocDigest is ignored when protoc is taken from the PATH. Details The documentation for the protocDigest parameter says: ... Users may wish to specify this if using a PATH-based binary ... However, when specifying <protocPATH</protoc the protocDigest is not actually checked because the code returns here already https://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L91-L93 before the digest check: https://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L106 PoC Specify: And notice how the protoc on the PATH is not rejected, despite a digest mismatch. Impact Users who have an untrusted protoc executable on their PATH and rely <protocDigest as protection are affected.

Published by the source

4 Nov 2025, 15:48 UTC

Last modified by the source

4 Nov 2025, 15:48 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j2pc-v64r-mv4f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j2pc-v64r-mv4f

Advisory: Protobuf Maven Plugin protocDigest is ignored when using protoc from PATH
IDs: GHSA-j2pc-v64r-mv4f
Record: https://patchnext.com/advisories/ghsa-j2pc-v64r-mv4f (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.github.ascopes:protobuf-maven-plugin 4.0.2, 3.10.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.github.ascopes:protobuf-maven-plugin: affected >= 4.0.0, <= 4.0.1; < 3.10.2; fixed in 3.10.2, 4.0.2

## Suggested inspection (read-only)
- Maven io.github.ascopes:protobuf-maven-plugin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.github.ascopes:protobuf-maven-plugin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j2pc-v64r-mv4f (GitHub-reviewed advisory GHSA-j2pc-v64r-mv4f lists affected ranges: Maven io.github.ascopes:protobuf-maven-plugin >=4.0.0 =0 <3.10.2)

Commands are suggestions: review each one before running it.