NetSight

Security Dashboard

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

Reset
276 matching advisories · page 2 of 10Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-49421 The kernel function that implements unlinkat(2) and funlinkat(2) validated the AT_RESOLVE_BENEATH flag but failed to pass it through to the underlying path loo… freebsd · freebsd 2026-08-19 high8.8 CVE-2026-49420 The RTSP handler in libalias rewrote outgoing packets into a fixed-length stack buffer without checking whether the rewritten data fit in the buffer, or whethe… freebsd · freebsd 2026-08-19 high8.8 CVE-2026-49419 When the JAIL_AT_DESC flag is specified, kern_jail_set() and kern_jail_get() released the reference to the caller's current prison before looking up the jail d… freebsd · freebsd 2026-08-19 high8.8 CVE-2026-49418 When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping range are marked invalid but remain in the pa… freebsd · freebsd 2026-08-19 high8.8 CVE-2026-49415 During execve(2) of a SUID binary, the new virtual address space is installed before the process credentials are updated. freebsd · freebsd 2026-08-19 high8.2 CVE-2026-55074 Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv) pip · ansible-jailexec 2026-08-12 high7.8 CVE-2026-49416 The CONS_HISTORY ioctl handler did not adequately validate the requested history size. freebsd · freebsd 2026-06-27 high7.8 CVE-2026-49414 The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. freebsd · freebsd 2026-06-27 high7.0 CVE-2026-49417 Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. freebsd · freebsd 2026-06-27 high7.1 CVE-2026-49413 The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. freebsd · freebsd 2026-06-27 high7.8 CVE-2026-49412 The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. freebsd · freebsd 2026-06-27 high7.8 CVE-2026-45258 dsp_mmap_single() validated the requested mapping by checking the sum of the user-supplied offset and length against the buffer size. freebsd · freebsd 2026-06-27 high7.8 CVE-2026-45257 The KTLS receive path decrypted each record in place, assuming that the mbufs holding received data were anonymous and safe to modify. freebsd · freebsd 2026-06-26 high7.5 CVE-2026-45255 When bsdinstall or bsdconfig are prompted to scan for nearby Wi-Fi networks, they build up a list of network names and use bsddialog(1) to prompt the user to s… freebsd · freebsd 2026-05-21 high8.4 CVE-2026-45253 ptrace(PT_SC_REMOTE) failed to properly validate parameters for the syscall(2) and __syscall(2) meta-system calls. freebsd · freebsd 2026-05-21 high7.8 CVE-2026-45251 A file descriptor can be closed while a thread is blocked in a poll(2) or select(2) call waiting for that descriptor. freebsd · freebsd 2026-05-21 high8.8 CVE-2026-39461 libcasper(3) communicates with helper processes via UNIX domain sockets, and uses the select(2) system call to wait for data to become available. freebsd · freebsd 2026-05-21 high7.8 CVE-2026-45250 The setcred(2) system call is only available to privileged users. freebsd · freebsd 2026-05-21 high8.1 CVE-2026-42512 As dhclient is building an environment to pass to dhclient-script, it may need to resize the array of string pointers. freebsd · freebsd 2026-04-30 high7.8 CVE-2026-39457 When exchanging data over a socket, libnv uses select(2) to wait for data to arrive. freebsd · freebsd 2026-04-30 high8.1 CVE-2026-35547 When processing the header of an incoming message, libnv failed to properly validate the message size. freebsd · freebsd 2026-04-30 high7.5 CVE-2026-7164 Incorrect packet validation allowed unbounded recursion parsing SCTP chunk parameters. freebsd · freebsd 2026-04-30 high7.8 CVE-2026-7270 An operator precedence bug in the kernel results in a scenario where a buffer overflow causes attacker-controlled data to overwrite adjacent execve(2) argument… freebsd · freebsd 2026-04-30 high8.1 CVE-2026-42511 The BOOTP file field is written to the lease file without escaping embedded double-quotes, allowing injection of arbitrary dhclient.conf directives. freebsd · freebsd 2026-04-30 high8.4 CVE-2026-5398 The implementation of TIOCNOTTY failed to clear a back-pointer from the structure representing the controlling terminal to the calling process' session. freebsd · freebsd 2026-04-22 high8.2 CVE-2026-34578 OPNsense is a FreeBSD based firewall and routing platform. opnsense · opnsense 2026-04-09 high7.5 CVE-2026-4748 A regression in the way hashes were calculated caused rules containing the address range syntax (x.x.x.x - y.y.y.y) that only differ in the address range(s) in… freebsd · freebsd 2026-04-01 high8.8 CVE-2026-4747 Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet. freebsd · freebsd 2026-03-26 high7.5 CVE-2026-4652 On a system exposing an NVMe/TCP target, a remote client can trigger a kernel panic by sending a CONNECT command for an I/O queue with a bogus or stale CNTLID. freebsd · freebsd 2026-03-26 high7.5 CVE-2026-4247 When a challenge ACK is to be sent tcp_respond() constructs and sends the challenge ACK and consumes the mbuf that is passed in. freebsd · freebsd 2026-03-26

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.