NetSight

Security Dashboard

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

Reset
96 matching advisories · page 1 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-32gx-7hwp-3v8j Malicious code in kuinsu-lubki-nasmi (npm)Malware npm · kuinsu-lubki-nasmi 2026-09-17 critical GHSA-5q4g-ffmp-cx55 Malicious code in alanasme (npm)Malware npm · alanasme 2026-08-31 high7.5 CVE-2026-6069 NASM’s disasm() function contains a stack based buffer overflow when formatting disassembly output, allowing an attacker triggered out-of-bounds write when `sl… nasm · netwide_assembler 2026-04-10 critical9.6 CVE-2026-6068 NASM contains a heap use after free vulnerability in response file (-@) processing where a dangling pointer to freed memory is stored in the global depend_file… nasm · netwide_assembler 2026-04-10 medium5.5 CVE-2026-6067 A heap buffer overflow vulnerability exists in the Netwide Assembler (NASM) due to a lack of bounds checking in the obj_directive() function. nasm · netwide_assembler 2026-04-10 medium5.3 CVE-2025-8846 A vulnerability has been found in NASM Netwide Assember 2.17rc0. nasm · netwide_assembler 2025-08-11 medium5.3 CVE-2025-8845 A vulnerability was identified in NASM Netwide Assember 2.17rc0. nasm · netwide_assembler 2025-08-11 low3.3 CVE-2025-8844 A vulnerability was determined in NASM Netwide Assember 2.17rc0. nasm · netwide_assembler 2025-08-11 medium5.3 CVE-2025-8843 A vulnerability was found in NASM Netwide Assember 2.17rc0. nasm · netwide_assembler 2025-08-11 medium5.3 CVE-2025-8842 A vulnerability has been found in NASM Netwide Assember 2.17rc0. nasm · netwide_assembler 2025-08-11 medium5.5 CVE-2023-51258 A memory leak issue discovered in YASM v.1.3.0 allows a local attacker to cause a denial of service via the new_Token function in the modules/preprocs/nasm/nas… tortall · yasm 2024-01-18 medium5.5 CVE-2023-49558 An issue in YASM 1.3.0.86.g9def allows a remote attacker to cause a denial of service via the expand_mmac_params function in the modules/preprocs/nasm/nasm-pp.… yasm_project · yasm 2024-01-03 medium5.5 CVE-2023-49555 An issue in YASM 1.3.0.86.g9def allows a remote attacker to cause a denial of service via the expand_smacro function in the modules/preprocs/nasm/nasm-pp.c com… yasm_project · yasm 2024-01-03 medium5.5 CVE-2023-38668 Stack-based buffer over-read in disasm in nasm 2.16 allows attackers to cause a denial of service (crash). nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2023-38667 Stack-based buffer over-read in function disasm in nasm 2.16 allows attackers to cause a denial of service. nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2023-38665 Null pointer dereference in ieee_write_file in nasm 2.16rc0 allows attackers to cause a denial of service (crash). nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2022-29654 Buffer overflow vulnerability in quote_for_pmake in asm/nasm.c in nasm before 2.15.05 allows attackers to cause a denial of service via crafted file. nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2020-21687 Buffer Overflow vulnerability in scan function in stdscan.c in nasm 2.15rc0 allows remote attackers to cause a denial of service via crafted asm file. nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2020-21686 A stack-use-after-scope issue discovered in expand_mmac_params function in preproc.c in nasm before 2.15.04 allows remote attackers to cause a denial of servic… nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2020-21685 Buffer Overflow vulnerability in hash_findi function in hashtbl.c in nasm 2.15rc0 allows remote attackers to cause a denial of service via crafted asm file. nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2020-21528 A Segmentation Fault issue discovered in in ieee_segment function in outieee.c in nasm 2.14.03 and 2.15 allows remote attackers to cause a denial of service vi… nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2020-18780 A Use After Free vulnerability in function new_Token in asm/preproc.c in nasm 2.14.02 allows attackers to cause a denial of service via crafted nasm command. nasm · netwide_assembler 2023-08-22 medium5.5 CVE-2023-31725 yasm 1.3.0.55.g101bc was discovered to contain a heap-use-after-free via the function expand_mmac_params at yasm/modules/preprocs/nasm/nasm-pp.c. yasm_project · yasm 2023-05-17 high7.8 CVE-2023-31724 yasm 1.3.0.55.g101bc was discovered to contain a segmentation violation via the function do_directive at /nasm/nasm-pp.c. yasm_project · yasm 2023-05-17 medium5.5 CVE-2023-31723 yasm 1.3.0.55.g101bc was discovered to contain a segmentation violation via the function expand_mmac_params at /nasm/nasm-pp.c. yasm_project · yasm 2023-05-17 high7.8 CVE-2023-31722 There exists a heap buffer overflow in nasm 2.16.02rc1 (GitHub commit: b952891). nasm · netwide_assembler 2023-05-17 medium5.5 CVE-2023-31973 yasm v1.3.0 was discovered to contain a use after free via the function expand_mmac_params at /nasm/nasm-pp.c. tortall · yasm 2023-05-09 medium5.5 CVE-2023-31974 yasm v1.3.0 was discovered to contain a use after free via the function error at /nasm/nasm-pp.c. tortall · yasm 2023-05-09 medium5.5 CVE-2023-31972 yasm v1.3.0 was discovered to contain a use after free via the function pp_getline at /nasm/nasm-pp.c. tortall · yasm 2023-05-09 medium5.5 CVE-2023-30402 YASM v1.3.0 was discovered to contain a heap overflow via the function handle_dot_label at /nasm/nasm-token.re. yasm_project · yasm 2023-04-25

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.