How severe is GHSA-j2pc-v64r-mv4f?

No CVSS score has been assigned to GHSA-j2pc-v64r-mv4f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j2pc-v64r-mv4f?

GHSA-j2pc-v64r-mv4f affects the following packages: io.github.ascopes:protobuf-maven-plugin (Maven), io.github.ascopes:protobuf-maven-plugin (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j2pc-v64r-mv4f?

Update io.github.ascopes:protobuf-maven-plugin to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2pc-v64r-mv4f is resolved across your whole dependency graph.

How do I detect GHSA-j2pc-v64r-mv4f in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.ascopes:protobuf-maven-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j2pc-v64r-mv4f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j2pc-v64r-mv4f actively exploited in the wild?

No public exploit code has been indexed for GHSA-j2pc-v64r-mv4f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-j2pc-v64r-mv4f published, and has it been updated?

GHSA-j2pc-v64r-mv4f was published on November 4, 2025 and was last updated on November 15, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Protobuf Maven Plugin protocDigest is ignored when using protoc from PATHGHSA-j2pc-v64r-mv4f

Fix: ascopes/protobuf-maven-plugin@d3330e7

GHSA-j2pc-v64r-mv4f is a security vulnerability in io.github.ascopes:protobuf-maven-plugin. A fix is available for io.github.ascopes:protobuf-maven-plugin — see the affected versions and patch details below.

Published

Nov 4, 2025

Updated

Nov 15, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 15, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

☕io.github.ascopes:protobuf-maven-plugin☕io.github.ascopes:protobuf-maven-plugin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 <protoc>PATH</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:

<protoc>PATH</protoc>
<protocDigest>sha256:0000000000000000000000000000000000000000000000000000000000000000</protocDigest>

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.github.ascopes:protobuf-maven-plugin`	≥ 4.0.0&&< 4.0.2	4.0.2`io.github.ascopes:protobuf-maven-plugin:4.0.2`
☕Maven	`io.github.ascopes:protobuf-maven-plugin`	all versions	3.10.2`io.github.ascopes:protobuf-maven-plugin:3.10.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.ascopes:protobuf-maven-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.github.ascopes:protobuf-maven-plugin to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2pc-v64r-mv4f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 `<protoc>PATH</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://

O3 Security · Impact-Aware SCA

Is GHSA-j2pc-v64r-mv4f in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works