NetSight

Security Dashboard

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

Reset
64 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.3 CVE-2026-124577 A weakness has been identified in Intelbras SG 2404 PoE L2+ 1.00.70/1.00.72. The affected element... Intelbras · SG 2404 PoE L2+ 12 days ago low3.1 CVE-2026-101265 A vulnerability was identified in Intelbras TIP 125i 4.3.35/4.3.41. 54 days ago low2.7 CVE-2026-12211 A flaw has been found in Intelbras iNVU 7016 FT 3.004.00IB000.0.T Build 2025-09-26. 2026-06-15 medium5.3 CVE-2026-36438 An issue in Intelbras VIP-1230-D-G4 Version V2.800.00IB00C.0.T allows a remote attacker to obtain sensitive information via password reset functionality under … 2026-05-18 high8.7 CVE-2019-25472 IntelBras Telefone IP TIP200 and 200 LITE contain an unauthenticated arbitrary file read vulnerability in the dumpConfigFile function accessible via the cgiSer… Intelbras · Telefone IP TIP 200, Intelbras · Telefone IP TIP 200 LITE 2026-03-11 medium6.3 CVE-2026-3101 A vulnerability was found in Intelbras TIP 635G 1.12.3.5. intelbras · tip_635g_firmware 2026-02-24 high8.1 CVE-2026-2564 A security flaw has been discovered in Intelbras VIP 3260 Z IA 2.840.00IB005.0.T. 2026-02-16 high7.5 CVE-2020-36963 Intelbras Router RF 301K firmware version 1.1.2 contains an authentication bypass vulnerability that allows unauthenticated attackers to download router config… 2026-01-28 high8.2 CVE-2025-67070 A vulnerability exists in Intelbras CFTV IP NVD 9032 R Ftd V2.800.00IB00C.0.T, which allows an unauthenticated attacker to bypass the multi-factor authenticati… 2026-01-09 medium5.3 CVE-2025-13221 A weakness has been identified in Intelbras UnniTI 24.07.11. 2025-11-15 medium5.3 CVE-2025-13187 A security vulnerability has been detected in Intelbras ICIP 2.0.20. intelbras · icip_30_firmware 2025-11-14 high8.4 CVE-2025-55976 Intelbras IWR 3000N 1.9.8 exposes the Wi-Fi password in plaintext via the /api/wireless endpoint. intelbras · iwr_3000n_firmware 2025-09-10 high7.3 CVE-2025-26065 A cross-site scripting (XSS) vulnerability in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows attackers to execute arbitrary web scripts or HTML via injectin… intelbras · rx_1500_firmware, intelbras · rx_3000_firmware 2025-08-04 low3.1 CVE-2025-8515 A weakness has been identified in Intelbras InControl 2.21.60.9. intelbras · incontrol_web 2025-08-04 high7.3 CVE-2025-26064 A cross-site scripting (XSS) vulnerability in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows attackers to execute arbitrary web scripts or HTML via injectin… intelbras · rx_1500_firmware, intelbras · rx_3000_firmware 2025-07-31 critical9.8 CVE-2025-26063 An issue in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows unauthenticated attackers to execute arbitrary code via injecting a crafted payload into the ESSI… intelbras · rx_1500_firmware, intelbras · rx_3000_firmware 2025-07-31 critical9.8 CVE-2025-26062 An access control issue in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows unauthenticated attackers to access the router's settings file and obtain potentia… intelbras · rx_1500_firmware, intelbras · rx_3000_firmware 2025-07-31 low2.7 CVE-2025-7061 A vulnerability was found in Intelbras InControl up to 2.21.60.9. intelbras · incontrol_web 2025-07-04 medium6.5 CVE-2025-50405 Intelbras RX1500 Router v2.2.17 and before is vulnerable to Incorrect Access Control in the FirmwareUpload function and GetFirmwareValidation function. intelbras · rx_1500_firmware 2025-07-01 medium5.3 CVE-2025-50404 Intelbras RX1500 Router v2.2.17 and before is vulnerable to Integer Overflow. intelbras · rx_1500_firmware 2025-07-01 medium6.3 CVE-2025-6765 A vulnerability, which was classified as critical, has been found in Intelbras InControl 2.21.60.9. intelbras · incontrol_web 2025-06-27 low2.4 CVE-2025-4996 A vulnerability, which was classified as problematic, has been found in Intelbras RF 301K 1.1.5. 2025-05-20 low2.7 CVE-2025-4286 A vulnerability was found in Intelbras InControl up to 2.21.59. intelbras · incontrol_web 2025-05-05 low2.4 CVE-2025-3157 A vulnerability was found in Intelbras WRN 150 1.0.15_pt_ITB01. 2025-04-03 low3.7 CVE-2025-0784 A vulnerability has been found in Intelbras InControl up to 2.21.58 and classified as problematic. intelbras · incontrol_web 2025-01-28 medium4.3 CVE-2024-12897 A vulnerability was found in Intelbras VIP S3020 G2, VIP S4020 G2, VIP S4020 G3 and VIP S4320 G2 up to 20241222. 2024-12-23 medium5.3 CVE-2024-12896 A vulnerability was found in Intelbras VIP S3020 G2, VIP S4020 G2, VIP S4020 G3 and VIP S4320 G2 up to 20241222 and classified as problematic. 2024-12-22 high7.8 CVE-2024-9325 A vulnerability classified as critical has been found in Intelbras InControl up to 2.21.56. intelbras · incontrol_web 2024-09-29 medium6.3 CVE-2024-9324 A vulnerability was found in Intelbras InControl up to 2.21.57. intelbras · incontrol_web 2024-09-29 high7.8 CVE-2024-6080 A vulnerability classified as critical was found in Intelbras InControl 2.21.56. intelbras · incontrol 2024-06-17

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.