How many CVEs have patched mysql57_calculate_null_position?

1 published CVEs changed mysql57_calculate_null_position in MariaDB/server, in 1 distinct patches totalling 5 changed lines, between 2026 and 2026.

What is the latest CVE that changed mysql57_calculate_null_position?

CVE-2026-107821 (MariaDB: insufficient validation of binary frm data when opening a table), published 2026-10-09, changed lines 1067 to 1080 of sql/table.cc.

How does mysql57_calculate_null_position compare to the rest of MariaDB/server?

MariaDB/server has 23 CVEs with a located fix in total; 1 of them changed mysql57_calculate_null_position.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

MariaDB/server

Function

mysql57_calculate_null_position

Name: mysql57_calculate_null_position in MariaDB/server: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

sql/table.cc

Last patched October 9, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

5

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

mysql57_calculate_null_position in MariaDB/server was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 5 lines in total.

MariaDB/server has 23 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed mysql57_calculate_null_position, newest first, with the lines each fix touched.

MariaDB: insufficient validation of binary frm data when opening a table
CVE-2026-107821 · lines 1067–1080 · +4 −1 in 2 hunks
High · CVSS 8.0
EPSS 0.8%2026-10-09

Get an alert when the next CVE fix lands in MariaDB/server, with the patched functions.

Monitor server CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in MariaDB/server changed by the most CVE fixes.

Validate3 CVEs · extra/yassl/src/cert_wrapper.cpp X509_NAME_get_index_by_NID3 CVEs · extra/yassl/src/ssl.cpp CopyX5093 CVEs · extra/yassl/src/yassl_int.cpp GetEntry3 CVEs · extra/yassl/src/yassl_int.cpp GetLength3 CVEs · extra/yassl/src/yassl_int.cpp set_resuming3 CVEs · extra/yassl/src/yassl_int.cpp

All patched functions in MariaDB/server

Frequently asked questions

Common questions about CVE fixes to mysql57_calculate_null_position.

How many CVEs have patched mysql57_calculate_null_position?: 1 published CVEs changed mysql57_calculate_null_position in MariaDB/server, in 1 distinct patches totalling 5 changed lines, between 2026 and 2026.
What is the latest CVE that changed mysql57_calculate_null_position?: CVE-2026-107821 (MariaDB: insufficient validation of binary frm data when opening a table), published 2026-10-09, changed lines 1067 to 1080 of sql/table.cc.
How does mysql57_calculate_null_position compare to the rest of MariaDB/server?: MariaDB/server has 23 CVEs with a located fix in total; 1 of them changed mysql57_calculate_null_position.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track MariaDB/server CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing