{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59144 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59144 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59144 is a critical memory corruption vulnerability in EGOR Data::RingBuffer::Shared, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59144 and fix it if it is affected.\n\nWhat it is: CVE-2026-59144 is a critical memory corruption vulnerability in EGOR Data::RingBuffer::Shared, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59144 in the wild and no public exploit code.\n\nAffected product: EGOR Data::RingBuffer::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-59144/ (Markdown: https://insights.sbomify.com/CVE-2026-59144/index.md)","id":"CVE-2026-59144","markdown":"https://insights.sbomify.com/CVE-2026-59144/index.md","name":"CVE-2026-59144","record":{"aliases":["GHSA-jxx5-5g59-8f3j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl ring buffer library","requires_auth":"none","summary":"A local attacker can trigger a stack buffer overflow in the Perl Data::RingBuffer::Shared library by manipulating a shared memory file, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"Data::RingBuffer::Shared versions before 0.04 for Perl allow a stack buffer overflow via an unvalidated elem_size in ring_read_seq.\n\nThe attach-time validator ring_validate_header checks the capacity-overflow and total_size consistency of the header but never caps elem_size against the destination size. ring_read_seq does memcpy(out, ring_slot(h, seq), elem_size) with elem_size read raw from the mmap'd segment, copying into a fixed 8-byte destination scalar. An elem_size larger than 8 bytes writes past the destination.\n\nA local peer that can write the backing file can leave the header valid while setting a large elem_size, so the next read copies a file-controlled length into the fixed 8-byte stack buffer, corrupting adjacent stack frames.","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::RingBuffer::Shared","id":"CVE-2026-59144","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":"Information disclosure in Data::Intern::Shared","id":"CVE-2026-59145"},"packages":[],"prev":{"headline":"Memory corruption in Data::RoaringBitmap::Shared","id":"CVE-2026-59143"},"products":["Data::RingBuffer::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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["EGOR"]},"summary":"A local attacker can trigger a stack buffer overflow in the Perl Data::RingBuffer::Shared library by manipulating a shared memory file, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-59144/"}