CVE-2026-44440
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.101.1 and 16.10.0, an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability on an endpoint allows an authenticated adjacent attacker to read arbitrary files. This vulnerability is fixed in 15.101.1 and 16.10.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceERPNext contains a path traversal vulnerability allowing authenticated adjacent attackers to read arbitrary files on the system via manipulation of file paths in a specific endpoint. The vulnerability exists in versions prior to 15.101.1 and 16.10.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.101.1>= 16.0.0, < 16.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check ERPNext version via bench CLIRun `bench version` in your ERPNext/Frappe bench directory to retrieve the installed ERPNext version numberAffected if The version shown is less than 15.101.1 or is 16.x.y where y is less than 10 (e.g., 16.0.0 through 16.9.x)
-
Check version via web interfaceLog into ERPNext as an administrator and navigate to Settings > System Settings > About, or access the /api/method/ping endpoint to inspect version information returned in the responseAffected if The displayed version matches the affected ranges (< 15.101.1 or >= 16.0.0 and < 16.10.0)
-
Verify authentication is required for the vulnerable endpointInspect your ERPNext web server configuration and confirm that user authentication is enforced. Path traversal requires an authenticated session to exploitAffected if The application allows unauthenticated access to the file-related endpoints, though authenticated adjacent attackers are the specified threat vector
-
Confirm ERPNext is exposed on networkCheck if your ERPNext instance is accessible from adjacent network segments (non-localhost connections). The vulnerability description specifies adjacent attacker scenarioAffected if ERPNext web interface is reachable from network segments beyond the localhost
You are affected if your installed ERPNext version is below 15.101.1 or falls between 16.0.0 and 16.10.0, and the application is accessible to authenticated users on adjacent networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.101.116.10.0
Upgrade ERPNext to version 15.101.1 or 16.10.0 to apply the patched code that properly validates and restricts file path inputs.
ERPNext 15.101.1 or later for 15.x branch; ERPNext 16.10.0 or later for 16.x branch
- Identify your current ERPNext version by checking the bench version or Frappe framework version
- If running ERPNext 15.x branch: Upgrade to version 15.101.1 or later using `bench update --patch` or by pulling the latest changes and running `bench migrate`
- If running ERPNext 16.x branch (>=16.0.0): Upgrade to version 16.10.0 or later using `bench update --patch` or by pulling the latest changes and running `bench migrate`
- After upgrade, verify the version using `bench version` to confirm the fix is applied
- Test that the application functions normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44440 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data