How many CVEs have patched get_valid_pkey?

1 published CVEs changed get_valid_pkey in ash-project/ash, in 1 distinct patches totalling 24 changed lines, between 2026 and 2026.

What is the latest CVE that changed get_valid_pkey?

CVE-2026-82745 (ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness), published 2026-09-01, changed lines 1853 to 1867 of lib/ash/data_layer/ets/ets.ex.

How does get_valid_pkey compare to the rest of ash-project/ash?

ash-project/ash has 29 CVEs with a located fix in total; 1 of them changed get_valid_pkey.

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

ash-project/ash

Function

get_valid_pkey

Name: get_valid_pkey in ash-project/ash: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/ash/data_layer/ets/ets.ex

Last patched September 1, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

24

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

get_valid_pkey in ash-project/ash was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 24 lines in total.

ash-project/ash has 29 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

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

ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness
CVE-2026-82745 · lines 1853–1867 · +14 −10
Medium · CVSS 5.9
EPSS 0.2%2026-09-01

Get an alert when the next CVE fix lands in ash-project/ash, with the patched functions.

Monitor ash CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in ash-project/ash changed by the most CVE fixes.

length_ok2 CVEs · lib/ash/type/string.ex project2 CVEs · mix.exs start2 CVEs · lib/ash/application.ex hello2 CVEs · lib/ash.ex run_count_query1 CVEs · lib/ash/actions/read.ex update_aggregate_filters1 CVEs · lib/ash/actions/read.ex

All patched functions in ash-project/ash

Frequently asked questions

Common questions about CVE fixes to get_valid_pkey.

How many CVEs have patched get_valid_pkey?: 1 published CVEs changed get_valid_pkey in ash-project/ash, in 1 distinct patches totalling 24 changed lines, between 2026 and 2026.
What is the latest CVE that changed get_valid_pkey?: CVE-2026-82745 (ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness), published 2026-09-01, changed lines 1853 to 1867 of lib/ash/data_layer/ets/ets.ex.
How does get_valid_pkey compare to the rest of ash-project/ash?: ash-project/ash has 29 CVEs with a located fix in total; 1 of them changed get_valid_pkey.
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 ash-project/ash 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