Summary
OpenWISP Controller CA CRL REST API does not scope requests to managed organizations
The authenticated REST API endpoint for downloading a CA Certificate Revocation List resolves the requested CA without applying the organization-scoped queryset used by the rest of the PKI API.
An organization manager with CA view permission can request another organization's sequential CA ID and receive that CA's CRL. The endpoint is intended to be authenticated and organization-scoped, so it should use the same access-control path as GET /api/v1/controller/ca/<id>/.
Affected endpoint
GET /api/v1/controller/ca/<integer-id>/crl
CrlDownloadView inherits ProtectedAPIMixin, which requires an authenticated organization manager with the relevant model permission. However, retrieve() resolves the CA with get_object_or_404(Ca, pk=kwargs["pk"]). This bypasses FilterByOrganizationManaged and does not perform an object-level permission check.
Consequently, a manager of organization A can enumerate CA integer IDs and retrieve the CRL for a CA belonging to organization B. The sibling CA detail endpoint is correctly organization-scoped and returns 404 for the same cross-organization request.
Impact
The endpoint returns only the CRL, including CA issuer information and revoked certificate serial numbers. It does not disclose CA private keys and does not permit modification.
django-x509 exposes CRLs publicly by default unless DJANGO_X509_CRL_PROTECTED = True. Therefore, the default configuration does not gain a new confidentiality exposure from this REST API behavior. Nonetheless, the endpoint is part of the authenticated, organization-scoped REST API and does not enforce its intended authorization boundary.
Deployments that explicitly protect CRLs have a stronger expectation that this endpoint will scope access to the requester's managed organizations. The practical impact is low, but the authorization behavior should be corrected for consistency and defense in depth.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Resolve the CA through the view's organization-scoped queryset. Set queryset = Ca.objects.all(), replace the direct get_object_or_404(Ca, pk=kwargs["pk"]) lookup with self.get_object(), and add a regression test that a same-organization manager receives 200 while a manager of another organization receives 404.
Frequently Asked Questions
- What is CVE-2026-116677? CVE-2026-116677 is a medium-severity missing authorization vulnerability in openwisp-controller (pip), affecting versions >= 1.0.0, < 1.3.2. It is fixed in 1.3.2. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of openwisp-controller are affected by CVE-2026-116677? openwisp-controller (pip) versions >= 1.0.0, < 1.3.2 is affected.
- Is there a fix for CVE-2026-116677? Yes. CVE-2026-116677 is fixed in 1.3.2. Upgrade to this version or later.
- Is CVE-2026-116677 exploitable, and should I be worried? Whether CVE-2026-116677 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-116677 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-116677? Upgrade
openwisp-controllerto 1.3.2 or later.