NetSight

Security Dashboard

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

Reset
153 matching advisories · page 4 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2025-10924 GIMP FF File Parsing Integer Overflow Remote Code Execution Vulnerability. gimp · gimp 2025-10-29 high7.8 CVE-2025-10923 GIMP WBMP File Parsing Integer Overflow Remote Code Execution Vulnerability. gimp · gimp 2025-10-29 high7.8 CVE-2025-10922 GIMP DCM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. gimp · gimp, debian · debian_linux 2025-10-29 high7.8 CVE-2025-10921 GIMP HDR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. gimp · gimp, debian · debian_linux 2025-10-29 high7.8 CVE-2025-10920 GIMP ICNS File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. gimp · gimp 2025-10-29 high7.8 CVE-2025-8672 MacOS version of GIMP bundles a Python interpreter that inherits the Transparency, Consent, and Control (TCC) permissions granted by the user to the main appli… gimp · gimp 2025-08-11 medium6.1 CVE-2025-6035 A flaw was found in GIMP. gimp · gimp 2025-06-13 high8.8 CVE-2025-5473 GIMP ICO File Parsing Integer Overflow Remote Code Execution Vulnerability. gimp · gimp 2025-06-06 high7.3 CVE-2025-48798 A flaw was found in GIMP when processing XCF image files. 2025-05-27 high7.3 CVE-2025-48797 A flaw was found in GIMP when processing certain TGA image files. 2025-05-27 high7.3 CVE-2025-48796 A flaw was found in GIMP. 2025-05-27 high7.8 CVE-2025-2761 GIMP FLI File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. gimp · gimp 2025-04-23 high7.8 CVE-2025-2760 GIMP XWD File Parsing Integer Overflow Remote Code Execution Vulnerability. gimp · gimp 2025-04-23 high7.8 CVE-2023-44444 GIMP PSP File Parsing Off-By-One Remote Code Execution Vulnerability. gimp · gimp 2024-05-03 high7.8 CVE-2023-44443 GIMP PSP File Parsing Integer Overflow Remote Code Execution Vulnerability. gimp · gimp 2024-05-03 high7.8 CVE-2023-44442 GIMP PSD File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. gimp · gimp 2024-05-03 high7.8 CVE-2023-44441 GIMP DDS File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. gimp · gimp 2024-05-03 medium6.7 CVE-2022-20546 In getCurrentConfigImpl of Effect.cpp, there is a possible out of bounds write due to a missing bounds check. google · android 2022-12-16 medium5.5 CVE-2022-32990 An issue in gimp_layer_invalidate_boundary of GNOME GIMP 2.10.30 allows attackers to trigger an unhandled exception via a crafted XCF file, causing a Denial of… gimp · gimp 2022-06-24 medium5.5 CVE-2022-30067 GIMP 2.10.30 and 2.99.10 are vulnerable to Buffer Overflow. gimp · gimp 2022-05-17 high7.8 CVE-2021-45463 load_cache in GEGL before 0.4.34 allows shell expansion when a pathname in a constructed command line is not escaped or filtered. gegl · gegl, gimp · gimp, redhat · enterprise_linux +1 2021-12-23 critical9.8 CVE-2020-9006 The Popup Builder plugin 2.2.8 through 2.6.7.6 for WordPress is vulnerable to SQL injection (in the sgImportPopups function in sg_popup_ajax.php) via PHP Deser… sygnoos · popup_builder 2020-02-17 critical9.1 CVE-2018-12713 GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp… gimp · gimp 2018-06-24 high7.8 CVE-2017-17789 In GIMP 2.8.22, there is a heap-based buffer overflow in read_channel_data in plug-ins/common/file-psp.c. gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 medium5.5 CVE-2017-17788 In GIMP 2.8.22, there is a stack-based buffer over-read in xcf_load_stream in app/xcf/xcf.c when there is no '\0' character after the version string. gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 high7.8 CVE-2017-17787 In GIMP 2.8.22, there is a heap-based buffer over-read in read_creator_block in plug-ins/common/file-psp.c. gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 high7.8 CVE-2017-17786 In GIMP 2.8.22, there is a heap-based buffer over-read in ReadImage in plug-ins/common/file-tga.c (related to bgr2rgb.part.1) via an unexpected bits-per-pixel … gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 high7.8 CVE-2017-17785 In GIMP 2.8.22, there is a heap-based buffer overflow in the fli_read_brun function in plug-ins/file-fli/fli.c. gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 high7.8 CVE-2017-17784 In GIMP 2.8.22, there is a heap-based buffer over-read in load_image in plug-ins/common/file-gbr.c in the gbr import parser, related to mishandling of UTF-8 da… gimp · gimp, debian · debian_linux, canonical · ubuntu_linux 2017-12-20 high7.3 CVE-2017-14484 The Gentoo sci-mathematics/gimps package before 28.10-r1 for Great Internet Mersenne Prime Search (GIMPS) allows local users to gain privileges by creating a h… gentoo · sci-mathematics-gimps 2017-09-15

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.