# CVE-2026-70381: Unauthorized Access to Internal Web Resources


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-vrqh-rf2x-2whg

## What is CVE-2026-70381?

CVE-2026-70381 is a medium-severity vulnerability in WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure Pro, published on 26 Oct 2026. 

### Official description

An access-control vulnerability has been identified in the web server configuration. Some resources intended for on-device use only could be accessed remotely by an unauthenticated attacker with network access to the web interface.
The accessible resources do not expose credentials or provide administrative functionality, but may include non-public device content, such as screen-saver content or assets used by the web interface.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-70381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70381 is a medium-severity vulnerability in WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure Pro, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-70381 in the wild and no public exploit code.

Affected product: WolfVision Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini, Cynap Pure 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-70381/ (Markdown: https://insights.sbomify.com/CVE-2026-70381/index.md)
```

## Sources

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

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