# CVE-2026-130865: wireguard_webadmin before 0.9981 Missing Authorization via Scheduler Views


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-h5wh-qmxh-4jf7

## What is CVE-2026-130865?

CVE-2026-130865 is a medium-severity vulnerability in eduardogsilva wireguard_webadmin, published on 17 Nov 2026. 

### Official description

wireguard_webadmin before 0.9981 contains a missing authorization vulnerability in scheduler/views.py that allows low-privilege authenticated users to manage peer schedules without Peer Manager level. View Only or Debugging Analyst users can create, modify, and delete schedule profiles and time slots to disable WireGuard peers or keep disabled peers off.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `eduardogsilva/wireguard_webadmin` | GitHub | `pkg:github/eduardogsilva/wireguard_webadmin` | All versions | 0.9981 |

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

Upgrade eduardogsilva/wireguard_webadmin to 0.9981 or later.

## Is CVE-2026-130865 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- eduardogsilva/wireguard_webadmin (GitHub): affected all versions; fixed in 0.9981

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

## Sources

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

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