protobuf susceptible to buffer overflow

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2015-5237: 4.96% estimated exploitation activity in the next 30 days; percentile 92.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

protobuf allows remote authenticated attackers to cause a heap-based buffer overflow.

Published by the source

13 May 2022, 01:06 UTC

Last modified by the source

9 Jul 2026, 16:56 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jwvw-v7c5-m82h

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jwvw-v7c5-m82h

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

# Patch Next advisory brief: CVE-2015-5237

Advisory: protobuf susceptible to buffer overflow
IDs: CVE-2015-5237, GHSA-jwvw-v7c5-m82h
Record: https://patchnext.com/advisories/cve-2015-5237 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: protobuf 3.4.0; github.com/protocolbuffers/protobuf 3.4.0; google/protobuf 3.4.0; google.protobuf 3.4.0; com.google.protobuf:protobuf-parent 3.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI protobuf: affected < 3.4.0; fixed in 3.4.0
- Go github.com/protocolbuffers/protobuf: affected < 3.4.0; fixed in 3.4.0
- Packagist google/protobuf: affected < 3.4.0; fixed in 3.4.0
- NuGet google.protobuf: affected < 3.4.0; fixed in 3.4.0
- Maven com.google.protobuf:protobuf-parent: affected < 3.4.0; fixed in 3.4.0

## Suggested inspection (read-only)
- `python -m pip show protobuf`: prints the installed version. Run with the environment that serves production active.
- Go github.com/protocolbuffers/protobuf: check the installed version with your package manager.
- Packagist google/protobuf: check the installed version with your package manager.
- NuGet google.protobuf: check the installed version with your package manager.
- Maven com.google.protobuf:protobuf-parent: 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 protobuf, github.com/protocolbuffers/protobuf, google/protobuf, google.protobuf, com.google.protobuf:protobuf-parent.
- 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://osv.dev/vulnerability/GHSA-jwvw-v7c5-m82h (OSV record GHSA-jwvw-v7c5-m82h lists affected ranges: NuGet google.protobuf >=0 =0 =0 =0 =0 <3.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jwvw-v7c5-m82h (GitHub-reviewed advisory GHSA-jwvw-v7c5-m82h lists affected ranges: NuGet google.protobuf >=0 =0 =0 <3.4.0)

Commands are suggestions: review each one before running it.