NetSight

Security Dashboard

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

Reset
4,692 matching advisories · page 21 of 157Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2025-58485 Improper input validation in Samsung Internet prior to version 29.0.0.48 allows local attackers to inject arbitrary script. samsung · internet 2025-12-02 medium4.0 CVE-2025-58484 Incorrect default permissions in Samsung Cloud Assistant prior to version 8.0.03.8 allows local attacker to access partial data in sandbox. 2025-12-02 medium5.9 CVE-2025-58483 Improper export of android application components in Galaxy Store for Galaxy Watch prior to version 1.0.06.29 allows local attacker to install arbitrary applic… samsung · galaxy_store 2025-12-02 high7.3 CVE-2025-58482 Improper access control in MPLocalService of MotionPhoto prior to version 4.1.51 allows local attackers to start privileged service. samsung · motionphoto 2025-12-02 high7.3 CVE-2025-58481 Improper access control in MPRemoteService of MotionPhoto prior to version 4.1.51 allows local attackers to start privileged service. samsung · motionphoto 2025-12-02 medium4.3 CVE-2025-58480 Heap-based buffer overflow in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-12-02 medium4.3 CVE-2025-58479 Out-of-bounds read in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-12-02 medium4.3 CVE-2025-58478 Out-of-bounds write in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-12-02 medium4.3 CVE-2025-58477 Out-of-bounds write in parsing IFD tag in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-12-02 medium4.2 CVE-2025-58476 Out-of-bounds read vulnerability in bootloader prior to SMR Dec-2025 Release 1 allows physical attackers to access out-of-bounds memory. samsung · android 2025-12-02 medium5.6 CVE-2025-58475 Improper input validation in libsec-ril.so prior to SMR Dec-2025 Release 1 allows local privileged attackers to write out-of-bounds memory. samsung · android 2025-12-02 medium6.2 CVE-2025-21080 Improper export of android application components in Dynamic Lockscreen prior to SMR Dec-2025 Release 1 allows local attackers to access files with Dynamic Loc… samsung · android 2025-12-02 medium5.7 CVE-2025-21072 Out-of-bounds write in decoding metadata in fingerprint trustlet prior to SMR Dec-2025 Release 1 allows local privileged attackers to write out-of-bounds memor… samsung · android 2025-12-02 high7.5 CVE-2025-40129 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix null pointer dereference on zero-length checksum In xdr_stream_decode_opaque_au… 2025-11-12 high7.1 CVE-2025-48083 Cross-Site Request Forgery (CSRF) vulnerability in andriassundskard wpNamedUsers wpnamedusers allows Stored XSS.This issue affects wpNamedUsers: from n/a throu… wpNamedUsers: from n/a through 2025-11-06 high7.1 CVE-2025-21079 Improper input validation in Samsung Members prior to version 5.5.01.3 allows remote attackers to connect arbitrary URL and launch arbitrary activity with Sams… samsung · members 2025-11-05 high8.8 CVE-2025-21078 Use of insufficiently random value of secretKey in Smart Switch prior to version 3.7.68.6 allows adjacent attackers to access backup data from applications. samsung · smart_switch 2025-11-05 low3.3 CVE-2025-21077 Improper input validation in Samsung Email prior to version 6.2.06.0 allows local attackers to launch arbitrary activity with Samsung Email privilege. samsung · email 2025-11-05 medium5.5 CVE-2025-21076 Improper handling of insufficient permissions or privileges in Samsung Account prior to version 15.5.00.18 allows local attackers to access data in Samsung Acc… samsung · account 2025-11-05 medium4.3 CVE-2025-21075 Out-of-bounds write in libimagecodec.quram.so prior to SMR Nov-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-11-05 medium4.3 CVE-2025-21074 Out-of-bounds read in libimagecodec.quram.so prior to SMR Nov-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-11-05 medium6.8 CVE-2025-21073 Insecure default configuration in USB connection mode prior to SMR Nov-2025 Release 1 allows privileged physical attackers to access user data. samsung · android 2025-11-05 medium5.7 CVE-2025-21071 Out-of-bounds write in handling opcode in fingerprint trustlet prior to SMR Nov-2025 Release 1 allows local privileged attackers to write out-of-bounds memory. samsung · android 2025-11-05 medium6.5 CVE-2025-54335 An issue was discovered in the GPU driver in Samsung Mobile Processor Exynos 1480, 2400, 1580, 2500. samsung · exynos_1480_firmware, samsung · exynos_1580_firmware, samsung · exynos_2400_firmware +1 2025-11-04 critical9.8 CVE-2025-52910 An issue was discovered in the GPU in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1330, 1380, 1480, 2400. samsung · exynos_1280_firmware, samsung · exynos_1330_firmware, samsung · exynos_1380_firmware +3 2025-11-04 medium5.3 CVE-2025-27374 An issue was discovered in the Secure Boot component in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850, 1080, 1280, 2200, 133… samsung · exynos_9825_firmware, samsung · exynos_9820_firmware, samsung · exynos_980_firmware +8 2025-11-04 high7.5 CVE-2024-56426 An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, W920, W930, W1… samsung · exynos_1080_firmware, samsung · exynos_1280_firmware, samsung · exynos_1330_firmware +9 2025-11-04 medium6.5 CVE-2025-54327 An issue was discovered in VTS in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1380, W920, W930, W1000. samsung · exynos_1280_firmware, samsung · exynos_1380_firmware, samsung · exynos_2200_firmware 2025-11-04 high7.5 CVE-2025-49494 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 2100, 1280, 2200, 1330, 1380, 1480, 9110, Modem 5123. samsung · modem_5123_firmware, samsung · exynos_1280_firmware, samsung · exynos_1380_firmware +5 2025-11-04 high7.5 CVE-2025-54334 An issue was discovered in the NPU driver in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500. samsung · exynos_1280_firmware, samsung · exynos_1380_firmware, samsung · exynos_1480_firmware +4 2025-11-04

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.