Cyber Resilience

CVE-2026-107821

Published
09 October 2026
Modified
09 October 2026
CVSS Score v3.1 8.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0048 39th percentile
Risk Priority 54 floored blend · peak EPSS

CVSS 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

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

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-2024-23609Shared CWE-1285
CVE-2025-2633Shared CWE-1285
CVE-2024-51564Shared CWE-1285
CVE-2025-48502Shared CWE-1285
CVE-2024-0123Shared CWE-1285
CVE-2024-36342Shared CWE-1285
CVE-2023-36850Shared CWE-1285
CVE-2025-7848Shared CWE-1285
CVE-2025-2634Shared CWE-1285
CVE-2023-0859Shared CWE-1285

Affected Assets

Mariadb
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.1.1
  • V2.2.1
  • V2.2.2
  • V5.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.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
blocks

Patching and replacement can remediate instances of the weakness after discovery.

PR.PS-06 partial match
blocks

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.

blocks

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)

blocks

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.

blocks

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.

prevents

Secure coding standards directly require validation of indices, positions, and offsets before use.

finds

Security testing can detect missing or incorrect index validation during development and acceptance.

References