NetSight

Security Dashboard

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

Reset
40 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2025-12603 /etc/timezone can be Arbitrarily Written.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-11-01 critical9.8 CVE-2025-12602 /etc/avahi/services/z9.service can be Arbitrarily Written.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-11-01 high7.5 CVE-2025-12601 Denial of Service Due to SlowLoris.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-11-01 critical9.8 CVE-2025-12600 Web UI Malfunction when setting unexpected locale via API.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-11-01 critical9.8 CVE-2025-12599 Multiple Devices are Sharing the Same Secrets for SDKSocket (TCP/5000).This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-11-01 critical9.8 CVE-2025-12554 Missing Security Headers.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-31 critical9.8 CVE-2025-12553 Email Server Certificate Verification Disabled.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-31 critical9.8 CVE-2025-12552 Insufficient Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-31 medium5.3 CVE-2025-12517 Credits Page not Matching Versions in Use in the FirmwareThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-30 critical9.8 CVE-2025-12516 Lack of Graceful Error Handling - HTTP 5xx ErrorThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-30 critical9.8 CVE-2025-12515 Systemic Internal Server Errors - HTTP 500 ResponseThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic4_firmware, azure-access · blu-ic2_firmware 2025-10-30 high8.8 CVE-2025-12479 Systemic Lack of Cross-Site Request Forgery (CSRF) Token Implementation.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-29 critical9.8 CVE-2025-12478 Non-Compliant TLS Configuration.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-29 critical9.8 CVE-2025-12477 Server Version Disclosure.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-29 critical9.8 CVE-2025-12476 Resource Lacking AuthN.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-29 high7.8 CVE-2025-12425 Local Privilege Escalation.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-28 critical9.8 CVE-2025-12424 Privilege Escalation through SUID-bit Binary.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-28 high7.5 CVE-2025-12423 Protocol manipulation might lead to denial of service.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 . azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-28 critical9.8 CVE-2025-12422 Vulnerable Upgrade Feature (Arbitrary File Write) may lead to obtaining super user permissions on board.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: th… azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-28 medium5.3 CVE-2025-12365 Error Messages Wrapped In HTTP Header.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-27 critical9.8 CVE-2025-12364 Weak Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-27 high7.5 CVE-2025-12363 Email Password Disclosure.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-27 critical9.8 CVE-2025-12285 Missing Initial Password Change.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-26 medium6.1 CVE-2025-12284 Lack of Input Validation in the web UI might lead to potential exploitation.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-26 medium6.5 CVE-2025-12278 Logout Functionality not Working.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-26 critical9.8 CVE-2025-12275 Mail Configuration File Manipulation + Command Execution.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-26 high8.8 CVE-2025-12221 Busybox 1.31.1 - Multiple Known Vulnerabilities.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-25 critical9.8 CVE-2025-12220 Busybox 1.31.1 - Multiple Known Vulnerabilities.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-25 critical9.8 CVE-2025-12219 Vulnerable Components in Azure Access OS.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-25 critical9.1 CVE-2025-12218 Weak Default Credentials.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5. azure-access · blu-ic2_firmware, azure-access · blu-ic4_firmware 2025-10-25

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.