How many CVEs have patched change_release_date?

1 published CVEs changed change_release_date in frappe/erpnext, in 4 distinct patches totalling 6 changed lines, between 2026 and 2026.

What is the latest CVE that changed change_release_date?

CVE-2026-72910 (ERPNext: Unauthorised modification of master data due to missing validation), published 2026-08-10, changed lines 937 to 939 of erpnext/accounts/doctype/purchase_invoice/purchase_invoice.py.

How does change_release_date compare to the rest of frappe/erpnext?

frappe/erpnext has 22 CVEs with a located fix in total; 1 of them changed change_release_date.

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Frappe
Erpnext
Change_release_date

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Frappe
Erpnext
Change_release_date

change_release_date in frappe/erpnext: Patched by 1 CVEs

frappe/erpnext

Function

change_release_date

Name: change_release_date in frappe/erpnext: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

erpnext/accounts/doctype/purchase_invoice/purchase_invoice.py

Last patched August 10, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

change_release_date in frappe/erpnext was changed by 1 published CVE fixes in 2026, in 4 distinct patches that added or removed 6 lines in total.

frappe/erpnext has 22 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

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

ERPNext: Unauthorised modification of master data due to missing validation
CVE-2026-72910 · lines 937–939 · +3 −3
High · CVSS 7.1
EPSS 0.5%2026-08-10

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

Monitor erpnext CVEs

Other hotspots in the repository

Functions in frappe/erpnext changed by the most CVE fixes.

inner_join11 CVEs · erpnext/projects/doctype/timesheet/timesheet.py from_10 CVEs · erpnext/controllers/queries.py get_material_requests_based_on_supplier10 CVEs · erpnext/stock/doctype/material_request/material_request.py select10 CVEs · erpnext/accounts/doctype/loyalty_program/loyalty_program.py get_income_account10 CVEs · erpnext/controllers/queries.py unset_existing_data10 CVEs · erpnext/accounts/doctype/chart_of_accounts_importer/chart_of_accounts_importer.py

All patched functions in frappe/erpnext

Frequently asked questions

Common questions about CVE fixes to change_release_date.

How many CVEs have patched change_release_date?: 1 published CVEs changed change_release_date in frappe/erpnext, in 4 distinct patches totalling 6 changed lines, between 2026 and 2026.
What is the latest CVE that changed change_release_date?: CVE-2026-72910 (ERPNext: Unauthorised modification of master data due to missing validation), published 2026-08-10, changed lines 937 to 939 of erpnext/accounts/doctype/purchase_invoice/purchase_invoice.py.
How does change_release_date compare to the rest of frappe/erpnext?: frappe/erpnext has 22 CVEs with a located fix in total; 1 of them changed change_release_date.
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

erpnext/accounts/doctype/purchase_invoice/purchase_invoice.py on GitHub (opens in a new tab)
All patched functions in frappe/erpnext
Patched functions directory

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

Track frappe/erpnext 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

On this page

Overview
CVEs that patched it
Other hotspots in the repository
FAQ
References