{"api_version":"1","generated_at":"2026-07-21T22:59:30+00:00","cve":"CVE-2026-59144","urls":{"html":"https://cve.report/CVE-2026-59144","api":"https://cve.report/api/cve/CVE-2026-59144.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-59144","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-59144"},"summary":{"title":"Data::RingBuffer::Shared versions before 0.04 for Perl allow a stack buffer overflow via an unvalidated elem_size in ring_read_seq","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.","state":"PUBLISHED","assigner":"CPANSec","published_at":"2026-07-21 20:17:03","updated_at":"2026-07-21 20:17:03"},"problem_types":["CWE-121","CWE-121 CWE-121 Stack-based Buffer Overflow"],"metrics":[],"references":[{"url":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/changes","name":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/changes","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/diff/EGOR/Data-RingBuffer-Shared-0.03#ring.h","name":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/diff/EGOR/Data-RingBuffer-Shared-0.03#ring.h","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-59144","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-59144","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"EGOR","product":"Data::RingBuffer::Shared","version":"affected 0.04 custom","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to Data::RingBuffer::Shared 0.04 or later, which pins elem_size to the fixed element size of the buffer's registered variant.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"For deployments that cannot upgrade to 0.04, place the backing file in a directory writable only by the owning user, so a local peer cannot tamper with the elem_size the read path trusts.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"collectionURL":"https://cpan.org/modules","defaultStatus":"unaffected","packageName":"Data-RingBuffer-Shared","product":"Data::RingBuffer::Shared","programFiles":["ring.h"],"programRoutines":[{"name":"ring_read_seq"}],"repo":"https://github.com/vividsnow/perl5-data-ringbuffer-shared","vendor":"EGOR","versions":[{"lessThan":"0.04","status":"affected","version":"0","versionType":"custom"}]}],"descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-121","description":"CWE-121 Stack-based Buffer Overflow","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-07-21T19:04:20.191Z","orgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","shortName":"CPANSec"},"references":[{"url":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/diff/EGOR/Data-RingBuffer-Shared-0.03#ring.h"},{"tags":["release-notes"],"url":"https://metacpan.org/release/EGOR/Data-RingBuffer-Shared-0.04/changes"}],"solutions":[{"lang":"en","value":"Upgrade to Data::RingBuffer::Shared 0.04 or later, which pins elem_size to the fixed element size of the buffer's registered variant."}],"source":{"discovery":"UNKNOWN"},"title":"Data::RingBuffer::Shared versions before 0.04 for Perl allow a stack buffer overflow via an unvalidated elem_size in ring_read_seq","workarounds":[{"lang":"en","value":"For deployments that cannot upgrade to 0.04, place the backing file in a directory writable only by the owning user, so a local peer cannot tamper with the elem_size the read path trusts."}],"x_generator":{"engine":"cpansec-cna-tool 0.1"}}},"cveMetadata":{"assignerOrgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","assignerShortName":"CPANSec","cveId":"CVE-2026-59144","datePublished":"2026-07-21T19:04:20.191Z","dateReserved":"2026-07-02T16:24:17.913Z","dateUpdated":"2026-07-21T19:04:20.191Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-21 20:17:03","lastModifiedDate":"2026-07-21 20:17:03","problem_types":["CWE-121","CWE-121 CWE-121 Stack-based Buffer Overflow"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"59144","Ordinal":"1","Title":"Data::RingBuffer::Shared versions before 0.04 for Perl allow a s","CVE":"CVE-2026-59144","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"59144","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Data::RingBuffer::Shared versions before 0.04 for Perl allow a s"}]}}}