NetSight

Security Dashboard

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

Reset
285 matching advisories · page 1 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-128067 Pillow: Heap buffer overflow saving TIFF with libtiff when tags override image size pip · Pillow 9 days ago critical9.1 CVE-2026-112902 Pillow: Memory disclosure and segfault in libtiff encoder via crafted TIFF tags pip · Pillow 31 days ago medium6.1 CVE-2026-18495 A flaw was found in libtiff. 2026-09-11 high8.4 CVE-2026-52491 An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the libtiff/tools/thumbnail.c: main() component 2026-08-25 high7.8 CVE-2026-52492 An integer overflow in the libtiff rgb2ycbcr utility's cvtRaster() function when computing strip buffer sizes can result in an undersized heap allocation and s… 2026-08-24 critical9.8 CVE-2026-52490 An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the process_command_opts() function in tools/tiff… 2026-08-24 high7.3 CVE-2026-12912 A flaw was found in libtiff. 2026-06-29 high7.8 CVE-2026-4775 A flaw was found in the libtiff library. libtiff · libtiff, debian · debian_linux, redhat · ai_inference_server +9 2026-03-24 medium5.0 CVE-2025-61145 libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c. libtiff · libtiff 2026-02-23 high7.3 CVE-2025-61144 libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function. libtiff · libtiff 2026-02-23 medium5.5 CVE-2025-61143 libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c. libtiff · libtiff 2026-02-23 high8.8 CVE-2025-9900 A flaw was found in Libtiff. Red Hat · Red Hat Enterprise Linux 10, Red Hat · Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat · Red Hat Enterprise Linux 8 +10 2025-09-23 low2.5 CVE-2025-9165 A flaw has been found in LibTIFF 4.7.0. libtiff · libtiff 2025-08-19 low3.3 CVE-2025-8961 A weakness has been identified in LibTIFF 4.7.0. libtiff · libtiff 2025-08-14 medium5.3 CVE-2025-8851 A vulnerability was determined in LibTIFF up to 4.5.1. libtiff · libtiff 2025-08-11 low2.5 CVE-2025-8534 A vulnerability classified as problematic was found in libtiff 4.6.0. libtiff · libtiff 2025-08-05 low2.5 CVE-2024-13978 A vulnerability was found in LibTIFF up to 4.7.0. libtiff · libtiff 2025-08-01 medium5.3 CVE-2025-8177 A vulnerability was found in LibTIFF up to 4.7.0. libtiff · libtiff 2025-07-26 medium5.3 CVE-2025-8176 A vulnerability was found in LibTIFF up to 4.7.0. libtiff · libtiff 2025-07-26 high7.5 CVE-2024-7006 A null pointer dereference flaw was found in Libtiff via `tif_dirinfo.c`. libtiff · libtiff, redhat · enterprise_linux, redhat · enterprise_linux_for_arm_64 +2 2024-08-12 high7.5 CVE-2023-52356 A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. debian · debian_linux, apple · ipados, apple · iphone_os +17 2024-01-25 high7.5 CVE-2023-52355 An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. libtiff · libtiff, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 10 +8 2024-01-25 low3.3 CVE-2023-6228 An issue was found in the tiffcp utility distributed by the libtiff package where a crafted TIFF file on processing may cause a heap-based buffer overflow lead… libtiff · libtiff 2023-12-18 medium6.5 CVE-2023-6277 An out-of-memory flaw was found in libtiff. libtiff · libtiff, fedoraproject · fedora 2023-11-24 medium5.5 CVE-2023-3164 A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. libtiff · libtiff, redhat · enterprise_linux 2023-11-02 medium6.5 CVE-2023-40745 LibTIFF is vulnerable to an integer overflow. libtiff · libtiff, netapp · active_iq_unified_manager, fedoraproject · fedora +1 2023-10-05 medium6.5 CVE-2023-41175 A vulnerability was found in libtiff due to multiple potential integer overflows in raw2tiff.c. libtiff · libtiff, fedoraproject · fedora, redhat · enterprise_linux +2 2023-10-05 medium5.5 CVE-2023-3576 A memory leak flaw was found in Libtiff's tiffcrop utility. libtiff · libtiff, fedoraproject · fedora, redhat · enterprise_linux +1 2023-10-04 medium6.5 CVE-2022-40090 An issue was discovered in function TIFFReadDirectory libtiff before 4.4.0 allows attackers to cause a denial of service via crafted TIFF file. libtiff · libtiff 2023-08-22 medium5.5 CVE-2020-18768 There exists one heap buffer overflow in _TIFFmemcpy in tif_unix.c in libtiff 4.0.10, which allows an attacker to cause a denial-of-service through a crafted t… libtiff · libtiff 2023-08-22

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.