# CVE-2026-109377: ERPNext 9.0.0 through 16.50.0 Missing Authorization in Batch Lookup Methods

> Authenticated users, including customer portal users, can view sensitive stock quantities and batch details via exposed API methods.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jg45-xvf3-93rf

## What is CVE-2026-109377?

CVE-2026-109377 is a medium-severity missing authorization vulnerability in Frappe ERPNext, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ERPNext 9.0.0 through 16.50.0 contains a missing authorization vulnerability that allows authenticated users to view stock quantities via whitelisted batch methods. Attackers, including customer portal users, can call get_batch_qty, get_batches_by_oldest or get_pos_reserved_batch_qty to list every item batch with per-warehouse quantities.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-109377?


## How do I fix CVE-2026-109377?

No fix has been published for CVE-2026-109377 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109377 being exploited?

There is no known exploitation of CVE-2026-109377 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109377 and fix it if it is affected.

What it is: CVE-2026-109377 is a medium-severity missing authorization vulnerability in Frappe ERPNext, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109377 in the wild and no public exploit code.

Affected product: Frappe ERPNext. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109377/ (Markdown: https://insights.sbomify.com/CVE-2026-109377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109377
- OSV: https://osv.dev/vulnerability/CVE-2026-109377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109377/
Summaries are generated and may contain mistakes; the official description above is the record.