# CVE-2026-7668: MikroTik RouterOS SCEP Endpoint scep.p ASN1_STRING_data out-of-bounds

> Remote attackers can trigger an out-of-bounds read in the SCEP endpoint, potentially exposing memory or causing a crash.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-fqc2-7xh3-488w

## What is CVE-2026-7668?

CVE-2026-7668 is a medium-severity memory corruption vulnerability in MikroTik RouterOS, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in MikroTik RouterOS 6.49.8. This vulnerability affects the function ASN1_STRING_data in the library nova/lib/www/scep.p of the component SCEP Endpoint. The manipulation of the argument transactionID/messageType leads to out-of-bounds read. The attack may be initiated remotely. The exploit is publicly available and might be used. You should upgrade the affected component. The vendor recommends to "use the latest v6.x or 7.x MikroTik RouterOS version, the reported issue should be fixed there."

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-7668 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7668 is a medium-severity memory corruption vulnerability in MikroTik RouterOS, published on 2 May 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-7668 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-7668/ (Markdown: https://insights.sbomify.com/CVE-2026-7668/index.md)
```

## Sources

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

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