NetSight

Security Dashboard

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

Reset
25 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-38718 InHand Networks IR912 V1.0.0.r20042 and IR915 V1.0.0.r20042 (including earlier versions) were discovered to contain a buffer overflow vulnerability in the devi… inhandnetworks · ir915l-fq39-s_firmware, inhandnetworks · ir912l-fq58_firmware 2026-06-18 high7.0 CVE-2023-22599 InHand Networks InRouter 302, prior to version IR302 V3.5.56, and InRouter 615, prior to version InRouter6XX-S-V2.3.0.r5542, contain vulnerability CWE-760: Use… inhandnetworks · inrouter302_firmware, inhandnetworks · inrouter615-s_firmware 2023-01-12 high7.2 CVE-2023-22598 InHand Networks InRouter 302, prior to version IR302 V3.5.56, and InRouter 615, prior to version InRouter6XX-S-V2.3.0.r5542, contain vulnerability CWE-78: Impr… inhandnetworks · inrouter302_firmware, inhandnetworks · inrouter615-s_firmware 2023-01-12 high8.8 CVE-2022-30543 A leftover debug code vulnerability exists in the console infct functionality of InHand Networks InRouter302 V3.5.45. inhandnetworks · ir302_firmware 2022-11-09 high8.1 CVE-2022-29888 A leftover debug code vulnerability exists in the httpd port 4444 upload.cgi functionality of InHand Networks InRouter302 V3.5.45. inhandnetworks · ir302_firmware 2022-11-09 high8.8 CVE-2022-28689 A leftover debug code vulnerability exists in the console support functionality of InHand Networks InRouter302 V3.5.45. inhandnetworks · ir302_firmware 2022-11-09 high8.8 CVE-2022-27172 A hard-coded password vulnerability exists in the console infactory functionality of InHand Networks InRouter302 V3.5.37. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26782 Multiple improper input validation vulnerabilities exists in the libnvram.so nvram_import functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26781 Multiple improper input validation vulnerabilities exists in the libnvram.so nvram_import functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26780 Multiple improper input validation vulnerabilities exists in the libnvram.so nvram_import functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26518 An OS command injection vulnerability exists in the console infactory_net functionality of InHand Networks InRouter302 V3.5.37. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26420 An OS command injection vulnerability exists in the console infactory_port functionality of InHand Networks InRouter302 V3.5.37. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26085 An OS command injection vulnerability exists in the httpd wlscan_ASP functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26075 An OS command injection vulnerability exists in the console infactory_wlan functionality of InHand Networks InRouter302 V3.5.37. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-26042 An OS command injection vulnerability exists in the daretools binary functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high7.2 CVE-2022-26007 An OS command injection vulnerability exists in the console factory functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high7.2 CVE-2022-26002 A stack-based buffer overflow vulnerability exists in the console factory functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.8 CVE-2022-25995 A command execution vulnerability exists in the console inhand functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · ir302_firmware 2022-05-12 high8.1 CVE-2022-21809 A file write vulnerability exists in the httpd upload.cgi functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · inrouter302_firmware 2022-05-12 high8.8 CVE-2022-21182 A privilege escalation vulnerability exists in the router configuration import functionality of InHand Networks InRouter302 V3.5.4. inhandnetworks · inrouter302_firmware 2022-05-12 high7.5 CVE-2022-27279 InHand Networks InRouter 900 Industrial 4G Router before v1.0.0.r11700 was discovered to contain an arbitrary file read via the function sub_177E0. inhandnetworks · inrouter_900_firmware 2022-04-10 high8.0 CVE-2021-38486 InHand Networks IR615 Router's Versions 2.3.0.r4724 and 2.3.0.r4870 cloud portal allows for self-registration of the affected product without any requirements … inhandnetworks · ir615_firmware 2021-10-19 high8.7 CVE-2021-38482 InHand Networks IR615 Router's Versions 2.3.0.r4724 and 2.3.0.r4870 website used to control the router is vulnerable to stored cross-site scripting, which may … inhandnetworks · ir615_firmware 2021-10-19 high8.7 CVE-2021-38468 InHand Networks IR615 Router's Versions 2.3.0.r4724 and 2.3.0.r4870 are vulnerable to stored cross-scripting, which may allow an attacker to hijack sessions of… inhandnetworks · ir615_firmware 2021-10-19 high8.8 CVE-2021-38466 InHand Networks IR615 Router's Versions 2.3.0.r4724 and 2.3.0.r4870 do not perform sufficient input validation on client requests from the help page. inhandnetworks · ir615_firmware 2021-10-19

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.