Skip to main content
No exploitation reportedFix available

CVE-2022-1941

No exploitation reported by the sources we read.

  • Published2022-09-22
  • Fixed in4.21.6 · 3.21.6 · 3.20.2 · 3.19.5 · 3.18.3
  • WeaknessCWE-1286

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated.

Timeline

dates in UTC
  1. 2022-09-2215:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-1941?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-1941?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD · CISA-ADP
Google protobuf-cpp
BranchAffectedFixed in
4.x≥ 4.0.0, < 4.21.64.21.6
3.21≥ 3.21.0, < 3.21.63.21.6
3.20≥ 3.20.0, < 3.20.23.20.2
3.19≥ 3.19.0, < 3.19.53.19.5
3.18< 3.18.33.18.3
Google protobuf-python
BranchAffectedFixed in
4.x≥ 4.0.0, < 4.21.64.21.6
3.20≥ 3.20.0, < 3.20.23.20.2
3.19≥ 3.19.0, < 3.19.53.19.5
3.18< 3.18.33.18.3
Fedoraproject fedora
BranchAffectedFixed in
36.x= 36no fix published
37.x= 37no fix published

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • protobufAlmaLinux:9all versions · fixed in 3.14.0-16.el9and 5 other packages

Full record on NVD

Fix

  1. Update Google protobuf-cpp to 4.21.6 · 3.21.6 · 3.20.2 · 3.19.5 · 3.18.3

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-07-16
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.17.52024-07-16
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-1286read 2026-10-23
  • FIRST EPSSEPSS score1.5 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2022-09-22
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-1941?

A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated.

Is CVE-2022-1941 actively exploited?

Active exploitation of CVE-2022-1941 has not been confirmed. Its EPSS score was 1.5% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-1941?

CVE-2022-1941 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running protobuf? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month