Protocol Buffers End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Protocol Buffers versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/protobuf)
Protocol Buffers lifecycle status — the real story
Protocol Buffers is Google's wire format — the serialization layer under gRPC and much of modern service-to-service traffic — and unusually for infrastructure this deep, Google publishes explicit support windows for it at protobuf.dev. The catch is that the windows are per language runtime and they do not line up: the same “protobuf” release is supported until different dates depending on whether you consume it from Java, C++, Python, or PHP. This table follows the Java runtime (com.google.protobuf:protobuf-java), which has the longest windows; C++ and Python lines expire one to three years earlier — check the vendor table for your runtime.
The fine print matters more than the table. Google's “3.x supported until March 2027” applies to the final 3.x minor — the 3.25 maintenance line, which still receives patches. Earlier 3.x minors (3.21, 3.23…) stopped receiving fixes the day their successor shipped, support window or not. A service pinned to protobuf-java 3.21 — a common resting place, since 3.22 changed the C++ runtime underneath the JNI-based implementations — is unpatched today despite “3.x” reading as supported. And proto2-era 2.x artifacts (2.5.0, 2.6.1), still surprisingly common in older Hadoop-ecosystem stacks, predate the policy entirely.
Because protobuf sits at the wire boundary, an unpatched copy is not an internal detail: malformed-message parsing bugs in old runtimes are reachable from anything that can send your service a payload. If migrating a pinned 2.x or early-3.x dependency is not practical, commercial extended support for end-of-life protobuf lines exists — see the support options below.
What does Protocol Buffers end of life mean for your organization?
When a version of Protocol Buffers reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Protocol Buffers should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Protocol Buffers versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Protocol Buffers has 2 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Protocol Buffers exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Protocol Buffers 3.x. Tell us where to reach you and we'll reply with matched options and pricing guidance.