# CVE-2025-56566: Information disclosure in n/a

> Attackers with physical access can extract cleartext credentials from SPI flash, enabling unauthorized access to MikroTik devices.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-cq56-4wxf-3742

## What is CVE-2025-56566?

CVE-2025-56566 is a medium-severity vulnerability in n/a, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MikroTik firmware 7.19.4 stores sensitive authentication credentials and network state in cleartext within non-volatile storage. An attacker with physical access to the device can extract this material from an SPI flash dump, without authenticating to the device and without knowledge of the administrative password.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-56566?


## How do I fix CVE-2025-56566?

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

## Is CVE-2025-56566 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56566 and fix it if it is affected.

What it is: CVE-2025-56566 is a medium-severity vulnerability in n/a, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56566 exists.

Affected product: n/a. 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-2025-56566/ (Markdown: https://insights.sbomify.com/CVE-2025-56566/index.md)
```

## Sources

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

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