NetSight

Security Dashboard

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

Reset
3,104 matching advisories · page 12 of 104Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2025-21443 Memory corruption while processing message content in eAVB. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.8 CVE-2025-21442 Memory corruption while transmitting packet mapping information with invalid header payload size. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.8 CVE-2025-21441 Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver. qualcomm · fastconnect_7800_firmware, qualcomm · qca1062_firmware, qualcomm · qca1064_firmware +9 2025-04-07 high7.8 CVE-2025-21440 Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware +9 2025-04-07 high7.8 CVE-2025-21439 Memory corruption may occur while reading board data via IOCTL call when the WLAN driver copies the content to the provided output buffer. qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6900_firmware, qualcomm · qca6595au_firmware +9 2025-04-07 high7.8 CVE-2025-21438 Memory corruption while IOCTL call is invoked from user-space to read board data. qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6900_firmware +9 2025-04-07 high7.8 CVE-2025-21437 Memory corruption while processing memory map or unmap IOCTL operations simultaneously. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.8 CVE-2025-21436 Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads. qualcomm · fastconnect_7800_firmware, qualcomm · qmp1000_firmware, qualcomm · sm8735_firmware +9 2025-04-07 high7.5 CVE-2025-21435 Transient DOS may occur while parsing extended IE in beacon. qualcomm · ar8035_firmware, qualcomm · csr8811_firmware, qualcomm · fastconnect_6800_firmware +9 2025-04-07 high7.5 CVE-2025-21434 Transient DOS may occur while parsing EHT operation IE or EHT capability IE. qualcomm · qcs8300_firmware, qualcomm · qcs8550_firmware, qualcomm · qcs9100_firmware +9 2025-04-07 medium5.5 CVE-2025-21431 Information disclosure may be there when a guest VM is connected. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.5 CVE-2025-21430 Transient DOS while connecting STA to AP and initiating ADD TS request from AP to establish TSpec session. qualcomm · 315_5g_iot_modem_firmware, qualcomm · apq8017_firmware, qualcomm · apq8064au_firmware +9 2025-04-07 high7.5 CVE-2025-21429 Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request. qualcomm · sa9000p_firmware, qualcomm · sd626_firmware, qualcomm · sd660_firmware +9 2025-04-07 high7.3 CVE-2025-21425 Memory corruption may occur due top improper access control in HAB process. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.8 CVE-2025-21423 Memory corruption occurs when handling client calls to EnableTestMode through an Escape call. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware +9 2025-04-07 high7.8 CVE-2025-21421 Memory corruption while processing escape code in API. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware +9 2025-04-07 medium6.7 CVE-2024-49848 Memory corruption while processing multiple IOCTL calls from HLOS to DSP. qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware, qualcomm · qam8620p_firmware +9 2025-04-07 high7.8 CVE-2024-45557 Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation. qualcomm · ar8035_firmware, qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6900_firmware +9 2025-04-07 medium6.5 CVE-2024-45556 Cryptographic issue may arise because the access control configuration permits Linux to read key registers in TCSR. qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware, qualcomm · immersive_home_3210_platform_firmware +9 2025-04-07 high8.2 CVE-2024-45552 Information disclosure may occur during a video call if a device resets due to a non-conforming RTCP packet that doesn`t adhere to RFC standards. qualcomm · apq8064au_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware +9 2025-04-07 medium6.2 CVE-2024-45551 Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to … qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6800_firmware, qualcomm · fastconnect_6900_firmware +9 2025-04-07 high7.7 CVE-2024-45549 Information disclosure while creating MQ channels. qualcomm · sm8550p_firmware, qualcomm · sm8635_firmware, qualcomm · sm8635p_firmware +9 2025-04-07 medium6.6 CVE-2024-45544 Memory corruption while processing IOCTL calls to add route entry in the HW. qualcomm · c-v2x_9150_firmware, qualcomm · fastconnect_6800_firmware, qualcomm · fastconnect_6900_firmware +9 2025-04-07 medium6.6 CVE-2024-45543 Memory corruption while accessing MSM channel map and mixer functions. qualcomm · c-v2x_9150_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6800_firmware +9 2025-04-07 medium6.6 CVE-2024-45540 Memory corruption while invoking IOCTL map buffer request from userspace. qualcomm · c-v2x_9150_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6800_firmware +9 2025-04-07 high7.8 CVE-2024-43067 Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory. qualcomm · qca6391_firmware, qualcomm · qca6426_firmware, qualcomm · qca6436_firmware +9 2025-04-07 high7.8 CVE-2024-43066 Memory corruption while handling file descriptor during listener registration/de-registration. qualcomm · csrb31024_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6700_firmware +9 2025-04-07 high7.1 CVE-2024-43065 Cryptographic issues while generating an asymmetric key pair for RKP use cases. qualcomm · fastconnect_7800_firmware, qualcomm · qam8255p_firmware, qualcomm · qam8295p_firmware +9 2025-04-07 high7.8 CVE-2024-43058 Memory corruption while processing IOCTL calls. qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware, qualcomm · snapdragon_8_gen_1_mobile_platform_firmware +3 2025-04-07 medium5.5 CVE-2024-43046 There may be information disclosure during memory re-allocation in TZ Secure OS. qualcomm · csr8811_firmware, qualcomm · csra6620_firmware, qualcomm · csra6640_firmware +9 2025-04-07

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.