Cyber Resilience

CVE-2026-8376

Perl ≤ 5.43.10

Published
26 May 2026
Modified
23 July 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0044 37th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2026-8376 is a critical-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Perl Perl. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Perl versions through 5.43.10 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds. Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified…

more

fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer. A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-57432Same product: Perl Perl
CVE-2026-13221Same product: Perl Perl
CVE-2024-56406Same product: Perl Perl
CVE-2026-4176Same product: Perl Perl
CVE-2023-47039Same product: Perl Perl
CVE-2026-14740Same vendor: Perl
CVE-2026-14739Same vendor: Perl
CVE-2026-10879Same vendor: Perl
CVE-2026-9698Same vendor: Perl
CVE-2025-23326Shared CWE-680

Affected Assets

perl
perl
≤ 5.43.10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.

Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.

Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.

Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect integer-overflow-to-buffer-overflow conditions during development.

prevents

Secure development life cycle mandates practices that can catch integer overflows before deployment.

prevents

Application security requirements can specify safe integer handling and bounds checking.

prevents

Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.

prevents

Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.

References