CVE-2026-103903

waiting for further signalsZero needs more public information before it can validate it.

GHSA-23wm-v672-9cvc ↗EUVD-2026-97325 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
MikroTik RouterOS >= 7.0.0, < 7.24.5
fixed in 7.24.5
CWE-863 Incorrect Authorization
ETK-2026-1345Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 18h 04msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

MikroTik RouterOS WinBox authentication can assign the permissions of a different existing account to a logged-in low-privilege user. An attacker needs valid credentials for an account allowed to use WinBox and could obtain administrative access if a higher-privilege account exists.

mitigation

Upgrade MikroTik RouterOS to version 7.24.5. Until upgrades are complete, restrict WinBox access and disable it for accounts that do not require it.

fixed in 7.24.5

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.42%34th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 10:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-12 10:37Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103903

{
  "etk_id": "ETK-2026-1345",
  "cve_id": "CVE-2026-103903",
  "display_id": "CVE-2026-103903",
  "ghsa_id": "GHSA-23wm-v672-9cvc",
  "euvd_id": "EUVD-2026-97325",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in MikroTik RouterOS WinBox",
  "summary": "MikroTik RouterOS WinBox authentication can assign the permissions of a different existing account to a logged-in low-privilege user. An attacker needs valid credentials for an account allowed to use WinBox and could obtain administrative access if a higher-privilege account exists.",
  "mitigation": "Upgrade MikroTik RouterOS to version 7.24.5. Until upgrades are complete, restrict WinBox access and disable it for accounts that do not require it.",
  "vendor": "MikroTik",
  "product": "RouterOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, < 7.24.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.24.5"
      ],
      "package_name": "RouterOS",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0042,
  "epss_percentile": 0.3442,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.960197566666668,
  "t0_at": "2026-10-12T10:37:23.578000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T10:37:23.578000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T10:37:23.578000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103903"
    }
  }
}

published 2026-10-12 11:22Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.