2026-10-19 21:52 CEST · Intelligence refreshed (Europe/Stockholm)
Understand software risk, with the evidence visible.
Search software, operating systems, packages, CVEs, KBs, campaigns, advisories, named operations or GHSAs and review correlated vulnerability, campaign, advisory, exploitation, update, affected-product and lifecycle intelligence in one place.
Latest synchronized CVE
CVSS 5.5Published 2026-10-19 20:42 CEST
Vendor
Affected products · · · ·
5 affected products/devices5 operating system
General vulnerability queryRecent High & critical CVEs
Query the vulnerability time window. Default 7 days; narrow to the last 24 hours or expand to 14 or 30 days when needed.
CVSS 8.7/10High severity
First published: 22 September 2026, 19:07 CEST · Last modified: 1 October 2026, 17:21 CEST
CVE lookup — correlated security and lifecycle intelligence
· 8 sources correlated
Important — plan remediation
MikroTik RouterOS < 7.25beta4 Improper Input Validation DoS via BGP Labelled-VPN NLRI
SeverityCVSS 8.7High · Remote / network
ExploitationNone reportedEPSS 0.5% chance in 30 days
MikroTik RouterOS before 7.25beta4 contains an improper input validation vulnerability in the labelled-VPN NLRI iterators of the routing service that allows an unauthenticated on-path attacker to crash the BGP service by sending a malformed MP_REACH_NLRI UPDATE message with a prefix-length value below the minimum valid for a labelled-VPN NLRI, which passes validation while describing a route with a negative-length address portion. Attackers can repeatedly send a single BGP UPDATE packet carrying a VPNv4 or VPNv6 N…
Detailed evidence Everything below supports the summary above. Open only what you need.
Direct intelligence-source lanes: every lane below has direct evidence for
in that Scantide intelligence collection. Lanes share the CVE as their join key; their presence together does not imply that one source explicitly referenced another source's record.
These vendors are derived from affected product/device evidence tied to this CVE. This is intentionally separate from the direct intelligence-source lanes above: a vendor can have affected products without Scantide having a vendor-specific advisory or Microsoft KB record for the CVE.
1 affected vendors represented
Affected software, operating systems, hardware and devices 5
Deduplicated across Scantide's structured CVE, NVD applicability, CSAF, vendor advisory, campaign and downstream product evidence. Taxonomy IDs and evidence-only identifiers are excluded from the asset count. Counts represent relationships Scantide can currently prove, not the theoretical maximum downstream ecosystem.
MikroTik RouterOS before 7.25beta4 contains an improper input validation vulnerability in the labelled-VPN NLRI iterators of the routing service that allows an unauthenticated on-path attacker to crash the BGP service by sending a malformed MP_REACH_NLRI UPDATE message with a prefix-length value below the minimum valid for a labelled-VPN NLRI, which passes validation while describing a route with a negative-length address portion. Attackers can repeatedly send a single BGP UPDATE packet carrying a VPNv4 or VPNv6 NLRI with an out-of-bounds prefix-length to indefinitely hold down the BGP plane, causing session termination without a NOTIFICATION and triggering a service malfunction on the device.
Only sources that directly identify or describe the queried CVE are shown here. Historical examples from MITRE CWE definitions are kept in the weakness section and are not presented as related CVEs.
Affected-product scope: The product/device count is the deduplicated set Scantide can prove from its currently ingested structured records and advisory text. It is not a claim that only those products were affected; component vulnerabilities such as Log4Shell can have a much larger downstream ecosystem. Advisory and vendor references are kept clickable so additional downstream exposure can be followed to the authoritative source.
Coverage note: Scantide correlates multiple public and locally indexed intelligence sources, but no dataset or matching process is complete. Results may omit software, dependencies, affected versions or advisories, and related records do not by themselves prove that a specific installation is vulnerable. Confirm important findings against vendor guidance and the installed product and version.