{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59143 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59143 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59143 is a medium-severity memory corruption vulnerability in EGOR Data::RoaringBitmap::Shared, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59143 and fix it if it is affected.\n\nWhat it is: CVE-2026-59143 is a medium-severity memory corruption vulnerability in EGOR Data::RoaringBitmap::Shared, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59143 in the wild and no public exploit code.\n\nAffected product: EGOR Data::RoaringBitmap::Shared. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59143/ (Markdown: https://insights.sbomify.com/CVE-2026-59143/index.md)","id":"CVE-2026-59143","markdown":"https://insights.sbomify.com/CVE-2026-59143/index.md","name":"CVE-2026-59143","record":{"aliases":["GHSA-96m7-w48r-fx74"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl RoaringBitmap library","requires_auth":"low_privilege","summary":"A local attacker can trigger an out-of-bounds read and potential crash in the Perl Data::RoaringBitmap::Shared library by manipulating the backing file.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.\n\nThe 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.\n\nA 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Data::RoaringBitmap::Shared","id":"CVE-2026-59143","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Data::RingBuffer::Shared","id":"CVE-2026-59144"},"packages":[],"prev":{"headline":"Memory corruption in Data::HashMap::Shared","id":"CVE-2026-59142"},"products":["Data::RoaringBitmap::Shared"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["EGOR"]},"summary":"A local attacker can trigger an out-of-bounds read and potential crash in the Perl Data::RoaringBitmap::Shared library by manipulating the backing file.","url":"https://insights.sbomify.com/CVE-2026-59143/"}