Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.3
CVE-2026-59143: Data::RoaringBitmap::Shared (Perl) allows data corruption or crashes
CVE-2026-59143 · published 3 months ago
Summary
Versions of Data::RoaringBitmap::Shared for Perl before 0.02 have a security problem that can cause data corruption or crashes when using the rb_contains_locked function. This issue affects users who rely on Data::RoaringBitmap::Shared for data storage and retrieval. To stay safe, update to version 0.02 or later.
What to do
- Update egor data::roaringbitmap::shared to version 0.02 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| egor | data::roaringbitmap::shared | < 0.02 |
Original advisory text
Data::RoaringBitmap::Shared versions before 0.02 for Perl allow an out-of-bounds read via an unvalidated container offset and cardinality in rb_contains_locked.
The attach-time validator rb_valida...
Data::RoaringBitmap::Shared versions before 0.02 for Perl allow an out-of-bounds read via an unvalidated container offset and cardinality in rb_contains_locked.
The attach-time validator rb_validate_header checks the header scalars and region layout against the file size, but does not validate the bucket contents it then trusts. rb_contains_locked forms a container pointer as pool + container_off * 8192 from a raw file-stored offset and then searches over a file-stored cardinality, neither bounded against the container pool capacity or the fixed 8192-byte slot size.
A local peer that can write the backing file can leave the header valid while poisoning a bucket, so the next membership query dereferences a file-controlled wild pointer and scans a file-controlled count, reading adjacent memory or crashing the process.
The attach-time validator rb_validate_header checks the header scalars and region layout against the file size, but does not validate the bucket contents it then trusts. rb_contains_locked forms a container pointer as pool + container_off * 8192 from a raw file-stored offset and then searches over a file-stored cardinality, neither bounded against the container pool capacity or the fixed 8192-byte slot size.
A local peer that can write the backing file can leave the header valid while poisoning a bucket, so the next membership query dereferences a file-controlled wild pointer and scans a file-controlled count, reading adjacent memory or crashing the process.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
6.3
Medium
Type
CWE-125Out-of-bounds Read
Timeline
Published21 Jul 2026
Updated3 Nov 2026
First seen21 Jul 2026
Track software like this
Free during beta