NetSight

Security Dashboard

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

Reset
646 matching advisories · page 2 of 22Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-58090 The SOCK_STREAM receive path in the unix socket implementation failed to fully detach control messages from the socket buffer before processing them. freebsd · freebsd 2026-08-26 high7.8 CVE-2026-58089 When a process calls execve(2) to execute a setuid or setgid image, hwpmc(4) is supposed to detach PMCs owned by unprivileged processes. freebsd · freebsd 2026-08-26 high7.4 CVE-2026-58088 The ELF core dump code counted the number of dumpable VM map entries, allocated a buffer for the corresponding program headers, then iterated over the map a se… freebsd · freebsd 2026-08-19 high7.8 CVE-2026-58087 The GETALL and SETALL commands in semctl(2) recorded the number of semaphores in the target set, dropped the lock protecting the set, allocated a buffer sized … freebsd · freebsd 2026-08-19 high8.1 CVE-2026-58086 As an inadvertent side effect of an unrelated code change, PRIV_KTRACE was always denied to a jailed root user. freebsd · freebsd 2026-08-19 high7.5 CVE-2026-58085 After dispatching a decrypt operation to OCF and receiving the result, the wg(4) driver failed to check whether the MAC verification step succeeded. freebsd · freebsd 2026-08-19 medium5.5 CVE-2026-58084 To retrieve the previous timer value, the kernel calls realtimer_gettime(), which obtains the current time for the timer's clock. freebsd · freebsd 2026-08-19 high8.4 CVE-2026-58083 While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue's active list before the copy was c… freebsd · freebsd 2026-08-19 critical9.8 CVE-2026-58082 The ISO-2022 encoding module used a stack buffer sized to MB_LEN_MAX (6 bytes) for intermediate character output. freebsd · freebsd 2026-08-19 critical9.8 CVE-2026-58081 Several encoding modules, including HZ, UTF-7, VIQR, and ZW, did not properly check the size of the caller-supplied output buffer before writing converted char… freebsd · freebsd 2026-08-19 medium5.5 CVE-2026-49425 The compat32 kevent() handler translates a 64-bit kevent struct into a stack- declared 32-bit struct. freebsd · freebsd 2026-08-19 medium5.5 CVE-2026-49424 The Linux waitid() implementation translates a FreeBSD siginfo_t struct into a stack-declared Linux siginfo_t. freebsd · freebsd 2026-08-19 low3.3 CVE-2026-49423 When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including … freebsd · freebsd 2026-08-19 low3.3 CVE-2026-49431 The ZFS_IOC_SET_PROP ioctl, used by zfs-set(8), incorrectly validated the calling user such that an unprivileged user is able to set metadata on a dataset indi… freebsd · freebsd 2026-08-19 high7.8 CVE-2026-49430 The ZFS_IOC_RECV_NEW ioctl, in the heal receive path, similarly truncated a 64-bit payload size to a 32-bit integer for allocation, then used the original 64-b… freebsd · freebsd 2026-08-19 high7.8 CVE-2026-49429 The ZFS_IOC_USERSPACE_MANY ioctl, used by zfs-userspace(8), truncated a 64-bit output buffer size to a 32-bit integer for the kernel allocation, but used the o… freebsd · freebsd 2026-08-19 high8.4 CVE-2026-49428 Certain system calls, such open(2) with the O_TRUNC flag set, and fspacectl(2), could incorrectly free memory in largepage objects. freebsd · freebsd 2026-08-19 high8.8 CVE-2026-49427 Pages belonging to largepage shared memory objects were not explicitly wired. freebsd · freebsd 2026-08-19 low3.3 CVE-2026-49426 When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather … freebsd · freebsd 2026-08-19 high8.4 CVE-2026-49422 The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. freebsd · freebsd 2026-08-19 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

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.