NetSight

Security Dashboard

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

Reset
42 matching advisories · page 1 of 2Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low1.0 CVE-2026-0460 Improper authentication in Bootgen could result in the use of a fixed salt value for RSA padding instead of a randomly generated salt, potentially impacting da… AMD · Bootgen 9 days ago low1.9 CVE-2026-105051 Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on… 50 days ago low2.0 CVE-2025-52532 A race condition in the MxGPU-Virtualization driver’s ioctl path caused by concurrent unsynchronized access to the global variable amdgv_cmd in an unlocked ioc… 2026-05-15 low2.0 CVE-2025-54505 A transient execution vulnerability within AMD CPUs may allow a local user-privileged attacker to leak data via the floating point divisor unit, potentially re… 2026-04-27 low1.8 CVE-2021-26410 Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter values from its own memory space allowing a… 2026-02-10 low3.3 CVE-2025-0011 Improper removal of sensitive information before storage or transfer in AMD Crash Defender could allow an attacker to obtain kernel address information potenti… 2025-09-06 low3.3 CVE-2023-31306 Improper validation of an array index in the AMD graphics driver software could allow an attacker to pass malformed arguments to the dynamic power management (… 2025-09-06 low3.8 CVE-2025-36581 Dell PowerEdge Platform version(s) 14G AMD BIOS v1.25.0 and prior, contain(s) an Access of Memory Location After End of Buffer vulnerability. dell · poweredge_r7425_firmware, dell · poweredge_r7415_firmware, dell · poweredge_r6415_firmware 2025-08-14 low3.8 CVE-2024-36349 A transient execution vulnerability in some AMD processors may allow a user process to infer TSC_AUX even when such a read is disabled, potentially resulting i… 2025-07-08 low3.8 CVE-2024-36348 A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively even if UMIP feature is enable… 2025-07-08 low3.2 CVE-2025-0036 In AMD Versal Adaptive SoC devices, the incorrect configuration of the SSS during runtime (post-boot) cryptographic operations could cause data to be incorrect… 2025-06-10 low3.3 CVE-2023-31366 Improper input validation in AMD μProf could allow an attacker to perform a write to an invalid address, potentially resulting in denial of service. amd · uprof 2024-08-13 low2.3 CVE-2023-31307 Improper validation of array index in Power Management Firmware (PMFW) may allow a privileged attacker to cause an out-of-bounds memory read within PMFW, poten… amd · radeon_software 2024-08-13 low3.9 CVE-2021-26387 Insufficient access controls in ASP kernel may allow a privileged attacker with access to AMD signing keys and the BIOS menu or UEFI shell to map DRAM regions … 2024-08-13 low3.3 CVE-2023-20570 Insufficient verification of data authenticity in the configuration state machine may allow a local attacker to potentially load arbitrary bitstreams. amd · alveo_u50_firmware, amd · alveo_u200_firmware, amd · alveo_u250_firmware +9 2024-02-13 low3.2 CVE-2023-20573 A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information. amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2024-01-11 low1.9 CVE-2023-20526 Insufficient input validation in the ASP Bootloader may enable a privileged attacker with physical access to expose the contents of ASP memory potentially lead… amd · epyc_7001_firmware, amd · epyc_7251_firmware, amd · epyc_7261_firmware +9 2023-11-14 low3.3 CVE-2023-20521 TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verification, potentially leading t… amd · epyc_7001_firmware, amd · epyc_7251_firmware, amd · epyc_7261_firmware +9 2023-11-14 low3.3 CVE-2023-20519 A Use-After-Free vulnerability in the management of an SNP guest context page may allow a malicious hypervisor to masquerade as the guest's migration agent res… amd · milanpi_firmware, amd · genoapi_firmware 2023-11-14 low1.9 CVE-2022-23830 SMM configuration may not be immutable, as intended, when SNP is enabled resulting in a potential limited loss of guest memory integrity. amd · epyc_9654p_firmware, amd · epyc_9654_firmware, amd · epyc_9634_firmware +9 2023-11-14 low2.5 CVE-2021-46766 Improper clearing of sensitive data in the ASP Bootloader may expose secret keys to a privileged attacker accessing ASP SRAM, potentially leading to a loss of … amd · epyc_9654p_firmware, amd · epyc_9654_firmware, amd · epyc_9634_firmware +9 2023-11-14 low1.9 CVE-2021-26345 Failure to validate the value in APCB may allow a privileged attacker to tamper with the APCB token to force an out-of-bounds memory read potentially resulting… amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-11-14 low3.3 CVE-2022-42336 Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting o… xen · xen 2023-05-17 low3.9 CVE-2021-46762 Insufficient input validation in the SMU may allow an attacker to corrupt SMU SRAM potentially leading to a loss of integrity or denial of service. amd · epyc_72f3_firmware, amd · epyc_7313_firmware, amd · epyc_7313p_firmware +9 2023-05-09 low2.4 CVE-2023-20528 Insufficient input validation in the SMU may allow a physical attacker to exfiltrate SMU memory contents over the I2C bus potentially leading to a loss of conf… amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-01-11 low3.3 CVE-2021-26342 In SEV guest VMs, the CPU may fail to flush the Translation Lookaside Buffer (TLB) following a particular sequence of operations that includes creation of a ne… amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-05-11 low3.3 CVE-2016-1791 The AMD subsystem in Apple OS X before 10.11.5 allows attackers to obtain sensitive kernel memory-layout information via a crafted app. apple · mac_os_x 2016-05-20 low3.8 CVE-2016-3159 The fpu_fxrstor function in arch/x86/i387.c in Xen 4.x does not properly handle writes to the hardware FSW.ES bit when running on AMD64 processors, which allow… oracle · vm_server, xen · xen, fedoraproject · fedora +1 2016-04-13 low3.8 CVE-2016-3158 The xrstor function in arch/x86/xstate.c in Xen 4.x does not properly handle writes to the hardware FSW.ES bit when running on AMD64 processors, which allows l… xen · xen, fedoraproject · fedora, oracle · vm_server 2016-04-13 low2.9 CVE-2013-1573 The csnStreamDissector function in epan/dissectors/packet-csn1.c in the CSN.1 dissector in Wireshark 1.6.x before 1.6.13 and 1.8.x before 1.8.5 does not proper… wireshark · wireshark 2013-02-03

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.