NetSight

Security Dashboard

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

Reset
17 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.3 CVE-2026-128043 OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains a cross-site request forgery vulnerability in PayPal cancel and decline retur… OpenMage · magento-lts 8 days ago low2.7 CVE-2026-48412 Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. adobe · commerce, adobe · magento, adobe · commerce_b2b 2026-08-11 low3.7 CVE-2026-48001 Adobe Commerce is affected by an Information Exposure vulnerability that could lead to a limited disclosure of sensitive information. adobe · commerce, adobe · commerce_b2b, adobe · magento +1 2026-07-14 low3.4 CVE-2026-34685 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 Input Validation vulnerability… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-05-12 low3.1 CVE-2026-21295 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 a URL Redirection to Untrusted Site ('Ope… adobe · commerce, adobe · commerce_b2b, adobe · magento 2026-03-11 low2.7 CVE-2025-49549 Magento Authenticated Security feature bypass composer · magento/project-community-edition, composer · magento/community-edition 2025-06-25 low2.7 CVE-2025-27192 Magento does not properly protect credentials composer · magento/project-community-edition, composer · magento/community-edition 2025-04-08 low2.9 CVE-2025-27400 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 2025-02-28 low3.7 CVE-2025-24432 Magento Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2025-02-11 low3.7 CVE-2025-24430 Magento Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2025-02-11 low3.5 CVE-2025-24429 Magento Improper Access Control vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2025-02-11 low2.7 CVE-2024-45149 Magento Open Source Improper Access Control vulnerability composer · magento/community-edition 2024-10-10 low2.7 CVE-2023-29293 Magento Open Source affected by Improper Input Validation composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 low3.7 CVE-2021-28566 Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are vulnerable to an Information Disclosure vulnerability when uploadin… composer · magento/community-edition 2021-09-08 low3.7 CVE-2020-24406 When in maintenance mode, Magento version 2.4.0 and 2.3.4 (and earlier) are affected by an information disclosure vulnerability that could expose the installat… composer · magento/community-edition 2020-11-09 low2.7 CVE-2020-24404 Magento version 2.4.0 and 2.3.5p1 (and earlier) are affected by an incorrect permissions vulnerability within the Integrations component. composer · magento/community-edition 2020-11-09 low2.7 CVE-2020-24403 Magento version 2.4.0 and 2.3.5p1 (and earlier) are affected by an incorrect user permissions vulnerability within the Inventory component. composer · magento/community-edition, composer · magento/project-community-edition 2020-11-09

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.