NetSight

Security Dashboard

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

Reset
263 matching advisories · page 1 of 9Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.7 CVE-2026-128028 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability in Mage_Catalog_Model_Product_Opt… OpenMage · magento-lts 8 days ago medium4.7 CVE-2026-128029 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability in the Dataflow profile run page,… OpenMage · magento-lts 8 days ago medium5.1 CVE-2026-128031 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an incorrect authorization vulnerability because admin controllers' _isAllowe… OpenMage · magento-lts 8 days ago medium4.4 CVE-2026-128032 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 accepts the free (No Payment Information Required) payment method on orders with a non… OpenMage · magento-lts 8 days ago medium5.3 CVE-2026-128033 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an information disclosure vulnerability in Mage_Rss_Model_Resource_Order::get… OpenMage · magento-lts 8 days ago medium6.3 CVE-2026-128042 OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains a race condition in shopping cart price rule usage limits, because Mage_Sales… OpenMage · magento-lts 8 days ago medium6.9 CVE-2026-128045 OpenMage Magento-LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an authorization bypass in the /rss/order/status feed because its URL key is … OpenMage · magento-lts 8 days ago medium6.9 CVE-2026-128048 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 lets restricted administrators read decrypted configuration secrets because the store.… OpenMage · magento-lts 8 days ago medium4.8 CVE-2026-128051 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability because storefront MSRP/MAP popup… OpenMage · magento-lts 8 days ago medium5.1 CVE-2026-128052 OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains an incorrect authorization vulnerability in the template filter's {{layout}} … OpenMage · magento-lts 8 days ago medium4.7 CVE-2026-128053 OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a reflected cross-site scripting vulnerability in its error pages, which prin… OpenMage · magento-lts 8 days ago medium4.3 CVE-2026-95630 Adobe Commerce is affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. adobe · commerce, adobe · commerce_b2b, adobe · magento 39 days ago medium6.5 CVE-2026-48411 Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. adobe · commerce, adobe · magento, adobe · commerce_b2b 2026-08-11 medium5.4 CVE-2026-48371 Adobe Commerce is affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts i… adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium6.1 CVE-2026-48000 Adobe Commerce is affected by an Improper Redirect (Open Redirect) vulnerability that could result in a Security feature bypass. adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium4.8 CVE-2026-47999 Adobe Commerce is affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker to inject malicious scripts … adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium5.9 CVE-2026-47998 Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium5.9 CVE-2026-47997 Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium6.8 CVE-2026-47996 Adobe Commerce is affected by an Incorrect Authorization vulnerability that could lead to arbitrary file system read. adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 medium4.8 CVE-2026-34658 Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by a stored Cross-Site Scripting (XSS) vulner… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-05-12 medium4.3 CVE-2026-34656 Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by an Improper Authorization vulnerability th… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-05-12 medium4.8 CVE-2026-34655 Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by a stored Cross-Site Scripting (XSS) vulner… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-05-12 medium5.3 CVE-2026-34654 Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by a Dependency on Vulnerable Third-Party Com… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-05-12 medium5.3 CVE-2026-42458 Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a … composer · openmage/magento-lts 2026-05-06 medium6.1 CVE-2026-42207 Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a … composer · openmage/magento-lts 2026-05-05 medium5.4 CVE-2026-40098 Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a … composer · openmage/magento-lts 2026-04-20 medium4.9 CVE-2026-25525 Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a … composer · openmage/magento-lts 2026-04-20 medium5.3 CVE-2026-5603 A vulnerability was identified in elgentos magento2-dev-mcp up to 1.0.2. npm · @elgentos/magento2-dev-mcp 2026-04-05 medium6.8 CVE-2026-21360 Adobe Commerce versions 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 and earlier are affected by an Improper Limitation of a Pathname to a… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-03-11 medium4.7 CVE-2026-21359 Adobe Commerce versions 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 and earlier are affected by an Incorrect Authorization vulnerability … adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-03-11

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.