# CVE-2026-120463: Warracker before 1.0.4 Missing Authorization via Paperless-ngx Document Linking


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-3h89-rqfj-5674, GHSA-xqgh-rxmq-pv66

## What is CVE-2026-120463?

CVE-2026-120463 is a medium-severity vulnerability in sassanix Warracker, published on 2 Nov 2026. 

### Official description

Warracker before 1.0.4 contains a missing authorization vulnerability in its Paperless-ngx integration that allows an authenticated, non-administrative user to bypass document ownership restrictions by searching for and linking another user's private document ID to a warranty they own using the `other` document type. Attackers can exploit insufficient authorization checks in the `paperless_search_and_link()` and `serve_paperless_document()` route handlers in file_routes.py to retrieve and disclose private documents belonging to another user via the shared Paperless-ngx API credential, resulting in unauthorized read access and confidentiality loss.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-120463 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120463 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120463 is a medium-severity vulnerability in sassanix Warracker, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120463 exists.

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

## Sources

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

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