NetSight

Security Dashboard

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

Reset
4,236 matching advisories · page 13 of 142Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.4 CVE-2026-83102 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). 2026-09-15 high8.1 CVE-2026-83101 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). 2026-09-15 critical9.8 CVE-2026-83100 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 critical10.0 CVE-2026-83099 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 critical9.8 CVE-2026-83098 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 medium6.5 CVE-2026-83097 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 high7.9 CVE-2026-83096 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). 2026-09-15 critical9.8 CVE-2026-83095 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 critical9.8 CVE-2026-83094 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 high8.6 CVE-2026-83093 Vulnerability in the Oracle Forms product of Oracle Fusion Middleware (component: Forms Services, C/S, Charmode). oracle · forms 2026-09-15 medium6.7 CVE-2026-58767 In multiple functions of arm-smmu-v3.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 high7.8 CVE-2026-58766 In multiple functions of arm-smmu-v3.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-58755 In smmu_install_nested_ste of arm-smmu-v3.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-58751 In multiple functions of arm-smmu-v3.c, there is a possible use-after-free due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-58747 In smmu_detach_dev of arm-smmu-v3.c, there is a possible permission bypass due to a logic error in the code. google · android 2026-09-15 high7.0 CVE-2026-58728 In ARM64_TLBI of mmu.h, there is a possible memory corruption due to a race condition. google · android 2026-09-15 medium6.7 CVE-2026-58718 In smmu_detach_dev_nested of arm-smmu-v3.c, there is a possible escalation of privilege due to improper input validation. google · android 2026-09-15 high7.0 CVE-2026-58701 In trusty_dputc of generic-arm64-smcall.c, there is a possible out-of-bounds write due to a race condition. google · android 2026-09-15 medium5.3 CVE-2026-91002 A weakness has been identified in stamparm maltrail up to 3.0.1. stamparm maltrail 2026-09-15 critical GHSA-pxh4-pcgj-8rhr Malicious code in jittery-tan-ptarmigan (npm)Malware npm · jittery-tan-ptarmigan 2026-09-13 critical GHSA-h648-65wq-vfpr Malicious code in jasmine-karma-innercore-csrf (npm)Malware npm · jasmine-karma-innercore-csrf 2026-09-13 critical GHSA-88gg-cjhm-xrcv Malicious code in jasmine-figures-geomorphology-karma (npm)Malware npm · jasmine-figures-geomorphology-karma 2026-09-13 critical GHSA-wp8m-xg2q-rr2c Malicious code in jai-surya-varman78 (npm)Malware npm · jai-surya-varman78, npm · jai-surya-varman78 2026-09-13 critical GHSA-fwmm-4hrr-m2h2 Malicious code in island-ntgm1-zymvl-harmony-project (npm)Malware npm · island-ntgm1-zymvl-harmony-project 2026-09-13 critical GHSA-8prj-9cwv-v435 Malicious code in ishanisharma (npm)Malware npm · ishanisharma 2026-09-13 critical GHSA-m49x-h5v3-4jmc Malicious code in involved_ptarmigan_z3n (npm)Malware npm · involved_ptarmigan_z3n 2026-09-13 critical GHSA-24cc-6c8c-8277 Malicious code in invisible_marmoset_z3n (npm)Malware npm · invisible_marmoset_z3n 2026-09-13 critical GHSA-9x4c-4jmx-73r3 Malicious code in invisible_armadillo_dumbs (npm)Malware npm · invisible_armadillo_dumbs 2026-09-13 critical GHSA-pj32-8c23-6j7v Malicious code in interstellarmedium-postcss-loader-chromedriver-innercore (npm)Malware npm · interstellarmedium-postcss-loader-chromedriver-innercore 2026-09-13 critical GHSA-xrc6-hp2g-3cg9 Malicious code in interstellarmedium-configstore-dotenv-safe-oauth (npm)Malware npm · interstellarmedium-configstore-dotenv-safe-oauth 2026-09-13

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.