# CVE-2026-19829: 648540858 wvp-GB28181-pro Log File Download Endpoint LogController.java path traversal

> Remote attackers can exploit a path traversal flaw in the log download endpoint to read arbitrary files from the server.

- **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/E:P`)
- **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:** 14 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-wp6f-xq4p-r9fp

## What is CVE-2026-19829?

CVE-2026-19829 is a medium-severity path traversal vulnerability in 648540858 wvp-GB28181-pro, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in 648540858 wvp-GB28181-pro 2.7.4-20260107. This vulnerability affects unknown code of the file LogController.java of the component Log File Download Endpoint. The manipulation of the argument fileName results in path traversal. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

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

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


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

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

## Is CVE-2026-19829 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19829 is a medium-severity path traversal vulnerability in 648540858 wvp-GB28181-pro, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19829 exists.

Affected product: 648540858 wvp-GB28181-pro. 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-19829/ (Markdown: https://insights.sbomify.com/CVE-2026-19829/index.md)
```

## Sources

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

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