# CVE-2026-14227: Insufficient session expiration in MikroTik RouterOS

> Authenticated users retain elevated permissions after group changes or timeouts, allowing unauthorized data access in MikroTik RouterOS devices.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-x9w7-jgwj-cp2f

## What is CVE-2026-14227?

CVE-2026-14227 is a medium-severity vulnerability in MikroTik RouterOS, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An API session‑management flaw in products with the MikroTik RouterOS API enabled are vulnerable to a Insufficient Session Expiration vulnerability. This could allow active sessions to retain their previous permission set after inactivity timeouts or user‑group changes. As a result, an authenticated user whose permissions have been reduced may continue accessing information.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-14227 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14227 is a medium-severity vulnerability in MikroTik RouterOS, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14227 in the wild and no public exploit code.

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

## Sources

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

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