# CVE-2026-116677: OpenWISP Controller CA CRL REST API does not scope requests to managed organizations


- **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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-9gh4-xw24-9xh5

## What is CVE-2026-116677?

CVE-2026-116677 is a medium-severity vulnerability in openwisp-controller, published on 27 Oct 2026. 

### Official description

OpenWISP Controller is a network and WiFi controller for provisioning, configuration management, updates, and PKI management. From 1.0.0 until 1.3.2, the GET /api/v1/controller/ca/<integer-id>/crl endpoint allows an authenticated organization manager with CA view permission to retrieve another organization's certificate revocation list by requesting its sequential CA identifier. CrlDownloadView.retrieve resolves the CA directly instead of using the organization-scoped object retrieval enforced by FilterByOrganizationManaged, bypassing the endpoint's intended authorization boundary. The response can disclose CA issuer information and revoked certificate serial numbers, but it does not expose CA private keys or allow modification. This issue is fixed in version 1.3.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-116677 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116677 is a medium-severity vulnerability in openwisp-controller, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116677 in the wild and no public exploit code.

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

## Sources

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

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