NetSight

Security Dashboard

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

Reset
276 matching advisories · page 3 of 10Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-3038 The rtsock_msg_buffer() function serializes routing information into a buffer. freebsd · freebsd 2026-03-09 high7.5 CVE-2026-2261 Due to a programming error, blocklistd leaks a socket descriptor for each adverse event report it receives. freebsd · freebsd 2026-03-09 high7.5 CVE-2025-15576 If two sibling jails are restricted to separate filesystem trees, which is to say that neither of the two jail root directories is an ancestor of the other, ja… freebsd · freebsd 2026-03-09 high8.8 CVE-2025-15547 By default, jailed processes cannot mount filesystems, including nullfs(4). freebsd · freebsd 2026-03-09 high7.5 CVE-2025-14769 In some cases, the `tcp-setmss` handler may free the packet data and throw an error without halting the rule processing engine. freebsd · freebsd 2026-03-09 high7.2 CVE-2025-14558 The rtsol(8) and rtsold(8) programs do not validate the domain search list options provided in router advertisement messages; the option body is passed to reso… freebsd · freebsd 2026-03-09 high8.8 CVE-2024-8178 The ctl_write_buffer and ctl_read_buffer functions allocated memory to be returned to userspace, without initializing it. freebsd · freebsd 2024-09-05 high8.8 CVE-2024-45063 The function ctl_write_buffer incorrectly set a flag which resulted in a kernel Use-After-Free when a command finished processing. freebsd · freebsd 2024-09-05 high8.8 CVE-2024-43110 The ctl_request_sense function could expose up to three bytes of the kernel heap to userspace. freebsd · freebsd 2024-09-05 high8.8 CVE-2024-42416 The ctl_report_supported_opcodes function did not sufficiently validate a field provided by userspace, allowing an arbitrary write to a limited amount of kerne… freebsd · freebsd 2024-09-05 high8.2 CVE-2024-32668 An insufficient boundary validation in the USB code could lead to an out-of-bounds write on the heap, with data controlled by the caller. freebsd · freebsd 2024-09-05 high7.5 CVE-2024-45287 A malicious value of size in a structure of packed libnv can cause an integer overflow, leading to the allocation of a smaller buffer than required for the par… freebsd · freebsd 2024-09-05 high8.1 CVE-2024-7589 A signal handler in sshd(8) may call a logging function that is not async-signal-safe. freebsd · freebsd 2024-08-12 high7.5 CVE-2024-6760 A logic bug in the code which disables kernel tracing for setuid programs meant that tracing was not disabled when it should have, allowing unprivileged users … freebsd · freebsd 2024-08-12 high8.8 CVE-2022-23092 The implementation of lib9p's handling of RWALK messages was missing a bounds check needed when unpacking the message contents. freebsd · freebsd 2024-02-15 high7.7 CVE-2022-23090 The aio_aqueue function, used by the lio_listio system call, fails to release a reference to a credential in an error case. freebsd · freebsd 2024-02-15 high8.8 CVE-2022-23087 The e1000 network adapters permit a variety of modifications to an Ethernet packet when it is being transmitted. freebsd · freebsd 2024-02-15 high7.8 CVE-2022-23086 Handlers for *_CFG_PAGE read / write ioctls in the mpr, mps, and mpt drivers allocated a buffer of a caller-specified size, but copied to it a fixed size heade… freebsd · freebsd 2024-02-15 high8.2 CVE-2022-23085 A user-provided integer option was passed to nmreq_copyin() without checking if it would overflow. freebsd · freebsd 2024-02-15 high7.5 CVE-2022-23084 The total size of the user-provided nmreq to nmreq_copyin() was first computed and then trusted during the copyin. freebsd · freebsd 2024-02-15 high7.5 CVE-2023-6534 In versions of FreeBSD 14.0-RELEASE before 14-RELEASE-p2, FreeBSD 13.2-RELEASE before 13.2-RELEASE-p7 and FreeBSD 12.4-RELEASE before 12.4-RELEASE-p9, the pf(4… freebsd · freebsd 2023-12-13 high7.5 CVE-2023-5978 In versions of FreeBSD 13-RELEASE before 13-RELEASE-p5, under certain circumstances the cap_net libcasper(3) service incorrectly validates that updated constra… freebsd · freebsd 2023-11-08 high7.1 CVE-2023-5369 Before correction, the copy_file_range system call checked only for the CAP_READ and CAP_WRITE capabilities on the input and output file descriptors, respectiv… freebsd · freebsd 2023-10-04 high7.5 CVE-2023-4809 In pf packet processing with a 'scrub fragment reassemble' rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately … freebsd · freebsd 2023-09-06 high8.8 CVE-2023-3494 The fwctl driver implements a state machine which is executed when a bhyve guest accesses certain x86 I/O ports. freebsd · freebsd 2023-08-01 high7.5 CVE-2023-3107 A set of carefully crafted ipv6 packets can trigger an integer overflow in the calculation of a fragment reassembled packet's payload length field. freebsd · freebsd, netapp · clustered_data_ontap 2023-08-01 high7.5 CVE-2022-32264 sys/netinet/tcp_timer.h in FreeBSD before 7.0 contains a denial-of-service (DoS) vulnerability due to improper handling of TSopt on TCP connections. freebsd · freebsd 2022-09-06 high7.5 CVE-2021-29632 In FreeBSD 13.0-STABLE before n247428-9352de39c3dc, 12.2-STABLE before r370674, 13.0-RELEASE before p6, and 12.2-RELEASE before p12, certain conditions involvi… freebsd · freebsd 2022-01-18 high8.1 CVE-2021-29630 In FreeBSD 13.0-STABLE before n246938-0729ba2f49c9, 12.2-STABLE before r370383, 11.4-STABLE before r370381, 13.0-RELEASE before p4, 12.2-RELEASE before p10, an… freebsd · freebsd 2021-08-30 high7.8 CVE-2021-29631 In FreeBSD 13.0-STABLE before n246941-20f96f215562, 12.2-STABLE before r370400, 11.4-STABLE before r370399, 13.0-RELEASE before p4, 12.2-RELEASE before p10, an… freebsd · freebsd 2021-08-30

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.