How severe is CVE-2022-3171?

CVE-2022-3171 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-3171?

CVE-2022-3171 affects the following packages: com.google.protobuf:protobuf-java (Maven), com.google.protobuf:protobuf-kotlin (Maven), com.google.protobuf:protobuf-javalite (Maven), com.google.protobuf:protobuf-kotlin-lite (Maven), com.google.protobuf:protobuf-java (Maven), com.google.protobuf:protobuf-java (Maven), com.google.protobuf:protobuf-java (Maven), com.google.protobuf:protobuf-kotlin (Maven), and 12 more. Ecosystems affected: Maven, RubyGems.

How do I fix CVE-2022-3171?

Update com.google.protobuf:protobuf-java to 3.21.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3171 is resolved across your whole dependency graph.

How do I detect CVE-2022-3171 in my Maven, RubyGems dependencies?

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

How do I mitigate CVE-2022-3171 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-3171 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-3171 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.

What is the EPSS score for CVE-2022-3171?

CVE-2022-3171 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-3171?

CVE-2022-3171 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-3171 published, and has it been updated?

CVE-2022-3171 was published on October 12, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2022-3171 — protobuf-java

MEDIUM

CVE-2022-3171 is a medium-severity (CVSS 4.3) Improper Input Validation vulnerability in com.google.protobuf:protobuf-java. A fix is available for com.google.protobuf:protobuf-java — see the affected versions and patch details below.

Memory handling vulnerability in ProtocolBuffers Java core and lite

Also known asGHSA-h4h5-3hr4-j3g2

Published

Oct 12, 2022

Updated

Oct 28, 2026

Affected

20 pkgs

Patched

20 / 20

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-3171.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

20 pkgs affected

☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-kotlin☕com.google.protobuf:protobuf-javalite☕com.google.protobuf:protobuf-kotlin-lite☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-kotlin+12 more

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

A potential Denial of Service issue in protobuf-java core and lite was discovered in the parsing procedure for binary and text format data. Input streams containing multiple instances of non-repeated embedded messages with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses.

Reporter: OSS Fuzz

Affected versions: This issue affects both the Java full and lite Protobuf runtimes, as well as Protobuf for Kotlin and JRuby, which themselves use the Java Protobuf runtime.

Severity

CVE-2022-3171 Medium - CVSS Score: 5.7 (NOTE: there may be a delay in publication)

Remediation and Mitigation

Please update to the latest available versions of the following packages:

protobuf-java (3.21.7, 3.20.3, 3.19.6, 3.16.3) protobuf-javalite (3.21.7, 3.20.3, 3.19.6, 3.16.3) protobuf-kotlin (3.21.7, 3.20.3, 3.19.6, 3.16.3) protobuf-kotlin-lite (3.21.7, 3.20.3, 3.19.6, 3.16.3) google-protobuf [JRuby gem only] (3.21.7, 3.20.3, 3.19.6)

Affected Packages

20 total 20 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.google.protobuf:protobuf-java`	≥ 3.21.0-rc-1&&< 3.21.7	3.21.7`com.google.protobuf:protobuf-java:3.21.7`
☕Maven	`com.google.protobuf:protobuf-kotlin`	≥ 3.21.0-rc-1&&< 3.21.7	3.21.7`com.google.protobuf:protobuf-kotlin:3.21.7`
☕Maven	`com.google.protobuf:protobuf-javalite`	≥ 3.21.0-rc-1&&< 3.21.7	3.21.7`com.google.protobuf:protobuf-javalite:3.21.7`
☕Maven	`com.google.protobuf:protobuf-kotlin-lite`	≥ 3.21.0-rc-1&&< 3.21.7	3.21.7`com.google.protobuf:protobuf-kotlin-lite:3.21.7`
☕Maven	`com.google.protobuf:protobuf-java`	≥ 3.20.0-rc-1&&< 3.20.3	3.20.3`com.google.protobuf:protobuf-java:3.20.3`
☕Maven	`com.google.protobuf:protobuf-java`	≥ 3.17.0-rc-1&&< 3.19.6	3.19.6`com.google.protobuf:protobuf-java:3.19.6`

Affected Products

6 products · 21 configurations

fedorafedoraproject

1 version

Application

google-protobufgoogle

≥ 3.21.0 && < 3.21.7

range

Application

protobuf-javagoogle

≥ 3.21.0 && < 3.21.7

range

Application

protobuf-javalitegoogle

≥ 3.21.0 && < 3.21.7

range

Application

protobuf-kotlingoogle

≥ 3.21.0 && < 3.21.7

range

Application

protobuf-kotlin-litegoogle

≥ 3.21.0 && < 3.21.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.protobuf:protobuf-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.google.protobuf:protobuf-java to 3.21.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3171 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat AMQ Streams 2.7.0	see advisory	RHSA-2024:3527
Red Hat build of Quarkus 2.13.5	see advisory	RHSA-2022:9023
Red Hat build of Quarkus 2.7.7	`protobuf-java`	RHSA-2023:1006
RHINT Debezium 1.9.7	`protobuf-java`	RHSA-2022:7896
RHPAM 7.13.4 async	`protobuf-java`	RHSA-2023:4983

Frequently Asked Questions

## Summary A potential Denial of Service issue in `protobuf-java` core and lite was discovered in the parsing procedure for binary and text format data. Input streams containing multiple instances of non-repeated [embedded messages](http://developers.google.com/protocol-buffers/docs/encoding#embedded) with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses. Reporter: [OSS Fuzz](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48771) Affected versions: This issue affects both

O3 Security · Impact-Aware SCA

Is CVE-2022-3171 in your dependencies?

Find it across Maven, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Raw vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

protobuf

6.1/10

Maintained10/10

Code-Review0/10

Dependency-Update-Tool10/10

Vulnerabilities6/10

Branch-ProtectionN/A

Assessed Nov 3, 2026

Timeline

Disclosed

Oct 12, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-3171

GHSA-h4h5-3hr4-j3g2

References

Advisorygithub.com · CVE 2022 3171.json Advisorygithub.com · GHSA h4h5 3hr4 j3g2 Advisorylists.fedoraproject.org · CBAUKJQL6O4TIWYBENORSY5P43TVB4M3 Advisorylists.fedoraproject.org · MPCGUT3T5L6C3IDWUPSUO22QDCGQKTOP Advisorynvd.nist.gov · CVE 2022 3171 Advisorysecurity.gentoo.org · 202301 09 Webbugs.chromium.org · detail Webgithub.com · v21.7 Webgithub.com · v3.16.3 Webgithub.com · v3.19.6 Webgithub.com · v3.20.3 Webgithub.com · CVE 2022 3171.yml Weblists.fedoraproject.org · CBAUKJQL6O4TIWYBENORSY5P43TVB4M3 Weblists.fedoraproject.org · MPCGUT3T5L6C3IDWUPSUO22QDCGQKTOP Packagegithub.com · protobuf

Related vulnerabilities

Also affects protobuf-java

This CVE is medium severity; 4 of 4 other CVEs affecting protobuf-java are rated as high or higher (top: high).

CVE-2024-7254CVE-2022-3510CVE-2022-3509CVE-2021-22569

Same weakness: CWE-20

This CVE is medium severity; 3 of 4 other CVEs with CWE-20 are rated as high or higher (top: high).

CVE-2026-44265CVE-2026-119280CVE-2026-96631CVE-2026-119210Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-3171 — protobuf-java

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Summary

Severity

Remediation and Mitigation

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-3171 in your dependencies?