NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
318 matching advisories · page 1 of 11Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-129972 A buffer overflow vulnerability exists in the web management service of the Ethernet Remote I/Os products. Moxa · ioLogik E1200 Series 33 hours ago high8.7 CVE-2026-129971 A buffer overflow vulnerability exists in the SNMP service of the Ethernet Remote I/Os products.... Moxa · ioLogik E1200 Series 33 hours ago high8.6 CVE-2026-130494 An improper firmware authenticity verification vulnerability exists in the affected Ethernet Switches products. Moxa · EDS-510E Series 34 hours ago high7.7 CVE-2026-130493 A hard-coded cryptographic key vulnerability exists in affected Ethernet swiches. The use of a... Moxa · EDS-510E Series 34 hours ago medium5.3 CVE-2026-111548 A stack-based buffer overflow vulnerability exists in the web management interface of affected Moxa wireless device servers. 25 days ago high7.6 CVE-2026-111459 An improper certificate validation vulnerability exists in Moxa Remote Connect Suite (MRC Client). 25 days ago high8.6 CVE-2026-109813 A hard-coded cryptographic key vulnerability exists in the `/usr/bin/sysman` of some of Moxa's industrial computing products. 37 days ago medium6.9 CVE-2026-109812 A missing authorization vulnerability exists in the internal API `/api/v1/secrets/` of some of Moxa's industrial computing products. 37 days ago high7.1 CVE-2026-10825 A denial-of-service vulnerability exists in the WebSocket API due to insufficient validation and handling of JSON-based requests. Moxa · NPort 6000-G2 Series 2026-06-16 high7.0 CVE-2026-9266 A Missing Required Cryptographic Step vulnerability has been identified in Moxa's embedded Linux firmware for industrial computers and controllers. 2026-06-12 high8.7 CVE-2026-3868 An improper handling of the length parameter inconsistency vulnerability has been identified in Moxa’s Secure Router. Moxa · EDR-8010 Series, Moxa · EDR-G9010 Series 2026-04-27 medium6.0 CVE-2026-3867 An improper ownership management vulnerability has been identified in Moxa’s Secure Router. Moxa · EDR-8010 Series, Moxa · EDR-G9010 Series 2026-04-27 high7.0 CVE-2026-4483 An exposed IOCTL with an insufficient access control vulnerability has been identified in the utility, MxGeneralIo, for Moxa’s industrial x86 computers. 2026-04-08 medium6.8 CVE-2026-0715 Moxa Arm-based industrial computers running Moxa Industrial Linux Secure use a device-unique bootloader password provided on the device. moxa · uc-1222a_firmware, moxa · uc-2222a-t-us_firmware, moxa · uc-2222a-t_firmware +9 2026-02-05 medium6.8 CVE-2026-0714 A physical attack vulnerability exists in certain Moxa industrial computers using TPM-backed LUKS full-disk encryption on Moxa Industrial Linux 3, where the di… moxa · uc-1222a_firmware, moxa · uc-2222a-t-us_firmware, moxa · uc-2222a-t_firmware +9 2026-02-05 unscored CVE-2025-1680 An acceptance of extraneous untrusted data with trusted data vulnerability has been identified in Moxa’s Ethernet switches, which allows attackers with adminis… 2025-10-23 medium4.8 CVE-2025-1679 Cross-site Scripting has been identified in Moxa’s Ethernet switches, which allows an authenticated administrative attacker to inject malicious scripts to an a… 2025-10-23 critical9.9 CVE-2025-6950 An Use of Hard-coded Credentials vulnerability has been identified in Moxa’s network security appliances and routers. 2025-10-17 critical9.3 CVE-2025-6949 An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. 2025-10-17 medium5.3 CVE-2025-6894 An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. 2025-10-17 critical9.3 CVE-2025-6893 An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. 2025-10-17 high8.7 CVE-2025-6892 An Incorrect Authorization vulnerability has been identified in Moxa’s network security appliances and routers. 2025-10-17 medium5.5 CVE-2022-50268 In the Linux kernel, the following vulnerability has been resolved: mmc: moxart: fix return value check of mmc_add_host() mmc_add_host() may return error, if w… linux · linux_kernel 2025-09-15 high7.3 CVE-2025-5191 An Unquoted Search Path vulnerability has been identified in the utility for Moxa’s industrial computers (Windows). 2025-08-25 high8.6 CVE-2025-0676 This vulnerability involves command injection in tcpdump within Moxa products, enabling an authenticated attacker with console access to exploit improper input… 2025-04-02 critical9.2 CVE-2024-12297 Moxa’s Ethernet switch is vulnerable to an authentication bypass because of flaws in its authorization mechanism. 2025-01-15 critical9.8 CVE-2024-9140 Moxa’s cellular routers, secure routers, and network security appliances are affected by a critical vulnerability, CVE-2024-9140. 2025-01-03 high7.2 CVE-2024-9138 Moxa’s cellular routers, secure routers, and network security appliances are affected by a high-severity vulnerability, CVE-2024-9138. 2025-01-03 medium5.3 CVE-2024-4740 MXsecurity software versions v1.1.0 and prior are vulnerable because of the use of hard-coded credentials. moxa · mxsecurity 2024-10-18 medium5.3 CVE-2024-4739 The lack of access restriction to a resource from unauthorized users makes MXsecurity software versions v1.1.0 and prior vulnerable. moxa · mxsecurity 2024-10-18

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.