NetSight

Security Dashboard

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

Reset
65 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-18616 A vulnerability was identified in GL-iNet GL-MT3000 up to 4.4.5. GL-iNet GL-MT3000 2026-08-03 critical9.8 CVE-2026-18615 A vulnerability was determined in GL-iNet GL-MT3000 up to 4.4.5. GL-iNet GL-MT3000 2026-08-03 critical9.8 CVE-2026-18614 A vulnerability was found in GL-iNet GL-MT3000 up to 4.4.5. GL-iNet GL-MT3000 2026-08-03 critical9.8 CVE-2026-18613 A vulnerability has been found in GL-iNet GL-MT3000 up to 4.4.5. GL-iNet GL-MT3000 2026-08-03 critical9.8 CVE-2026-18612 A flaw has been found in GL-iNet GL-MT3000 up to 4.4.5. GL-iNet GL-MT3000 2026-08-03 low3.7 CVE-2026-32293 The GL-iNet Comet (GL-RM1) KVM connects to a GL-iNet site during boot-up to provision client and CA certificates. gl-inet · comet_gl-rm1_firmware 2026-03-17 high7.5 CVE-2026-32292 The GL-iNet Comet (GL-RM1) KVM web interface does not limit login requests, enabling brute-force attempts to guess credentials. gl-inet · comet_gl-rm1_firmware 2026-03-17 medium6.8 CVE-2026-32291 The GL-iNet Comet (GL-RM1) KVM before 1.8.2 does not require authentication on the UART serial console. gl-inet · comet_gl-rm1_firmware 2026-03-17 medium4.7 CVE-2026-32290 The GL-iNet Comet (GL-RM1) KVM before version 1.8.2 does not sufficiently verify the authenticity of uploaded firmware files. gl-inet · comet_gl-rm1_firmware 2026-03-17 critical9.8 CVE-2026-26793 GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the set_config function. gl-inet · ar300m16_firmware 2026-03-12 critical9.8 CVE-2026-26795 GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the module parameter in the M.get_system_log function. gl-inet · ar300m16_firmware 2026-03-12 high8.8 CVE-2026-26794 GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a SQL injection vulnerability via the add_group() function. gl-inet · ar300m16_firmware 2026-03-12 critical9.8 CVE-2026-26792 GL-iNet GL-AR300M16 v4.3.11 was discovered to contain multiple command injection vulnerabilities in the set_upgrade function via the modem_url, target_version,… gl-inet · ar300m16_firmware 2026-03-12 critical9.8 CVE-2026-26791 GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the string port parameter in the enable_echo_server function. gl-inet · ar300m16_firmware 2026-03-12 medium6.5 CVE-2025-67091 An issue in GL Inet GL.Inet AX1800 Version 4.6.4 & 4.6.8 are vulnerable. gl-inet · ax1800_firmware 2026-01-08 medium5.1 CVE-2025-67090 The LuCI web interface on Gl Inet GL.Inet AX1800 Version 4.6.4 & 4.6.8 are vulnerable. gl-inet · ax1800_firmware 2026-01-08 high8.1 CVE-2025-67089 A command injection vulnerability exists in the GL-iNet GL-AXT1800 router firmware v4.6.8. gl-inet · gl-axt1800_firmware 2026-01-08 high8.3 CVE-2025-44018 A firmware downgrade vulnerability exists in the OTA Update functionality of GL-Inet GL-AXT1800 4.7.0. 2025-11-24 high7.5 CVE-2025-25685 An issue was discovered in GL-INet Beryl AX GL-MT3000 v4.7.0. 2025-03-17 high7.5 CVE-2025-25684 A lack of validation in the path parameter (/download) of GL-INet Beryl AX GL-MT3000 v4.7.0 allows attackers to download arbitrary files from the device's file… 2025-03-17 high8.8 CVE-2024-45263 An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. gl-inet · mt6000_firmware, gl-inet · mt3000_firmware, gl-inet · mt2500_firmware +9 2024-10-24 high8.8 CVE-2024-45262 An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. gl-inet · mt2500_firmware, gl-inet · axt1800_firmware, gl-inet · ax1800_firmware +9 2024-10-24 high8.0 CVE-2024-45261 An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. gl-inet · mt2500_firmware, gl-inet · axt1800_firmware, gl-inet · ax1800_firmware +9 2024-10-24 high8.0 CVE-2024-45260 An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. gl-inet · mt6000_firmware, gl-inet · b1300_firmware, gl-inet · mt2500_firmware +9 2024-10-24 medium6.5 CVE-2024-45259 An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. gl-inet · mt3000_firmware, gl-inet · mt2500_firmware, gl-inet · axt1800_firmware +9 2024-10-24 high7.5 CVE-2024-28077 A denial-of-service issue was discovered on certain GL-iNet devices. gl-inet · mt6000_firmware, gl-inet · x3000_firmware, gl-inet · xe3000_firmware +9 2024-08-26 medium5.3 CVE-2024-39229 An issue in GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 … gl-inet · mt6000_firmware, gl-inet · a1300_firmware, gl-inet · x300b_firmware +9 2024-08-06 critical9.8 CVE-2024-39227 GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E75… gl-inet · mt6000_firmware, gl-inet · a1300_firmware, gl-inet · x300b_firmware +9 2024-08-06 critical9.8 CVE-2024-39228 GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E75… gl-inet · mt6000_firmware, gl-inet · a1300_firmware, gl-inet · x300b_firmware +9 2024-08-06 critical9.8 CVE-2024-39226 GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E75… gl-inet · mt6000_firmware, gl-inet · a1300_firmware, gl-inet · x300b_firmware +9 2024-08-06

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.