> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/other/changelog/mikopbx-2026.8.2.md).

# MikoPBX 2026.8.2

Changes since MikoPBX 2026.6.99

The main focus of MikoPBX 2026.8.2 is security and fixes after 2026.6.99. Vulnerabilities in module access rights, provider settings, and DHCP response handling have been fixed. Forwarding to voicemail, Busy, and Hangup works again, modules can be installed from the marketplace again, and the click at the start of prompts and music on hold is gone.

{% hint style="warning" %}
Back up the PBX before updating. After the update, web interface users need to sign in again once. When updating from 2026.5.6, upload the IMG image manually. For PBXs installed before 2026.1.1, use the IMG-legacy image.
{% endhint %}

<figure><img src="https://835495363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ8acWnNlSalIHQjMFu1%2Fuploads%2Fgit-blob-fb25fbace6f414ccd446874207d4174ea6406e65%2Fmikopbx-2026.8.2-header.png?alt=media" alt="MikoPBX 2026.8.2"><figcaption></figcaption></figure>

### Security

A user with a restricted role can no longer call module actions without permission. The module menu item form can no longer be used to change system settings or inject markup into the menu.

Values in provider settings and off-work calendar settings can no longer change the telephony configuration behind the interface. Routes received from a DHCP server are validated: a forged reply on the local network can no longer run commands on the PBX.

Each PBX now gets its own login session encryption key. Employee CSV import data, including phone passwords, is kept in a protected location and deleted after an hour. On internal errors, the interface shows a generic message without service details.

### Calls and sound

Forwarding to voicemail, Busy, Hangup, and DID to User works again. Previously, the call kept ringing the employee instead of being forwarded. These options are available again in the selectors of incoming routes, IVR menus, queues, and forwarding.

The click at the start of IVR menus, system prompts, and music on hold has been removed. Existing files are repaired automatically when the PBX starts.

Music on hold plays again on new installs. If you delete all your own tracks, the PBX uses the built-in set.

### Modules

Installing modules from the marketplace works again.

### Network filters and access

A network filter used by an employee, provider, AMI user, or API key can no longer be deleted. Previously, deleting the filter removed the address restriction from such records.

API keys with a network filter work from the permitted networks again. Previously, they were rejected from any address.

In LXC containers, banned addresses are now actually blocked from the web interface, and the whitelist applies right after a restart.

### Other fixes

New installs no longer try to send notifications through an unconfigured mail server. Disks and partitions are detected correctly even when there are more than nine of them or their names are similar.

### Update notes

If an employee, provider, AMI user, or API key was bound to a network filter that has already been deleted, after the update it can connect only from local addresses. Each such record is listed in the system log - assign the right filter to it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mikopbx.com/mikopbx/english/other/changelog/mikopbx-2026.8.2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
