dbcve.org
RouterosOperating system · Mikrotik

CVE-2025-6443

HIGH · 7.2 CVSS v3.0 Published 2025-06-25
Fix available
A fix is available. Upgrade to 7.20 or later.
See remediation →
81/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
Mikrotik RouterOS VXLAN Source IP Improper Access Control Vulnerability. This vulnerability allows remote attackers to bypass access restrictions on affected installations of Mikrotik RouterOS. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of remote IP addresses when processing VXLAN traffic. The issue results from the lack of validation of the remote IP address against configured values prior to allowing ingress traffic into the internal network. An attacker can leverage this vulnerability to gain access to internal network resources. Was ZDI-CAN-26415.

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

Mikrotik RouterOS fails to validate remote IP addresses against configured allowlists when processing VXLAN traffic. This allows unauthenticated remote attackers to bypass access controls and inject traffic into internal networks by spoofing source IP addresses in VXLAN packets.

MitigationValidate all remote IP addresses against configured VXLAN peer lists before allowing ingress; update RouterOS to latest stable version if patch available; implement IP-based ACLs on VXLAN interfaces.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RouterosOperating system
Affected:< 7.20

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check RouterOS version
    Run '/system resource print' in RouterOS CLI or check via Winbox/SecHub. Look for 'version' in the output.
    Affected if Version is below 7.20 (e.g., 7.19.x, 7.18.x, etc.)
  2. Verify VXLAN interface is configured
    Run '/interface vxlan print' in RouterOS CLI to list all VXLAN interfaces.
    Affected if Any VXLAN interface exists and is enabled (vlan-id present and running)
  3. Inspect VXLAN remote peer configuration
    Run '/interface vxlan print detail' and check for 'remote' or 'remote-address' entries. Also run '/interface vxlan vlan' to check VLAN bindings.
    Affected if VXLAN peers are configured but the router accepts traffic from ANY remote IP rather than only from the configured peer list
  4. Confirm IP validation is bypassed
    Send a VXLAN packet with a spoofed source IP that is NOT in the configured peer list. Capture traffic on the VXLAN interface to verify the packet is processed despite the source IP being unauthorized.
    Affected if Packets with spoofed/unlisted source IP addresses are accepted and processed by the VXLAN interface

You are affected if RouterOS version is below 7.20 AND VXLAN is enabled with peer list configuration, because the router fails to validate incoming VXLAN traffic against the configured allowlist.

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
Upgrade available Upgrade to 7.20 or later
Fixed in 7.20
Interim mitigation

Validate all remote IP addresses against configured VXLAN peer lists before allowing ingress; update RouterOS to latest stable version if patch available; implement IP-based ACLs on VXLAN interfaces.

Recommended fix High confidence

RouterOS 7.20 or later

  1. 1. Backup the current RouterOS configuration before performing any upgrade.
  2. 2. Download RouterOS version 7.20 or later 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. Reboot the router to apply the new RouterOS version.
  5. 5. After reboot, verify the router is running version 7.20 or later using the /system resource print command.
  6. 6. Verify that VXLAN configurations are still functioning correctly and that the remote IP access controls are now properly enforced.
Caveat Review release notes for any configuration changes between current version and 7.20; some legacy RouterOS packages may need to be reinstalled after upgrade

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

Fix this in Routeros Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6443 — 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-2025-6443 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