NetSight

Security Dashboard

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

Reset
131 matching advisories · page 1 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.2 CVE-2026-125159 ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. TYPO3 · TYPO3 CMS 4 days ago high7.7 CVE-2026-126384 n8n before 1.123.89, 2.x before 2.45.5, 2.46.x before 2.46.1, and 3.x before 3.0.1 bundles a GraphicsMagick version with known vulnerabilities in its official … n8n-io · n8n 8 days ago medium4.3 CVE-2026-103118 A vulnerability was detected in GraphicsMagick up to 1.3.47. GraphicsMagick 52 days ago high8.4 CVE-2026-77118 A heap out-of-bounds write exists in the Photo CD (PCD) decoder of GraphicsMagick. 2026-08-20 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 high7.8 CVE-2022-1270 In GraphicsMagick, a heap buffer overflow was found when parsing MIFF. graphicsmagick · graphicsmagick, debian · debian_linux 2022-09-28 high7.5 CVE-2020-12672 GraphicsMagick through 1.3.35 has a heap-based buffer overflow in ReadMNGImage in coders/png.c. graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports_sle +1 2020-05-06 critical9.8 CVE-2020-10938 GraphicsMagick before 1.3.35 has an integer overflow and resultant heap-based buffer overflow in HuffmanDecodeImage in magick/compress.c. graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports +1 2020-03-24 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 critical9.1 CVE-2019-19953 In GraphicsMagick 1.4 snapshot-20191208 Q8, there is a heap-based buffer over-read in the function EncodeImage of coders/pict.c. graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports +1 2019-12-24 critical9.8 CVE-2019-19951 In GraphicsMagick 1.4 snapshot-20190423 Q8, there is a heap-based buffer overflow in the function ImportRLEPixels of coders/miff.c. graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports +1 2019-12-24 critical9.8 CVE-2019-19950 In GraphicsMagick 1.4 snapshot-20190403 Q8, there is a use-after-free in ThrowException and ThrowLoggedException of magick/error.c. graphicsmagick · graphicsmagick, debian · debian_linux, opensuse · backports +1 2019-12-24 high8.8 CVE-2019-11506 In GraphicsMagick from version 1.3.30 to 1.4 snapshot-20190403 Q8, there is a heap-based buffer overflow in the function WriteMATLABImage of coders/mat.c, whic… graphicsmagick · graphicsmagick, debian · debian_linux, canonical · ubuntu_linux +2 2019-04-24 high8.8 CVE-2019-11505 In GraphicsMagick from version 1.3.8 to 1.4 snapshot-20190403 Q8, there is a heap-based buffer overflow in the function WritePDBImage of coders/pdb.c, which al… graphicsmagick · graphicsmagick, debian · debian_linux, canonical · ubuntu_linux +2 2019-04-24 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 high8.1 CVE-2019-11009 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based buffer over-read in the function ReadXWDImage of coders/xwd.c, which allows attackers to caus… graphicsmagick · graphicsmagick, opensuse · leap, debian · debian_linux 2019-04-08 high8.8 CVE-2019-11008 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based buffer overflow in the function WriteXWDImage of coders/xwd.c, which allows remote attackers … graphicsmagick · graphicsmagick, opensuse · backports_sle, opensuse · leap +2 2019-04-08 high8.1 CVE-2019-11007 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based buffer over-read in the ReadMNGImage function of coders/png.c, which allows attackers to caus… graphicsmagick · graphicsmagick, opensuse · backports_sle, opensuse · leap +2 2019-04-08 critical9.1 CVE-2019-11006 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based buffer over-read in the function ReadMIFFImage of coders/miff.c, which allows attackers to ca… graphicsmagick · graphicsmagick, opensuse · leap, debian · debian_linux 2019-04-08 critical9.8 CVE-2019-11005 In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a stack-based buffer overflow in the function SVGStartElement of coders/svg.c, which allows remote attacke… graphicsmagick · graphicsmagick, opensuse · leap 2019-04-08 high7.5 CVE-2019-7397 In ImageMagick before 7.0.8-25 and GraphicsMagick through 1.3.31, several memory leaks exist in WritePDFImage in coders/pdf.c. imagemagick · imagemagick, graphicsmagick · graphicsmagick, opensuse · leap +2 2019-02-05 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

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.