Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-125 (跨界内存读) — Vulnerability Class 4336

4336 vulnerabilities classified as CWE-125 (跨界内存读). AI Chinese analysis included.

CWE-125, Out-of-bounds Read, is a memory safety weakness where software accesses memory locations outside the designated buffer boundaries, either before its start or past its end. This vulnerability typically arises from insufficient bounds checking during array indexing or pointer arithmetic, allowing attackers to read sensitive data such as stack canaries, cryptographic keys, or internal application state. By leveraging this flaw, adversaries can achieve information disclosure or potentially facilitate further exploitation techniques like heap spraying. Developers mitigate this risk by implementing rigorous input validation, utilizing static analysis tools to detect unsafe memory access patterns, and adopting safer programming languages or libraries that enforce automatic bounds checking. Additionally, employing compiler protections like Address Sanitizer during development helps identify these errors early, ensuring that memory reads remain strictly within allocated limits to prevent unauthorized data exposure.

MITRE CWE Description
The product reads data past the end, or before the beginning, of the intended buffer.
Common Consequences (4)
Confidentiality Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other Varies by Context
The read operation could produce other undefined or unexpected results.
Mitigations (2)
Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Architecture and Design Use a language that provides appropriate memory abstractions.
Examples (2)
In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method
int getValueFromArray(int *array, int len, int index) { int value; // check that the array index is less than the maximum // length of the array if (index < len) { // get the value at the specified index of the array value = array[index]; } // if array index is invalid then output error message // and return value indicating error else { printf("Value is: %d\n", array[index]); value = -1; } return value; }
Bad · C
... // check that the array index is within the correct // range of values for the array if (index >= 0 && index < len) { ...
Good · C
In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.
int processMessageFromSocket(int socket) { int success; char buffer[BUFFER_SIZE]; char message[MESSAGE_SIZE]; // get message from socket and store into buffer //Ignoring possibliity that buffer > BUFFER_SIZE if (getMessage(socket, buffer, BUFFER_SIZE) > 0) { // place contents of the buffer into message structure ExMessage *msg = recastBuffer(buffer); // copy message body into string for processing int index; for (index = 0; index < msg->msgLength; index++) { message[index] = msg->msgBody[index]; } message[index] = '\0'; // process message success = processMessage(message); } return success; }
Bad · C
CVE ID Title CVSS Severity Published
CVE-2026-113054 Chrome 156.0.8078.47 前 SiteIsolation 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113329 Chrome 156.0.8078.47 前 Installer 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113010 Chrome 156 扩展越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113045 Chrome Android 156.0.8078.47 离线模式越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113070 Chrome 156.0.8078.47 前 GetUserMedia 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113102 Chrome 156 之前版本 FileSystem 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113035 Chrome 156 前 API 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113006 Chrome 156 导航组件越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113095 Chrome 156.0.8078.47 以下 Focus 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113295 Chrome 156 之前版本 ANGLE 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113309 Chrome 156.0.8078.47 之前版本 Media 越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-113310 Chrome 156 之前版本蓝牙越界读取漏洞 — Chrome - - 2026-10-20
CVE-2026-100132 Acrobat for Edge | Out-of-bounds Read (CWE-125) — Acrobat for Edge 4.3 Medium 2026-10-20
CVE-2026-94202 Module block-pool create validates two of the four parameter words it reads — Eclipse ThreadX 4.8 Medium 2026-10-20
CVE-2026-94024 Module Manager object lookup validates one byte of a module's search name — Eclipse ThreadX 6.9 Medium 2026-10-20
CVE-2026-94023 Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion — Eclipse ThreadX 6.9 Medium 2026-10-20
CVE-2026-95109 Cortex-A7 module data validation checks only the first address of a caller-supplied range — Eclipse ThreadX 8.5 High 2026-10-20
CVE-2026-92843 Out-of-bounds Read via the TLS 1.3 Certificate extensions_length in NetX Secure — Eclipse ThreadX - NetX Duo 8.7 High 2026-10-20
CVE-2026-92853 Out-of-bounds Read via a Zero-length TLS 1.3 Certificate Message in NetX Secure — Eclipse ThreadX - NetX Duo 8.7 High 2026-10-20
CVE-2026-91057 Out-of-bounds read when a multi-line text view string ends with a carriage return — Eclipse ThreadX - GUIX 4.6 Medium 2026-10-20
CVE-2026-92454 JPEG decoder: truncated segments are read past the image buffer, and a zero sampling factor hangs the decode — Eclipse ThreadX - GUIX 6.1 Medium 2026-10-20
CVE-2026-91059 JPEG decoder: a duplicate SOF0 after SOS publishes a pixelmap that misreports its own allocation size — Eclipse ThreadX - GUIX 6.8 Medium 2026-10-20
CVE-2026-92446 GUIX binary resource loader reads past the end of a resource, because no length for it ever reaches the loader — Eclipse ThreadX - GUIX 6.8 Medium 2026-10-20
CVE-2026-91186 PNG decoder: a duplicate IHDR chunk after IDAT resizes the image after allocation, causing a heap out-of-bounds write — Eclipse ThreadX - GUIX 8.4 High 2026-10-20
CVE-2026-95111 Module queue front-send validates a word count as a byte count — Eclipse ThreadX 4.8 Medium 2026-10-20
CVE-2026-96402 USBX PIMA/MTP host class reads past its receive buffer when a device over-reports its object handle count — Eclipse ThreadX - USBX 5.2 Medium 2026-10-20
CVE-2026-96406 VIDEO class descriptor walk consumes device-controlled wTotalLength as its bound — Eclipse ThreadX - USBX 4.9 Medium 2026-10-20
CVE-2026-96582 Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser — Eclipse ThreadX - USBX 4.9 Medium 2026-10-20
CVE-2026-109395 Ning compress-lzf before 1.2.0 Out-of-Bounds Memory Access via UnsafeChunkDecoder — compress-lzf 9.1 Critical 2026-10-20
CVE-2026-112896 Pillow: TIFF encoder ColorMap plane-size mismatch causes a heap out-of-bounds read — Pillow 8.8 High 2026-10-19

Vulnerabilities classified as CWE-125 (跨界内存读) represent 4336 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.