# CVE-2026-67281: Unauthenticated file read in Mikrotik RouterOS

> Unauthenticated attackers can read root-owned files, including credentials, via path traversal in the WebFig jsproxy interface.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-m7q3-cwh2-ffg5

## What is CVE-2026-67281?

CVE-2026-67281 is a high-severity path traversal vulnerability in Mikrotik Routeros, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RouterOS WebFig contains an unauthenticated file-read vulnerability in the /jsproxy path where a newly allocated session retains a stale uninitialized principal pointer used for file authorization. An unauthenticated attacker can prepare the allocator so that the file-serving path dereferences this pointer with sufficient rights, then supply parent-directory components in an encrypted URI to escape the WebFig file namespace and disclose root-owned files, including configuration stores containing credentials.This issue affects only 7.x branch was fixed in versions: 7.23.4 (Long-term) and 7.24.2 (Stable)

Weakness: CWE-824 (Access of Uninitialized Pointer), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Mikrotik Routeros.

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

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

## Is CVE-2026-67281 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67281 exists.

Public exploit code:

- https://github.com/sohel160/Webfig-jsproxy-unauthenticated-file-read-CVE-2026-67281- (github_poc): https://github.com/sohel160/Webfig-jsproxy-unauthenticated-file-read-CVE-2026-67281-

## Other vulnerabilities in Mikrotik Routeros

- [CVE-2018-7445](https://insights.sbomify.com/CVE-2018-7445/): MikroTik RouterOS Stack-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2026-86060](https://insights.sbomify.com/CVE-2026-86060/): MikroTik RouterOS Improper Neutralization of Argument Delimiters in a Command (critical 9.2, exploited in the wild)
- [CVE-2018-14847](https://insights.sbomify.com/CVE-2018-14847/): MikroTik Router OS Directory Traversal (critical 9.1, exploited in the wild)
- [CVE-2026-67277](https://insights.sbomify.com/CVE-2026-67277/): MikroTik RouterOS Missing Authentication for Critical Function (high 8.8, exploited in the wild)
- [CVE-2026-67279](https://insights.sbomify.com/CVE-2026-67279/): Mikrotik RouterOS Improper Enforcement of Behavioral Workflow (medium 6.9, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67281 is a high-severity path traversal vulnerability in Mikrotik Routeros, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67281 exists.

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

## Sources

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

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