NetSight

Security Dashboard

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

Reset
2,156 matching advisories · page 6 of 72Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2026-86314 Integer overflow in the source-bounds check in Memory::init() (src/runtime/Memory.cpp) in Samsung walrus on all platforms allows a remote attacker to cause an … 2026-09-07 high7.8 CVE-2026-86313 Out-of-bounds write vulnerability in Samsung Opensource Walrus allows Overflow Buffers. 2026-09-07 medium4.4 CVE-2026-49509 Out-of-bounds read vulnerability in Samsung Opensource rLottie allows Overread Buffers. 2026-09-04 medium6.3 CVE-2026-85084 Out-of-bounds Write and Improper Validation of Array Index vulnerability in Samsung Open Source TizenFX Samsung/TizenFX allows Overflow Buffers. 2026-09-03 medium5.5 CVE-2026-10420 Untrusted pointer dereference vulnerability in Samsung Open Source mTower allows Pointer Manipulation. 2026-09-01 medium5.5 CVE-2026-82927 Untrusted pointer dereference vulnerability in Samsung Open Source mTower allows Pointer Manipulation. 2026-09-01 medium5.5 CVE-2026-82926 NULL pointer dereference vulnerability in Samsung Open Source mTower allows Pointer Manipulation. 2026-09-01 medium5.5 CVE-2026-82797 Uncontrolled Recursion vulnerability in Samsung Open Source rlottie allows Serialized Data with Nested Payloads. 2026-08-31 medium6.5 CVE-2026-19588 Integer Overflow to Buffer Overflow vulnerability in Samsung Open Source rlottie allows Overflow Buffers. samsung · rlottie 2026-08-12 medium6.5 CVE-2026-19587 Uncontrolled Resource Consumption vulnerability in Samsung Open Source rlottie allows Excessive Allocation. samsung · rlottie 2026-08-12 medium6.5 CVE-2026-19518 Improper Validation of Specified Quantity in Input vulnerability in Samsung Open Source rlottie allows Input Data Manipulation. samsung · rlottie 2026-08-11 medium6.5 CVE-2026-19517 Improper Validation of Specified Quantity in Input and Allocation of Resources Without Limits or Throttling vulnerability in Samsung Open Source rlottie allows… samsung · rlottie 2026-08-11 medium6.5 CVE-2026-21083 Improper input validation in Smart Switch prior to version 3.7.72.6 allows adjacent attackers to access sensitive data. samsung · smart_switch 2026-08-10 medium5.5 CVE-2026-21082 Relative path traversal in Samsung Health prior to version 7.0.0 allows local attackers to access sensitive information. samsung · health 2026-08-10 medium5.1 CVE-2026-21081 Improper export of android application components in SamsungPassAutofill prior to version 5.2.10.x allows local attackers to access sensitive information. 2026-08-10 medium6.5 CVE-2026-21080 Cleartext storage of sensitive information in Smart Switch prior to version 3.7.72.6 allows adjacent attackers to access sensitive data. samsung · smart_switch 2026-08-10 medium6.5 CVE-2026-21079 Missing encryption of sensitive data in Smart Switch prior to version 3.7.72.6 allows adjacent attackers to intercept transmitted data. samsung · smart_switch 2026-08-10 medium6.5 CVE-2026-21078 Insufficient verification of data authenticity in Smart Switch trouble scanning mode prior to version 3.7.72.6 allows adjacent attackers to spoof device identi… samsung · smart_switch 2026-08-10 medium5.5 CVE-2026-21077 Incorrect authorization in Samsung Health prior to version 7.0.0 allows local attackers to access sensitive information. samsung · health 2026-08-10 medium5.5 CVE-2026-21076 Incorrect authorization in Samsung Health prior to version 7.0.0 allows local attackers to access sensitive information. samsung · health 2026-08-10 medium6.1 CVE-2026-21073 Improper input validation in Galaxy Themes prior to SMR Aug-2026 Release 1 allows physical attackers to launch arbitrary activity. samsung · android 2026-08-10 high7.8 CVE-2026-21072 Improper input validation in VC1 codec in libsavsvc.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 high7.8 CVE-2026-21071 Improper input validation in MPEG4 codec in libsavsvc.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 medium4.6 CVE-2026-21070 Improper input validation in Samsung Message prior to SMR Aug-2026 Release 1 allows physical attackers to access sensitive information. samsung · android 2026-08-10 high7.8 CVE-2026-21069 Incorrect conversion between numeric types in VC1 codec in libsavsvc.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 high7.8 CVE-2026-21068 Stack-based buffer overflow in libril_sem.so prior to SMR Aug-2026 Release 1 allows privileged local attackers to execute arbitrary code. samsung · android 2026-08-10 high7.8 CVE-2026-21067 Improper input validation in libsmsd.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 high7.8 CVE-2026-21066 Improper input validation in libcodec2_sec_flacdec.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 high7.8 CVE-2026-21065 Out-of-bounds write in libcodec2secqcelpdec.so prior to SMR Aug-2026 Release 1 allows local attackers to write out-of-bounds memory. samsung · android 2026-08-10 medium5.5 CVE-2026-21064 Improper access control in Weaver prior to SMR Aug-2026 Release 1 allows local attackers to cause device inoperability. samsung · android 2026-08-10

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.