How many CVEs have patched force_change_new_attribute_lazy?

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

What is the latest CVE that changed force_change_new_attribute_lazy?

CVE-2026-86338 (Ash field policies do not filter-nil forbidden calculations and aggregates, enabling an information-disclosure oracle), published 2026-09-16, changed lines 3285 of lib/ash/changeset/changeset.ex.

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

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

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

force_change_new_attribute_lazy

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

lib/ash/changeset/changeset.ex

Last patched September 16, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

force_change_new_attribute_lazy in ash-project/ash was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 2 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 force_change_new_attribute_lazy, newest first, with the lines each fix touched.

Ash field policies do not filter-nil forbidden calculations and aggregates, enabling an information-disclosure oracle
CVE-2026-86338 · line 3285 · +1 −1
Medium · CVSS 6.0
EPSS 0.4%2026-09-16

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 force_change_new_attribute_lazy.

How many CVEs have patched force_change_new_attribute_lazy?: 1 published CVEs changed force_change_new_attribute_lazy in ash-project/ash, in 1 distinct patches totalling 2 changed lines, between 2026 and 2026.
What is the latest CVE that changed force_change_new_attribute_lazy?: CVE-2026-86338 (Ash field policies do not filter-nil forbidden calculations and aggregates, enabling an information-disclosure oracle), published 2026-09-16, changed lines 3285 of lib/ash/changeset/changeset.ex.
How does force_change_new_attribute_lazy compare to the rest of ash-project/ash?: ash-project/ash has 29 CVEs with a located fix in total; 1 of them changed force_change_new_attribute_lazy.
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