# CVE-2026-61747: Missing authorization in InvenTree

> Authenticated users can access other users' imported data and column mappings via IDOR in the data-import API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-xjpv-cwpw-7qx8

## What is CVE-2026-61747?

CVE-2026-61747 is a medium-severity missing authorization vulnerability in InvenTree, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

InvenTree is an Open Source Inventory Management System. Prior to 1.4.0, the /api/importer/row/ and /api/importer/mapping/ endpoints do not scope DataImportRow and DataImportColumnMap querysets to the owner of the associated DataImportSession. Any authenticated user, including an account with no assigned roles, can supply another user's import session identifier and retrieve that session's row_data and data fields together with its column mappings. This exposes the full contents of data staged for import across users, although the InvenTree threat model treats authenticated instance users as trusted. This issue is fixed in version 1.4.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-61747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61747 is a medium-severity missing authorization vulnerability in InvenTree, published on 21 Sep 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-61747 in the wild and no public exploit code.

Affected product: InvenTree. 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-61747/ (Markdown: https://insights.sbomify.com/CVE-2026-61747/index.md)
```

## Sources

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

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