NetSight

Security Dashboard

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

Reset
78 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.6 CVE-2026-112077 A vulnerability was detected in radareorg radare2 6.2.0/6.2.2. 34 days ago medium5.5 CVE-2026-81886 radare2 is a UNIX-like reverse engineering framework and command-line toolset. radare · radare2 2026-09-22 medium5.5 CVE-2026-81885 radare2 is a UNIX-like reverse engineering framework and command-line toolset. radare · radare2 2026-09-22 medium5.5 CVE-2026-81880 radare2 is a UNIX-like reverse engineering framework and command-line toolset. radare · radare2 2026-09-22 medium5.5 CVE-2026-81879 radare2 is a UNIX-like reverse engineering framework and command-line toolset. radare · radare2 2026-09-22 medium5.5 CVE-2026-81878 radare2 is a UNIX-like reverse engineering framework and command-line toolset. radare · radare2 2026-09-22 medium5.3 CVE-2026-14757 A vulnerability was determined in radareorg radare2 up to 6.1.6. radare · radare2 2026-07-05 medium6.9 CVE-2026-6941 radare2 prior to 6.1.4 contains a path traversal vulnerability in its project notes handling that allows attackers to read or write files outside the configure… radare · radare2, radare2 · radare2 2026-04-23 medium5.5 CVE-2025-63745 A NULL pointer dereference vulnerability was discovered in radare2 6.0.5 and earlier within the info() function of bin_ne.c. radare · radare2 2025-11-14 medium4.3 CVE-2025-63744 A NULL pointer dereference vulnerability was discovered in radare2 6.0.5 and earlier within the load() function of bin_dyldcache.c. radare · radare2 2025-11-14 medium5.5 CVE-2025-60360 radare2 v5.9.8 and before contains a memory leak in the function r2r_subprocess_init. radare · radare2 2025-10-17 medium5.5 CVE-2025-60359 radare2 v5.9.8 and before contains a memory leak in the function r_bin_object_new. radare · radare2 2025-10-17 medium5.5 CVE-2025-60358 radare2 v.5.9.8 and before contains a memory leak in the function _load_relocations. radare · radare2 2025-10-16 medium5.5 CVE-2024-48241 An issue in radare2 v5.8.0 through v5.9.4 allows a local attacker to cause a denial of service via the __bf_div function. radare · radare2 2024-10-30 medium5.5 CVE-2024-26475 An issue in radareorg radare2 v.0.9.7 through v.5.8.6 and fixed in v.5.8.8 allows a local attacker to cause a denial of service via the grub_sfs_read_extent fu… radare · radare2 2024-03-14 medium5.5 CVE-2023-27114 radare2 v5.8.3 was discovered to contain a segmentation fault via the component wasm_dis at p/wasm/wasm.c. radare · radare2 2023-03-10 medium5.5 CVE-2022-34520 Radare2 v5.7.2 was discovered to contain a NULL pointer dereference via the function r_bin_file_xtr_load_buffer at bin/bfile.c. radare · radare2 2022-07-22 medium5.5 CVE-2022-34502 Radare2 v5.7.0 was discovered to contain a heap buffer overflow via the function consume_encoded_name_new at format/wasm/wasm.c. radare · radare2 2022-07-22 medium5.5 CVE-2021-44974 radareorg radare2 version 5.5.2 is vulnerable to NULL Pointer Dereference via libr/bin/p/bin_symbols.c binary symbol parser. radare · radare2 2022-05-25 medium5.5 CVE-2021-44975 radareorg radare2 5.5.2 is vulnerable to Buffer Overflow via /libr/core/anal_objc.c mach-o parser. radare · radare2 2022-05-24 medium5.5 CVE-2022-1649 Null pointer dereference in libr/bin/format/mach0/mach0.c in radareorg/radare2 in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-05-10 medium5.5 CVE-2022-1444 heap-use-after-free in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-04-23 medium6.1 CVE-2022-1383 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-18 medium5.5 CVE-2022-1382 NULL Pointer Dereference in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-18 medium5.5 CVE-2022-1284 heap-use-after-free in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-08 medium5.5 CVE-2022-1283 NULL Pointer Dereference in r_bin_ne_get_entrypoints function in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-08 medium5.5 CVE-2022-1244 heap-buffer-overflow in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-05 medium6.6 CVE-2022-1207 Out-of-bounds read in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-01 medium5.5 CVE-2022-1052 Heap Buffer Overflow in iterate_chained_fixups in GitHub repository radareorg/radare2 prior to 5.6.6. radare · radare2 2022-03-24 medium5.5 CVE-2022-0849 Use After Free in r_reg_get_name_idx in GitHub repository radareorg/radare2 prior to 5.6.6. radare · radare2 2022-03-05

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.