NetSight

Security Dashboard

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

Reset
1,969 matching advisories · page 4 of 66Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical10.0 CVE-2026-75650 Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine VulnerabilityExploited Adobe · Adobe Commerce, Magento · Magento Open Source, Adobe · Adobe Commerce B2B +3 2026-09-07 critical GHSA-9mp2-7r83-mx5c Malicious code in com.adobe.cq.core.wcm.components.content (npm)Malware npm · com.adobe.cq.core.wcm.components.content 2026-09-04 critical GHSA-vf4m-wgf3-pjhm Malicious code in adobe-dcapi-web (npm)Malware npm · adobe-dcapi-web, npm · adobe-dcapi-web, npm · adobe-dcapi-web +2 2026-08-31 critical GHSA-gjmg-49j7-f944 Malicious code in adobe-dcapi-web2 (npm)Malware npm · adobe-dcapi-web2 2026-08-31 critical GHSA-4vgf-4mvw-gfg9 Malicious code in adobe-cr (npm)Malware npm · adobe-cr 2026-08-31 critical GHSA-v2f4-qv25-7pc6 Malicious code in adobe-alloy-mini-site (npm)Malware npm · adobe-alloy-mini-site 2026-08-31 critical GHSA-vph4-48j5-rgwm Malicious code in adobe-tracking (npm)Malware npm · adobe-tracking 2026-08-31 critical GHSA-v3pg-f8fv-2586 Malicious code in adobe_pipeline_test (npm)Malware npm · adobe_pipeline_test 2026-08-31 critical GHSA-7crv-frgg-vv98 Malicious code in adobe-alloy (npm)Malware npm · adobe-alloy 2026-08-31 critical GHSA-v494-r6r6-84vp Malicious code in adobe-helix-rum-enhancer (npm)Malware npm · adobe-helix-rum-enhancer, npm · adobe-helix-rum-enhancer 2026-08-31 critical10.0 CVE-2026-76197 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability that co… adobe · campaign 2026-08-25 critical10.0 CVE-2026-76195 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability that co… adobe · campaign 2026-08-25 critical10.0 CVE-2026-76193 Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of … adobe · campaign 2026-08-25 critical10.0 CVE-2026-71398 Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the curren… adobe · campaign 2026-08-11 critical9.1 CVE-2026-71362 Adobe Commerce and Magento Incorrect Authorization VulnerabilityExploited adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-08-11 critical9.0 CVE-2026-48381 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could re… adobe · campaign 2026-08-11 critical10.0 CVE-2026-27302 Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the curren… adobe · campaign 2026-08-11 critical9.6 CVE-2026-71384 is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. adobe · coldfusion 2026-08-11 critical10.0 CVE-2026-48362 ColdFusion is affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability that could result in arbi… adobe · coldfusion 2026-08-11 critical9.8 CVE-2026-48333 Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. adobe · campaign 2026-08-03 critical10.0 CVE-2026-48331 Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. adobe · campaign 2026-08-03 critical10.0 CVE-2026-48330 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could re… adobe · campaign 2026-08-03 critical9.9 CVE-2026-48326 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could re… adobe · campaign 2026-08-03 critical10.0 CVE-2026-48323 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that could result in arbitra… adobe · campaign 2026-08-03 critical9.6 CVE-2026-48317 Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') vulnerability that could … adobe · campaign 2026-08-03 critical10.0 CVE-2026-48449 Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the curren… adobe · campaign 2026-07-30 critical GHSA-345r-jf58-m5rj Malicious code in @adobesign/as-dev-tools (npm)Malware npm · @adobesign/as-dev-tools, npm · @adobesign/as-dev-tools 2026-07-26 critical GHSA-vgm5-6f8q-9gp4 Malicious code in types-for-adobe (PyPI)Malware pip · types-for-adobe, pip · types-for-adobe 2026-07-21 critical9.3 CVE-2026-48334 Illustrator is affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user, potenti… adobe · illustrator 2026-07-14 critical9.0 CVE-2026-48327 ColdFusion is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. adobe · coldfusion 2026-07-14

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.