EGOR Data::RoaringBitmap::Shared up to 0.1 rb_validate_header roaring.h rb_contains_locked container offset/cardinality out-of-bounds

Summaryinfo

A vulnerability was found in EGOR Data::RoaringBitmap::Shared up to 0.1. It has been classified as problematic. Affected by this vulnerability is the function rb_contains_locked of the file roaring.h of the component rb_validate_header. The manipulation of the argument container offset/cardinality leads to out-of-bounds. This vulnerability is traded as CVE-2026-59143. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability was found in EGOR Data::RoaringBitmap::Shared up to 0.1 and classified as problematic. This issue affects the function rb_contains_locked of the file roaring.h of the component rb_validate_header. The manipulation of the argument container offset/cardinality with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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 advisory is shared at metacpan.org. The identification of this vulnerability is CVE-2026-59143 since 07/02/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading to version 0.02 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• EGOR

Name

• Data::RoaringBitmap::Shared

Version

• 0.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion