dm-reverb
Reverb is an efficient and easy-to-use data storage and transport system designed for machine learning research.
Activity
- Latest release
- 2y ago
- Total releases
- 50
- Cadence
- ~12 days
- Last 12 months
- 0
Details
- License
- Apache-2.0
- First release
- Jul 19, 2020
| Version | Released | |
|---|---|---|
0.14.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.14.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.13.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.13.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.12.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.12.0rc2
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.12.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.12.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.11.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.11.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.11.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.10.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.10.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.10.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.9.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.9.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.9.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.8.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.8.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.7.3
patch
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.7.2
patch
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.7.1
patch
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.7.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.7.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.6.1
patch
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.6.1rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.6.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.6.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.5.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.5.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.5.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.4.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.4.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.1
patch
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.1rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc5
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc4
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc3
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc2
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0
minor
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0rc3
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0rc2
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.0
initial
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.0rc1
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.0rc0
pre
1 CVE
CVE-2024-8375
PYSEC-2026-2452
GHSA-w69q-w4h4-2fx8
PYSEC-2026-1306
Jul 13, 2026
Reverb use after free vulnerability
High
Local
High
Low
There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25 Affected versions
0.1.0
0.1.0rc0
0.1.0rc1
0.10.0
0.10.0rc0
0.10.0rc1
0.11.0
0.11.0rc0
0.11.0rc1
0.12.0
0.12.0rc0
0.12.0rc1
+ 38 more Show less
0.12.0rc2
0.13.0
0.13.0rc0
0.14.0
0.14.0rc0
0.2.0
0.2.0rc0
0.2.0rc1
0.2.0rc2
0.2.0rc3
0.3.0
0.3.0rc0
0.3.0rc1
0.3.0rc2
0.3.0rc3
0.3.0rc4
0.3.0rc5
0.3.1
0.3.1rc0
0.4.0
0.4.0rc0
0.5.0
0.5.0rc0
0.5.0rc1
0.6.0
0.6.0rc0
0.6.1
0.6.1rc0
0.7.0
0.7.0rc0
0.7.1
0.7.2
0.7.3
0.8.0
0.8.0rc0
0.9.0
0.9.0rc0
0.9.0rc1
References
Updated Jul 13, 2026 · Source: OSV.dev |