CVE-2020-15205
Data leak in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
9.0
Data leak in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
CVE-2020-15205- CVSS 3.1
- 9.0 Critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-122, CWE-119
- Updated
- 2026-11-02
EUVDEUVD-2020-0201
9.0
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
EUVD-2020-0201- CVSS 3.1
- 9.0 Critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-g7p5-5759-qv46
6.5
Data leak in Tensorflow
Impact
The data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory
>>> tf.raw_ops.StringNGrams(data=["aa", "bb", "cc", "dd", "ee", "ff"], data_splits=[0,8], separator=" ", ngram_widths=[3], left_pad="", right_pad="", pad_width=0, preserve_short_sequences=False)
StringNGrams(ngrams=<tf.Tensor: shape=(6,), dtype=string, numpy=
array([b'aa bb cc', b'bb cc dd', b'cc dd ee', b'dd ee ff',
b'ee ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00',
b'ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00 \x9b~\xa8q\x7f\x00\x00p\xf5j\xa7q\x7f\x00\x00H\xf8j\xa7q\x7f\x00\x00\xf0\xf3\xf7\x85q\x7f\x00\x00`}\xa6\x00\x00\x00\x00\x00`~\xa6\x00\x00\x00\x00\x00\xb0~\xeb\x9bq\x7f\x00'],...
All the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.
Patches
We have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
- Record
GHSA-g7p5-5759-qv46- CVSS 4.0
- 6.5 Medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H - CVSS 3.1
- 9.0 Critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-119, CWE-122, CWE-787
- Updated
- 2026-11-02
NVD
9.0
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
CVE-2020-15205- CVSS 3.1
- 9.0 Critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H - CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-119, CWE-122, CWE-787
- Updated
- 2026-11-02
OSV
9.8
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
CVE-2020-15205- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-g7p5-5759-qv46
6.5
Data leak in Tensorflow
Impact
The data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory
>>> tf.raw_ops.StringNGrams(data=["aa", "bb", "cc", "dd", "ee", "ff"], data_splits=[0,8], separator=" ", ngram_widths=[3], left_pad="", right_pad="", pad_width=0, preserve_short_sequences=False)
StringNGrams(ngrams=<tf.Tensor: shape=(6,), dtype=string, numpy=
array([b'aa bb cc', b'bb cc dd', b'cc dd ee', b'dd ee ff',
b'ee ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00',
b'ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00 \x9b~\xa8q\x7f\x00\x00p\xf5j\xa7q\x7f\x00\x00H\xf8j\xa7q\x7f\x00\x00\xf0\xf3\xf7\x85q\x7f\x00\x00`}\xa6\x00\x00\x00\x00\x00`~\xa6\x00\x00\x00\x00\x00\xb0~\xeb\x9bq\x7f\x00'],...
All the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.
Patches
We have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
- Record
GHSA-g7p5-5759-qv46- CVSS 4.0
- 6.5 Medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H - CVSS 3.1
- 9.0 Critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-119, CWE-122, CWE-787
- Updated
- 2026-11-02
Show 6 moreShow less
OSVBIT-tensorflow-2020-15205 No score
Data leak in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
BIT-tensorflow-2020-15205- Updated
- 2026-11-02
OSVopenSUSE-SU-2020:1766-1 No score
Security update for tensorflow2
This update for tensorflow2 fixes the following issues:
- updated to 2.1.2 with following fixes (boo#1177022):
- Fixes an undefined behavior causing a segfault in tf.raw_ops.Switch (CVE-2020-15190)
- Fixes three vulnerabilities in conversion to DLPack format (CVE-2020-15191, CVE-2020-15192, CVE-2020-15193)
- Fixes two vulnerabilities in SparseFillEmptyRowsGrad (CVE-2020-15194, CVE-2020-15195)
- Fixes an integer truncation vulnerability in code using the work sharder API (CVE-2020-15202)
- Fixes a format string vulnerability in tf.strings.as_string (CVE-2020-15203)
- Fixes segfault raised by calling session-only ops in eager mode (CVE-2020-15204)
- Fixes data leak and potential ASLR violation from tf.raw_ops.StringNGrams (CVE-2020-15205)
- Fixes segfaults caused by incomplete SavedModel validation (CVE-2020-15206)
- Fixes a data corruption due to a bug in negative indexing support in TFLite (CVE-2020-15207)
- Fixes a data corruption due to dimension mismatch in TFLite (CVE-2020-15208)
- Fixes several vulnerabilities in TFLite saved model format (CVE-2020-15209, CVE-2020-15210, CVE-2020-15211)
- Record
openSUSE-SU-2020:1766-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:12116-1 No score
tensorflow-lite-2.9.1-1.1 on GA media
These are all security issues fixed in the tensorflow-lite-2.9.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:12116-1- Updated
- 2026-11-02
OSVPYSEC-2020-128 No score
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
PYSEC-2020-128- Updated
- 2026-11-02
OSVPYSEC-2020-285 No score
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
PYSEC-2020-285- Updated
- 2026-11-02
OSVPYSEC-2020-320 No score
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the data_splits argument of tf.raw_ops.StringNGrams lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after ee ff are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
- Record
PYSEC-2020-320- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
tensorflowPyPI |
before 1.15.4 | 1.15.4 |
tensorflowPyPI |
2.0.0 up to 2.0.3 | 2.0.3 |
tensorflowPyPI |
2.1.0 up to 2.1.2 | 2.1.2 |
tensorflowPyPI |
2.2.0 to 2.2.0 | 2.2.1 |
tensorflowPyPI |
2.3.0 to 2.3.0 | 2.3.1 |
tensorflow-cpuPyPI |
before 1.15.4 | 1.15.4 |
tensorflow-cpuPyPI |
2.0.0 up to 2.0.3 | 2.0.3 |
tensorflow-cpuPyPI |
2.1.0 up to 2.1.2 | 2.1.2 |
tensorflow-cpuPyPI |
2.2.0 to 2.2.0 | 2.2.1 |
tensorflow-cpuPyPI |
2.3.0 to 2.3.0 | 2.3.1 |
Show 27 moreShow less
| Package | Affected | Fixed |
|---|---|---|
tensorflow-gpuPyPI |
before 1.15.4 | 1.15.4 |
tensorflow-gpuPyPI |
2.0.0 up to 2.0.3 | 2.0.3 |
tensorflow-gpuPyPI |
2.1.0 up to 2.1.2 | 2.1.2 |
tensorflow-gpuPyPI |
2.2.0 to 2.2.0 | 2.2.1 |
tensorflow-gpuPyPI |
2.3.0 to 2.3.0 | 2.3.1 |
tensorflowBitnami |
before 1.15.4, 2.0.0 up to 2.0.3, 2.1.0 up to 2.1.2, 2.2.0 up to 2.2.1, 2.3.0 up to 2.3.1 | 1.15.42.0.32.1.22.2.12.3.1 |
tensorflowPyPI |
before 1.15.4, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 24 moreShow less1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.0 |
1.15.4 |
tensorflowPyPI |
2.0.0 up to 2.0.3, plus listed versions 2.0.12.0.2 |
2.0.3 |
tensorflowPyPI |
2.1.0 up to 2.1.2, plus listed versions 2.1.1 |
2.1.2 |
tensorflowPyPI |
2.2.0 up to 2.2.1 | 2.2.1 |
tensorflowPyPI |
2.3.0 up to 2.3.1 | 2.3.1 |
tensorflow-cpuPyPI |
before 1.15.4, plus listed versions 1.15.0 |
1.15.4 |
tensorflow-cpuPyPI |
2.1.0 up to 2.1.2, plus listed versions 2.1.1 |
2.1.2 |
tensorflow-cpuPyPI |
2.2.0 up to 2.2.1 | 2.2.1 |
tensorflow-cpuPyPI |
2.3.0 up to 2.3.1 | 2.3.1 |
tensorflow-gpuPyPI |
before 1.15.4, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 24 moreShow less1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.0 |
1.15.4 |
tensorflow-gpuPyPI |
2.0.0 up to 2.0.3, plus listed versions 2.0.12.0.2 |
2.0.3 |
tensorflow-gpuPyPI |
2.1.0 up to 2.1.2, plus listed versions 2.1.1 |
2.1.2 |
tensorflow-gpuPyPI |
2.2.0 up to 2.2.1 | 2.2.1 |
tensorflow-gpuPyPI |
2.3.0 up to 2.3.1 | 2.3.1 |
tensorflowPyPI |
before 1.15.4, 2.0.0 up to 2.0.3, 2.1.0 up to 2.1.2, 2.2.0 up to 2.2.1, 2.3.0 up to 2.3.1, plus listed versions 0.12.0rc00.12.0rc10.12.00.12.11.0.0 Show 45 moreShow less1.0.11.1.0rc01.1.0rc11.1.0rc21.1.01.2.0rc01.2.0rc11.2.0rc21.2.01.2.11.3.0rc01.3.0rc11.3.0rc21.3.01.4.0rc01.4.0rc11.4.01.4.11.5.0rc01.5.0rc11.5.01.5.11.6.0rc01.6.0rc11.6.01.7.0rc01.7.0rc11.7.01.7.11.8.0rc01.8.0rc11.8.01.9.0rc01.9.0rc11.9.0rc21.9.01.10.0rc01.10.0rc11.10.01.10.11.11.0rc01.11.0rc11.11.0rc21.11.01.12.0rc0 |
1.15.42.0.32.1.22.2.12.3.1 |
tensorflow-cpuPyPI |
before 1.15.4, 2.0.0 up to 2.0.3, 2.1.0 up to 2.1.2, 2.2.0 up to 2.2.1, 2.3.0 up to 2.3.1, plus listed versions 1.15.02.1.1 |
1.15.42.0.32.1.22.2.12.3.1 |
tensorflow-gpuPyPI |
before 1.15.4, 2.0.0 up to 2.0.3, 2.1.0 up to 2.1.2, 2.2.0 up to 2.2.1, 2.3.0 up to 2.3.1, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 27 moreShow less1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.02.0.12.0.22.1.1 |
1.15.42.0.32.1.22.2.12.3.1 |
tensorflow2openSUSE:Leap 15.2 From an advisory covering 16 CVEs |
before 2.1.2-lp152.7.3.1 | 2.1.2-lp152.7.3.1 |
tensorflow2-liteopenSUSE:Leap 15.2 From an advisory covering 16 CVEs |
before 2.1.2-lp152.7.3.1 | 2.1.2-lp152.7.3.1 |
tensorflow2_2_1_2-gnu-hpcopenSUSE:Leap 15.2 From an advisory covering 16 CVEs |
before 2.1.2-lp152.7.3.1 | 2.1.2-lp152.7.3.1 |
tensorflow2_2_1_2-gnu-openmpi2-hpcopenSUSE:Leap 15.2 From an advisory covering 16 CVEs |
before 2.1.2-lp152.7.3.1 | 2.1.2-lp152.7.3.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-15205 is a critical vulnerability (CVSS 9.0) in Google Tensorflow, published September 25, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.03%, the 63rd percentile. Fixed in tensorflow 1.15.4.
References
github.com/tensorflow/tensorflow/releases/tag/v2.3.1
github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46
github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80
lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
nvd.nist.gov/vuln/detail/CVE-2020-15205
github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-285.yaml
Show 177 moreShow less
github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-320.yaml
github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-128.yaml
github.com/advisories/GHSA-g7p5-5759-qv46
github.com/tensorflow/tensorflow
lists.opensuse.org/archives/list/[email protected]/thread/TNMEEN772D6LWSHNB64QFB5TB3CZZEF4
bugzilla.suse.com/1173314
bugzilla.suse.com/1175099
bugzilla.suse.com/1175789
bugzilla.suse.com/1177022
suse.com/security/cve/CVE-2020-15190
suse.com/security/cve/CVE-2020-15191
suse.com/security/cve/CVE-2020-15192
suse.com/security/cve/CVE-2020-15193
suse.com/security/cve/CVE-2020-15194
suse.com/security/cve/CVE-2020-15195
suse.com/security/cve/CVE-2020-15202
suse.com/security/cve/CVE-2020-15203
suse.com/security/cve/CVE-2020-15204
suse.com/security/cve/CVE-2020-15205
suse.com/security/cve/CVE-2020-15206
suse.com/security/cve/CVE-2020-15207
suse.com/security/cve/CVE-2020-15208
suse.com/security/cve/CVE-2020-15209
suse.com/security/cve/CVE-2020-15210
suse.com/security/cve/CVE-2020-15211
suse.com/security/cve/CVE-2020-10531
suse.com/security/cve/CVE-2020-26266
suse.com/security/cve/CVE-2020-26270
suse.com/security/cve/CVE-2021-22922
suse.com/security/cve/CVE-2021-22923
suse.com/security/cve/CVE-2021-22926
suse.com/security/cve/CVE-2021-37635
suse.com/security/cve/CVE-2021-37636
suse.com/security/cve/CVE-2021-37637
suse.com/security/cve/CVE-2021-37638
suse.com/security/cve/CVE-2021-37639
suse.com/security/cve/CVE-2021-37640
suse.com/security/cve/CVE-2021-37641
suse.com/security/cve/CVE-2021-37642
suse.com/security/cve/CVE-2021-37643
suse.com/security/cve/CVE-2021-37644
suse.com/security/cve/CVE-2021-37645
suse.com/security/cve/CVE-2021-37646
suse.com/security/cve/CVE-2021-37647
suse.com/security/cve/CVE-2021-37648
suse.com/security/cve/CVE-2021-37649
suse.com/security/cve/CVE-2021-37650
suse.com/security/cve/CVE-2021-37651
suse.com/security/cve/CVE-2021-37652
suse.com/security/cve/CVE-2021-37653
suse.com/security/cve/CVE-2021-37654
suse.com/security/cve/CVE-2021-37655
suse.com/security/cve/CVE-2021-37656
suse.com/security/cve/CVE-2021-37657
suse.com/security/cve/CVE-2021-37658
suse.com/security/cve/CVE-2021-37659
suse.com/security/cve/CVE-2021-37660
suse.com/security/cve/CVE-2021-37661
suse.com/security/cve/CVE-2021-37662
suse.com/security/cve/CVE-2021-37663
suse.com/security/cve/CVE-2021-37664
suse.com/security/cve/CVE-2021-37665
suse.com/security/cve/CVE-2021-37666
suse.com/security/cve/CVE-2021-37667
suse.com/security/cve/CVE-2021-37668
suse.com/security/cve/CVE-2021-37669
suse.com/security/cve/CVE-2021-37670
suse.com/security/cve/CVE-2021-37671
suse.com/security/cve/CVE-2021-37672
suse.com/security/cve/CVE-2021-37673
suse.com/security/cve/CVE-2021-37674
suse.com/security/cve/CVE-2021-37675
suse.com/security/cve/CVE-2021-37676
suse.com/security/cve/CVE-2021-37677
suse.com/security/cve/CVE-2021-37678
suse.com/security/cve/CVE-2021-37679
suse.com/security/cve/CVE-2021-37680
suse.com/security/cve/CVE-2021-37681
suse.com/security/cve/CVE-2021-37682
suse.com/security/cve/CVE-2021-37683
suse.com/security/cve/CVE-2021-37684
suse.com/security/cve/CVE-2021-37685
suse.com/security/cve/CVE-2021-37686
suse.com/security/cve/CVE-2021-37687
suse.com/security/cve/CVE-2021-37688
suse.com/security/cve/CVE-2021-37689
suse.com/security/cve/CVE-2021-37690
suse.com/security/cve/CVE-2021-37691
suse.com/security/cve/CVE-2021-37692
suse.com/security/cve/CVE-2021-41195
suse.com/security/cve/CVE-2021-41196
suse.com/security/cve/CVE-2021-41197
suse.com/security/cve/CVE-2021-41198
suse.com/security/cve/CVE-2021-41199
suse.com/security/cve/CVE-2021-41200
suse.com/security/cve/CVE-2021-41201
suse.com/security/cve/CVE-2021-41202
suse.com/security/cve/CVE-2021-41203
suse.com/security/cve/CVE-2021-41204
suse.com/security/cve/CVE-2021-41205
suse.com/security/cve/CVE-2021-41206
suse.com/security/cve/CVE-2021-41207
suse.com/security/cve/CVE-2021-41208
suse.com/security/cve/CVE-2021-41209
suse.com/security/cve/CVE-2021-41210
suse.com/security/cve/CVE-2021-41211
suse.com/security/cve/CVE-2021-41212
suse.com/security/cve/CVE-2021-41213
suse.com/security/cve/CVE-2021-41214
suse.com/security/cve/CVE-2021-41215
suse.com/security/cve/CVE-2021-41216
suse.com/security/cve/CVE-2021-41217
suse.com/security/cve/CVE-2021-41218
suse.com/security/cve/CVE-2021-41219
suse.com/security/cve/CVE-2021-41220
suse.com/security/cve/CVE-2021-41221
suse.com/security/cve/CVE-2021-41222
suse.com/security/cve/CVE-2021-41223
suse.com/security/cve/CVE-2021-41224
suse.com/security/cve/CVE-2021-41225
suse.com/security/cve/CVE-2021-41226
suse.com/security/cve/CVE-2021-41227
suse.com/security/cve/CVE-2021-41228
suse.com/security/cve/CVE-2022-21725
suse.com/security/cve/CVE-2022-21726
suse.com/security/cve/CVE-2022-21727
suse.com/security/cve/CVE-2022-21728
suse.com/security/cve/CVE-2022-21729
suse.com/security/cve/CVE-2022-21730
suse.com/security/cve/CVE-2022-21731
suse.com/security/cve/CVE-2022-21732
suse.com/security/cve/CVE-2022-21733
suse.com/security/cve/CVE-2022-21734
suse.com/security/cve/CVE-2022-21735
suse.com/security/cve/CVE-2022-21736
suse.com/security/cve/CVE-2022-21737
suse.com/security/cve/CVE-2022-21738
suse.com/security/cve/CVE-2022-21739
suse.com/security/cve/CVE-2022-21740
suse.com/security/cve/CVE-2022-21741
suse.com/security/cve/CVE-2022-23557
suse.com/security/cve/CVE-2022-23558
suse.com/security/cve/CVE-2022-23559
suse.com/security/cve/CVE-2022-23560
suse.com/security/cve/CVE-2022-23561
suse.com/security/cve/CVE-2022-23562
suse.com/security/cve/CVE-2022-23563
suse.com/security/cve/CVE-2022-23564
suse.com/security/cve/CVE-2022-23565
suse.com/security/cve/CVE-2022-23566
suse.com/security/cve/CVE-2022-23567
suse.com/security/cve/CVE-2022-23568
suse.com/security/cve/CVE-2022-23569
suse.com/security/cve/CVE-2022-23570
suse.com/security/cve/CVE-2022-23571
suse.com/security/cve/CVE-2022-23572
suse.com/security/cve/CVE-2022-23573
suse.com/security/cve/CVE-2022-23574
suse.com/security/cve/CVE-2022-23575
suse.com/security/cve/CVE-2022-23576
suse.com/security/cve/CVE-2022-23577
suse.com/security/cve/CVE-2022-23578
suse.com/security/cve/CVE-2022-23579
suse.com/security/cve/CVE-2022-23580
suse.com/security/cve/CVE-2022-23581
suse.com/security/cve/CVE-2022-23582
suse.com/security/cve/CVE-2022-23583
suse.com/security/cve/CVE-2022-23584
suse.com/security/cve/CVE-2022-23585
suse.com/security/cve/CVE-2022-23586
suse.com/security/cve/CVE-2022-23587
suse.com/security/cve/CVE-2022-23588
suse.com/security/cve/CVE-2022-23589
suse.com/security/cve/CVE-2022-23590
suse.com/security/cve/CVE-2022-23591
suse.com/security/cve/CVE-2022-23594
suse.com/security/cve/CVE-2022-23595
Left out here: 23 versions. The JSON record has them.