CVE-2026-107821
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-107821 is a high-severity Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) vulnerability in Mariadb (inferred from references). Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 39th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-95921
Vulnerability Data
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, MariaDB insufficiently validated counts, offsets, lengths, and field boundaries in FRM metadata while opening binary FRM files. An attacker able…
more
to place a crafted FRM file in the data directory could trigger out-of-bounds reads or writes, crash the server, or potentially execute code. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.1.1V2.2.1V2.2.2V5.3.3
Mitigating Controls (NIST 800-53 r5) AI
Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.
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.
Vulnerability identification processes can discover missing index validation via scanning or reviews.
Patching and replacement can remediate instances of the weakness after discovery.
Secure SDLC practices directly require input validation, preventing this class of flaw at development time.
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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach index/offset validation defects, but leaves a bounded remainder (e.g. incomplete enforcement across all languages, outsourced code without full assurance, or post-release changes)
A.8.26 explicitly lists resilience against SQL injections plus input validation/integrity checks (items d, j) as application security requirements to identify/address via risk assessment; this reaches a minority slice of index/offset validation defects but leaves most instances (non-web, non-SQL, incomplete enforcement, second-order) unaddressed by the requirements-setting process itself.
A.8.27 mandates security engineering principles including data validation/sanitization, distrust-external-input, security-by-design reviews against attack patterns, and hardening; this reaches a minority slice of CWE-1285 (index/offset validation in new designs) but leaves most instances (existing code, incomplete application of principles, or post-design defects) exploitable.
Secure coding standards directly require validation of indices, positions, and offsets before use.
Security testing can detect missing or incorrect index validation during development and acceptance.