# CVE-2026-130867: GreaterWMS through 2.1.54 Unauthenticated Path Traversal via Static Asset Routes


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-pq36-w5vx-47p7

## What is CVE-2026-130867?

CVE-2026-130867 is a high-severity vulnerability in GreaterWMS, published on 17 Nov 2026. 

### Official description

GreaterWMS through 2.1.54 contains an unauthenticated path traversal vulnerability in the css, js, statics and fonts routes in greaterwms/views.py, which concatenate raw request.path_info without normalization. Attackers can send URL-encoded ../ sequences to read db.sqlite3 and obtain user openid tokens, enabling impersonation of any account.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

1 open source package ship an affected version, including greaterwms/greaterwms.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `greaterwms/greaterwms` | GitHub | `pkg:github/greaterwms/greaterwms` | All versions to 2.1.54 | None |

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

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

## Is CVE-2026-130867 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130867 is a high-severity vulnerability in GreaterWMS, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130867 in the wild and no public exploit code.

Affected packages and fixed versions:
- greaterwms/greaterwms (GitHub): affected all versions up to 2.1.54; no fix listed

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

## Sources

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

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