CVE-2026-8796: Sereal::Decoder versions before 5.005 for Perl allow heap out-of-bounds read via crafted input
Sereal::Decoder versions before 5.005 for Perl allow heap out-of-bounds read via crafted input.
In Perl/Decoder/srl_decoder.c, srl_read_object() and srl_read_hash() process a COPY tag, a back-reference whose target byte the decoder re-decodes as a fresh tag. When that target byte matches the SHORT_BINARY pattern (an inline string whose length is encoded in the low bits of the tag), the resulting read is not bounded to precede the COPY tag's own offset and can run past the end of the input buffer. An attacker controlled COPY offset can land inside a previously decoded value rather than on a tag boundary, planting a byte that the decoder reads as a SHORT_BINARY tag and consuming up to 31 following bytes from the heap as a class name (OBJECT path) or hash key (HASH path).
Security readout for executives and security teams
Sereal::Decoder for Perl can read memory outside the supplied input when parsing specially crafted serialized data. In affected versions before 5.005, this may expose sensitive heap data or crash the process. The issue matters most where services decode Sereal data influenced by users, partners, queues, caches, or network inputs. Exposure is likely limited to Perl applications using Sereal::Decoder before 5.005 and decoding attacker-influenced Sereal payloads. Systems that only process trusted, internally generated serialized data have lower practical exposure, but should still update because dependency boundaries often change over time. Treat this as a high-priority dependency update for any Perl service that processes Sereal data from outside a fully trusted boundary. Prioritize internet-facing, partner-facing, queue-consuming, and multi-tenant services first. No source in the bundle confirms active exploitation. Mitigation focus: Upgrade Sereal::Decoder or Sereal-Decoder to version 5.005 or later.; Identify services that decode Sereal data from users, partners, queues, caches, or network inputs.; Reject or isolate untrusted Sereal payloads until the patched dependency is deployed..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.