dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-10948

HIGH · 8.8 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 has been found in MikroTik RouterOS 7. This affects the function parse_json_element of the file /rest/ip/address/print of the component libjson.so. The manipulation leads to buffer overflow. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 7.20.1 and 7.21beta2 mitigates this issue. You should upgrade the affected component. The vendor replied: "Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out."

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

Buffer overflow vulnerability in the parse_json_element function within libjson.so of MikroTik RouterOS 7, affecting the /rest/ip/address/print REST API endpoint. The flaw allows remote attackers to overflow a buffer via crafted JSON input, achieving high severity (CVSS 8.8) with publicly available exploit code.

MitigationUpgrade RouterOS to version 7.20.1 (stable) or 7.21beta2 (beta) to patch the buffer overflow in libjson.so. Until upgrade is possible, restrict REST API access to trusted internal networks or disable the REST API if not needed.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
    Log into the router via CLI (terminal) or WinBox/WebFig, then run '/system/resource/print' to view the 'version' field, or check '/system/package/print' for the routeros package version
    Affected if The installed version is RouterOS 7.x and is earlier than 7.20.1 stable or 7.21beta2 (if beta channels are used)
  2. Verify if REST API service is enabled
    In the CLI, run '/ip service print' to list all IP services. Look for the 'rest' service entry and check if it is marked as 'enabled' (the 'disabled' column shows 'no')
    Affected if The REST API service is enabled (disabled=no)
  3. Confirm REST API network accessibility
    In the CLI, run '/ip service print detail' to see the 'address' and 'port' columns for the rest service. Check the 'address' field - if it shows '0.0.0.0/0' or a broad range, the REST API is internet-facing. Run '/ip firewall filter print' to verify no firewall rule blocks inbound traffic to the REST API port (typically 443 or 4433)
    Affected if The REST API is accessible from untrusted networks (address field shows 0.0.0.0/0 or broad ranges without adequate firewall protection)
  4. Check if the vulnerable endpoint is exposed
    If the REST API is enabled and accessible, verify that the endpoint '/rest/ip/address/print' can be reached. From an external host, attempt a minimal HTTP/HTTPS request to https://<router-ip>/rest/ip/address/print using a tool like curl (note: this requires valid REST API authentication tokens)
    Affected if The REST API is exposed and reachable from untrusted networks, allowing potential attackers to send crafted JSON payloads to the /rest/ip/address/print endpoint

A user is affected if they are running MikroTik RouterOS 7.x versions before 7.20.1 (or 7.21beta2) with the REST API service enabled and accessible from untrusted networks.

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 RouterOS to version 7.20.1 (stable) or 7.21beta2 (beta) to patch the buffer overflow in libjson.so. Until upgrade is possible, restrict REST API access to trusted internal networks or disable the REST API if not needed.

Recommended fix High confidence

RouterOS 7.20.1 (stable) or later

  1. 1. Backup the current RouterOS configuration using the /export command or through WinBox/WebFig
  2. 2. Download RouterOS 7.20.1 (stable) or later from the MikroTik download page (https://mikrotik.com/download)
  3. 3. Upload the .npk upgrade file to the router via Files menu in WinBox, WebFig, or FTP
  4. 4. Reboot the router using the /system reboot command
  5. 5. After reboot, verify the upgrade was successful by checking /system resource print to confirm the new version
Caveat RouterOS upgrades typically retain configuration but always backup before upgrading; some legacy packages may need reinstallation after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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