NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-5223 Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of a… rust · cargo 2026-05-25 medium6.5 CVE-2026-5222 Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. rust · cargo 2026-05-25 high8.1 CVE-2024-43402 Rust is a programming language. rust-lang · rust 2024-09-04 critical9.8 CVE-2024-3566 A command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function whe… haskell · process_library, nodejs · node.js, php · php +2 2024-04-10 critical10.0 CVE-2024-24576 Rust is a programming language. fedoraproject · fedora, rust-lang · rust 2024-04-09 medium6.1 CVE-2023-40030 Malicious dependencies can inject arbitrary JavaScript into cargo-generated timing reports rust · cargo 2023-08-24 high7.9 CVE-2023-38497 Cargo not respecting umask when extracting crate archives rust · cargo 2023-08-03 medium5.3 CVE-2022-46176 Cargo did not verify SSH host keys rust · cargo 2023-01-10 medium4.2 CVE-2022-36114 Cargo extracting malicious crates can fill the file system rust · cargo 2022-09-14 medium4.6 CVE-2022-36113 Cargo extracting malicious crates can corrupt arbitrary files rust · cargo 2022-09-14 high7.5 CVE-2022-24713 Rust's regex crate vulnerable to regular expression denial of service rust · regex 2022-03-08 high7.3 CVE-2022-21658 Rust is a multi-paradigm, general-purpose programming language designed for performance and safety, especially safe concurrency. rust-lang · rust, fedoraproject · fedora, apple · ipados +4 2022-01-20 critical9.1 CVE-2021-29922 library/std/src/net/parser.rs in Rust before 1.53.0 does not properly consider extraneous zero characters at the beginning of an IP address string, which (in s… rust-lang · rust 2021-08-07 critical9.8 CVE-2021-31162 In the standard library in Rust before 1.52.0, a double free can occur in the Vec::from_iter function if freeing the element panics. rust-lang · rust, fedoraproject · fedora 2021-04-14 high8.2 CVE-2020-36323 In the standard library in Rust before 1.52.0, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to… rust-lang · rust, fedoraproject · fedora 2021-04-14 medium5.9 CVE-2018-25008 In the standard library in Rust before 1.29.0, there is weak synchronization in the Arc::get_mut method. rust-lang · rust 2021-04-14 medium5.9 CVE-2017-20004 In the standard library in Rust before 1.19.0, there is a synchronization problem in the MutexGuard object. rust-lang · rust 2021-04-14 critical9.8 CVE-2021-28879 In the standard library in Rust before 1.52.0, the Zip implementation can report an incorrect size due to an integer overflow. rust-lang · rust, fedoraproject · fedora 2021-04-11 high7.5 CVE-2021-28878 In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once for the same index (under certain conditi… rust-lang · rust, fedoraproject · fedora 2021-04-11 high7.5 CVE-2021-28877 In the standard library in Rust before 1.51.0, the Zip implementation calls __iterator_get_unchecked() for the same index more than once when nested. rust-lang · rust 2021-04-11 medium5.3 CVE-2021-28876 In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. rust-lang · rust, fedoraproject · fedora 2021-04-11 high7.5 CVE-2021-28875 In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. rust-lang · rust 2021-04-11 critical9.8 CVE-2020-36318 In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. rust-lang · rust 2021-04-11 high7.5 CVE-2020-36317 In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. rust-lang · rust 2021-04-11 high7.5 CVE-2015-20001 In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. rust-lang · rust 2021-04-11 medium6.1 CVE-2020-36202 Async-h1 request smuggling possible with long unread bodies rust · async-h1 2021-01-26 high8.2 CVE-2020-26297 XSS in mdBook rust · mdBook 2021-01-04 medium5.5 CVE-2020-35920 socket2 invalidly assumes the memory layout of std::net::SocketAddr rust · socket2, rust · net2 2020-12-31 medium5.5 CVE-2020-35908 Improper `Sync` implementation on `FuturesUnordered` in futures-utils can cause data corruption rust · futures-util 2020-12-31 medium5.5 CVE-2020-35907 futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer rust · futures-task 2020-12-31

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.