Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-67281 – Unauthenticated File Read – MikroTik RouterOS 6.0.0–6.49.20, 7.0.0–7.23.3, 7.24–7.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-67281 is an unauthenticated file-disclosure vulnerability in MikroTik RouterOS’s WebFig web management interface, specifically in the /jsproxy handler. The flaw stems from an uninitialized pointer that RouterOS can be tricked into using for file-access authorization, allowing a remote, unauthenticated attacker to read root-owned files — including configuration files that contain credentials. The issue carries a CVSS score of 8.7 (High) and affects all currently deployed RouterOS release branches (v6 and v7) prior to the patched versions.

Technical details

  • Root cause: A newly allocated WebFig session retains a stale, uninitialized "principal" pointer that is later dereferenced by the /jsproxy file-serving code path to authorize file access (CWE-824: Access of Uninitialized Pointer).
  • Trigger conditions: An attacker who can influence memory allocator behavior can cause the uninitialized pointer to resolve to a principal with elevated file-access rights.
  • Attack vector: By supplying parent-directory (../) traversal components inside an encrypted WebFig URI, the attacker escapes the intended WebFig file namespace (CWE-22: Path Traversal) and reads arbitrary files on the device.
  • Impact: Disclosure of root-owned files, including configuration stores that contain credentials — with no authentication and no user interaction required. The vulnerability affects confidentiality only; no direct impact on integrity or availability was reported.

Affected software

  • MikroTik RouterOS 7.24.x prior to 7.24.2 (Stable)
  • MikroTik RouterOS 7.0.0 through 7.23.3 (fixed in 7.23.4, Long-term)
  • MikroTik RouterOS 6.0.0 through 6.49.20 (fixed in 6.49.21, Long-term)

Exposure requires the WebFig service to be reachable by an attacker (e.g., exposed to the internet or an untrusted network).

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • Network attack vector, low attack complexity, no privileges or user interaction required, high impact to confidentiality.

Mitigation and recommended actions

  • Immediate: Upgrade RouterOS to one of the fixed releases:
    • 6.49.21 (Long-term)
    • 7.23.4 (Long-term)
    • 7.24.2 (Stable)
    • Any subsequent release incorporating these fixes (e.g., 7.25 beta builds)
  • If patching is not immediately possible:
    • Do not expose WebFig, Winbox, or SSH management interfaces directly to the internet or untrusted networks.
    • Restrict access to management services using firewall rules limited to trusted management networks/hosts.
    • Use a VPN for remote administrative access instead of exposing management ports.
    • Segment administrative interfaces onto isolated VLANs where feasible.
  • After upgrading: Review device configuration for unauthorized users, scripts, or scheduler entries, and rotate any credentials that may have been stored on the device, since exploitation could have disclosed configuration files containing credentials prior to patching.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge