NetSight

Security Dashboard

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

Reset
62 matching advisories · page 1 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-103118 A vulnerability was detected in GraphicsMagick up to 1.3.47. GraphicsMagick 52 days ago medium4.0 CVE-2025-32460 GraphicsMagick before 8e56520 has a heap-based buffer over-read in ReadJXLImage in coders/jxl.c, related to an ImportViewPixelArea call. graphicsmagick · graphicsmagick 2025-04-09 medium4.5 CVE-2025-27796 ReadWPGImage in WPG in GraphicsMagick before 1.3.46 mishandles palette buffer allocation, resulting in out-of-bounds access to heap memory in ReadBlob. graphicsmagick · graphicsmagick 2025-03-07 medium4.3 CVE-2025-27795 ReadJXLImage in JXL in GraphicsMagick before 1.3.46 lacks image dimension resource limits. graphicsmagick · graphicsmagick 2025-03-07 medium5.5 CVE-2020-21679 Buffer Overflow vulnerability in WritePCXImage function in pcx.c in GraphicsMagick 1.4 allows remote attackers to cause a denial of service via converting of c… graphicsmagick · graphicsmagick 2023-08-22 medium6.5 CVE-2019-12921 In GraphicsMagick before 1.3.32, the text filename component allows remote attackers to read arbitrary files via a crafted image because of TranslateTextEx for… graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports_sle +1 2020-03-18 medium6.5 CVE-2019-11474 coders/xwd.c in GraphicsMagick 1.3.31 allows attackers to cause a denial of service (floating-point exception and application crash) by crafting an XWD image f… graphicsmagick · graphicsmagick, fedoraproject · fedora, debian · debian_linux +3 2019-04-23 medium6.5 CVE-2019-11473 coders/xwd.c in GraphicsMagick 1.3.31 allows attackers to cause a denial of service (out-of-bounds read and application crash) by crafting an XWD image file, a… graphicsmagick · graphicsmagick 2019-04-23 medium6.5 CVE-2019-11010 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a memory leak in the function ReadMPCImage of coders/mpc.c, which allows attackers to cause a denial of se… graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · leap 2019-04-08 medium6.5 CVE-2018-20189 In GraphicsMagick 1.3.31, the ReadDIBImage function of coders/dib.c has a vulnerability allowing a crash and denial of service via a dib file that is crafted t… graphicsmagick · graphicsmagick, debian · debian_linux 2018-12-17 medium5.3 CVE-2018-20185 In GraphicsMagick 1.4 snapshot-20181209 Q8 on 32-bit platforms, there is a heap-based buffer over-read in the ReadBMPImage function of bmp.c, which allows atta… graphicsmagick · graphicsmagick, debian · debian_linux, canonical · ubuntu_linux 2018-12-17 medium6.5 CVE-2018-20184 In GraphicsMagick 1.4 snapshot-20181209 Q8, there is a heap-based buffer overflow in the WriteTGAImage function of tga.c, which allows attackers to cause a den… graphicsmagick · graphicsmagick, debian · debian_linux 2018-12-17 medium6.5 CVE-2018-18544 There is a memory leak in the function WriteMSLImage of coders/msl.c in ImageMagick 7.0.8-13 Q16, and the function ProcessMSLScript of coders/msl.c in Graphics… graphicsmagick · graphicsmagick, imagemagick · imagemagick, opensuse · leap 2018-10-21 medium6.5 CVE-2018-9018 In GraphicsMagick 1.3.28, there is a divide-by-zero in the ReadMNGImage function of coders/png.c. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-25 medium6.5 CVE-2017-18231 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 medium6.5 CVE-2017-18230 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 medium6.5 CVE-2017-18229 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 medium6.5 CVE-2017-18219 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-05 medium6.5 CVE-2018-5685 In GraphicsMagick 1.3.27, there is an infinite loop and application hang in the ReadBMPImage function (coders/bmp.c). graphicsmagick · graphicsmagick, debian · debian_linux 2018-01-14 medium6.5 CVE-2017-16353 GraphicsMagick 1.3.26 is vulnerable to a memory information disclosure vulnerability found in the DescribeImage function of the magick/describe.c file, because… graphicsmagick · graphicsmagick, debian · debian_linux 2017-11-01 medium6.5 CVE-2017-15277 ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when processing a GIF file that has neither a gl… graphicsmagick · graphicsmagick, imagemagick · imagemagick 2017-10-12 medium6.5 CVE-2017-14997 GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (excessive memory allocation) because of an integer underflow in ReadPICTImage in co… graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-04 medium6.5 CVE-2017-14994 ReadDCMImage in coders/dcm.c in GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted DICOM image… graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-04 medium6.5 CVE-2017-14733 ReadRLEImage in coders/rle.c in GraphicsMagick 1.3.26 mishandles RLE headers that specify too few colors, which allows remote attackers to cause a denial of se… graphicsmagick · graphicsmagick, debian · debian_linux 2017-09-25 medium5.5 CVE-2017-14649 ReadOneJNGImage in coders/png.c in GraphicsMagick version 1.3.26 does not properly validate JNG data, leading to a denial of service (assertion failure in magi… graphicsmagick · graphicsmagick 2017-09-21 medium6.5 CVE-2017-14504 ReadPNMImage in coders/pnm.c in GraphicsMagick 1.3.26 does not ensure the correct number of colors for the XV 332 format, leading to a NULL Pointer Dereference. graphicsmagick · graphicsmagick, debian · debian_linux 2017-09-17 medium6.5 CVE-2017-14314 Off-by-one error in the DrawImage function in magick/render.c in GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (DrawDashPolygon he… graphicsmagick · graphicsmagick, debian · debian_linux 2017-09-12 medium6.5 CVE-2017-14165 The ReadSUNImage function in coders/sun.c in GraphicsMagick 1.3.26 has an issue where memory allocation is excessive because it depends only on a length field … graphicsmagick · graphicsmagick 2017-09-06 medium6.5 CVE-2017-14042 A memory allocation failure was discovered in the ReadPNMImage function in coders/pnm.c in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick 2017-08-30 medium6.5 CVE-2017-13777 GraphicsMagick 1.3.26 has a denial of service issue in ReadXBMImage() in a coders/xbm.c "Read hex image data" version==10 case that results in the reader not r… graphicsmagick · graphicsmagick, debian · debian_linux 2017-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.