dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-7668

HIGH · 7.3 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds read vulnerability exists in the ASN1_STRING_data function within the SCEP Endpoint library (nova/lib/www/scep.p) of MikroTik RouterOS 6.49.8. The vulnerability is triggered via manipulation of the transactionID or messageType arguments, allowing remote attackers to read memory beyond allocated buffers.

MitigationUpgrade MikroTik RouterOS to the latest v6.x or v7.x version as recommended by the vendor. Prior to upgrading, ensure configuration backups are taken and plan for appropriate maintenance windows due to the public availability of exploits.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the RouterOS version
    Run '/system resource print' in RouterOS CLI or check 'System > Resources' in Winbox/WebFig. Alternatively, run '/system package update' to see the current version.
    Affected if Version is 6.49.8 or any version prior to it in the v6.x line, as this is the vulnerable release.
  2. Confirm the SCEP feature is enabled
    Navigate to IP > SCEP in Winbox/WebFig, or run '/scep print' in the CLI to check if SCEP is configured and active.
    Affected if SCEP is enabled and configured on the router, exposing the vulnerable endpoint.
  3. Check if the SCEP web endpoint is accessible
    Attempt to access 'http://<router-ip>/scep' or 'https://<router-ip>/scep' from an external or internal client. Also check '/tool fetch' against the SCEP URL.
    Affected if The SCEP endpoint (nova/lib/www/scep.p) responds to HTTP/HTTPS requests, indicating the vulnerable library is loaded and processing requests.
  4. Inspect SCEP request handling for transactionID or messageType
    If SCEP is enabled, review any available logs via '/log print' for SCEP-related entries, or capture traffic on the router interface to observe SCEP request parameters.
    Affected if The router processes SCEP requests containing transactionID or messageType parameters, which triggers the vulnerable code path in ASN1_STRING_data.

A user is affected if they are running MikroTik RouterOS v6.49.8 or earlier, have the SCEP feature enabled, and the SCEP web endpoint is accessible and can receive maliciously crafted transactionID or messageType arguments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MikroTik RouterOS to the latest v6.x or v7.x version as recommended by the vendor. Prior to upgrading, ensure configuration backups are taken and plan for appropriate maintenance windows due to the public availability of exploits.

Recommended fix Moderate confidence

Latest stable v6.x or v7.x MikroTik RouterOS (vendor recommends latest v6.x or v7.x as the issue is fixed in those releases)

  1. 1. Backup current RouterOS configuration using the /system backup save command or Dude backup if applicable
  2. 2. Download the latest stable MikroTik RouterOS from the official MikroTik download page (https://mikrotik.com/download)
  3. 3. Upload the RouterOS .npk file to the router via WinBox, WebFig, or FTP
  4. 4. Go to Files section in WinBox/WebFig and upload the new RouterOS .npk file
  5. 5. Reboot the router using /system reboot command
  6. 6. After reboot, verify the RouterOS version using /system resource print
  7. 7. Verify the SCEP endpoint is functioning correctly after upgrade
  8. 8. Restore configuration if needed from the backup created in step 1
Caveat RouterOS upgrades may introduce breaking changes; review MikroTik's changelog for the specific version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7668 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data