Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY25 SECURITY RECORDS

Frappe

ERPNext

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at erpnext, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-96672 23 Sep 2026 ERPNext: 16.0.0 < 16.34.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-94113 20 Sep 2026 ERPNext: < 15.121.0, 16.0.0 < 16.34.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-65822 17 Aug 2026 < 15.116.0; >= 16.0.0, < 16.23.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-65974 17 Aug 2026 < 15.111.0; >= 16.0.0, < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72911 10 Aug 2026 < 15.118.0; >= 16.0.0, < 16.29.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72910 10 Aug 2026 < 15.112.0; >= 16.0.0, < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72909 10 Aug 2026 < 15.112.0; >= 16.0.0, < 16.23.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72908 10 Aug 2026 < 15.109.0; >= 16.0.0, < 16.20.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72907 10 Aug 2026 < 15.111.0; >= 16.0.0, < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72906 10 Aug 2026 < 15.111.0; >= 16.0.0, < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13227 4 Aug 2026 < 15.115.0; < 16.26.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-12895 29 Jul 2026 < 15.111.0; < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-55242 15 Jul 2026 < 15.111.0; >= 16.0.0, < 16.22.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42839 3 Jun 2026 16.16.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42840 3 Jun 2026 16.16.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44448 13 May 2026 >= 16.0.0-beta.1, < 16.11.0; < 15.102.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44447 13 May 2026 < 16.9.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44446 13 May 2026 >= 16.0.0-beta.1, < 16.14.0; < 15.104.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44445 13 May 2026 >= 16.0.0-beta.1, < 16.12.0; < 15.104.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44441 13 May 2026 < 15.106.0; >= 16.0.0-beta.1, < 16.16.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44440 13 May 2026 < 15.101.1; >= 16.0.0-beta.1, < 16.10.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44442 13 May 2026 < 16.9.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-32954 20 Mar 2026 >= 16.0.0-beta.1, < 16.8.0; < 15.100.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-27471 21 Feb 2026 >= 16.0.0-rc.1, < 16.6.1; < 15.98.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2025-58439 6 Sep 2025 >=15.0.0, < 15.76.0; < 14.89.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.