CWE-125: Out-of-bounds Read
Official CWE-125 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.
Glexia's Take
CWE-125: 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.
Executive Impact
- Information disclosure
- Process crash
Developer Pattern
CWE-125 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Confidence
medium confidence from CWE-125, starter-2026-05.
Official CWE Definition
CWE-125: Out-of-bounds Read
Out-of-bounds Read is a software weakness pattern tracked by CWE 125. The local starter record is replaced by the official MITRE CWE import when the sync pipeline runs.
Out-of-bounds Read is a software weakness pattern tracked by CWE 125. The local starter record is replaced by the official MITRE CWE import when the sync pipeline runs.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- Reading beyond a buffer while parsing an untrusted packet.
Remediation
- Bounds checking
- Memory-safe abstractions
- Fuzzing
Detection
- Fuzzing
- SAST
- ASan/UBSan
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
No related CWE relationships are published yet.
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.