NetSight

Security Dashboard

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

Reset
50 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-122328 SDL_mixer 3.1.2 through 3.2.4 contains a stack-based buffer overflow vulnerability in FetchXLaw() of src/decoder_wav.c when decoding A-law or mu-law WAV files. libsdl-org · SDL_mixer 16 days ago high7.8 CVE-2026-122329 SDL_mixer 3.1.2 through 3.2.4 contains a stack-based buffer overflow in FetchXLaw() in src/decoder_aiff.c due to miscalculated output offsets when expanding A-… libsdl-org · SDL_mixer 16 days ago high7.1 CVE-2026-35444 SDL_image is a library to load images of various formats as SDL surfaces. libsdl · sdl_image 2026-04-06 medium5.5 CVE-2023-39114 ngiflib commit 84a75 was discovered to contain a segmentation violation via the function SDL_LoadAnimatedGif at ngiflibSDL.c. miniupnp_project · ngiflib 2023-08-02 high7.5 CVE-2022-4743 A potential memory leak issue was discovered in SDL2 in GLES_CreateTexture() function in SDL_render_gles.c. libsdl · simple_directmedia_layer, redhat · enterprise_linux 2023-01-12 high7.5 CVE-2022-34568 SDL v1.2 was discovered to contain a use-after-free via the XFree function at /src/video/x11/SDL_x11yuv.c. libsdl · simple_directmedia_layer 2022-07-28 high7.8 CVE-2022-27470 SDL_ttf v2.0.18 and below was discovered to contain an arbitrary memory write via the function TTF_RenderText_Solid(). libsdl · sdl_ttf, fedoraproject · fedora 2022-05-04 high8.8 CVE-2021-33657 There is a heap overflow problem in video/SDL_pixels.c in SDL (Simple DirectMedia Layer) 2.x to 2.0.18 versions. libsdl · simple_directmedia_layer 2022-04-01 medium5.4 CVE-2020-14410 SDL (Simple DirectMedia Layer) through 2.0.12 has a heap-based buffer over-read in Blit_3or4_to_3or4__inversed_rgb in video/SDL_blit_N.c via a crafted .BMP fil… libsdl · simple_directmedia_layer, debian · debian_linux, fedoraproject · fedora 2021-01-19 high7.8 CVE-2020-14409 SDL (Simple DirectMedia Layer) through 2.0.12 has an Integer Overflow (and resultant SDL_memcpy heap corruption) in SDL_BlitCopy in video/SDL_blit_copy.c via a… libsdl · simple_directmedia_layer, fedoraproject · fedora, debian · debian_linux +1 2021-01-19 critical9.8 CVE-2019-14906 A flaw was found with the RHSA-2019:3950 erratum, where it did not fix the CVE-2019-13616 SDL vulnerability. libsdl · simple_directmedia_layer, redhat · enterprise_linux 2020-01-07 high8.8 CVE-2019-5060 An exploitable code execution vulnerability exists in the XPM image rendering function of SDL2_image 2.0.4. libsdl · sdl2_image, opensuse · backports_sle, opensuse · leap 2019-07-31 high8.8 CVE-2019-5059 An exploitable code execution vulnerability exists in the XPM image rendering functionality of SDL2_image 2.0.4. libsdl · sdl2_image, opensuse · backports_sle, opensuse · leap 2019-07-31 high8.8 CVE-2019-5058 An exploitable code execution vulnerability exists in the XCF image rendering functionality of SDL2_image 2.0.4. libsdl · sdl2_image, opensuse · backports_sle, opensuse · leap 2019-07-31 high8.8 CVE-2019-5057 An exploitable code execution vulnerability exists in the PCX image-rendering functionality of SDL2_image 2.0.4. libsdl · sdl2_image, opensuse · backports_sle, opensuse · leap 2019-07-31 medium6.5 CVE-2019-13626 SDL (Simple DirectMedia Layer) 2.x through 2.0.9 has a heap-based buffer over-read in Fill_IMA_ADPCM_block, caused by an integer overflow in IMA_ADPCM_decode()… libsdl · libsdl, fedoraproject · fedora, debian · debian_linux +1 2019-07-17 high8.1 CVE-2019-13616 SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in BlitNtoN in video/SDL_blit_N.c when called from SDL_So… libsdl · simple_directmedia_layer, debian · debian_linux, opensuse · backports_sle +9 2019-07-16 high8.8 CVE-2019-5052 An exploitable integer overflow vulnerability exists when loading a PCX file in SDL2_image 2.0.4. libsdl · sdl2_image, debian · debian_linux, opensuse · backports_sle +2 2019-07-03 high8.8 CVE-2019-5051 An exploitable heap-based buffer overflow vulnerability exists when loading a PCX file in SDL2_image, version 2.0.4. libsdl · sdl2_image, debian · debian_linux, opensuse · backports_sle +2 2019-07-03 medium6.5 CVE-2019-12222 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9. libsdl · simple_directmedia_layer 2019-05-20 medium6.5 CVE-2019-12221 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer, fedoraproject · fedora +4 2019-05-20 medium6.5 CVE-2019-12220 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer 2019-05-20 high8.8 CVE-2019-12219 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer 2019-05-20 medium6.5 CVE-2019-12218 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer 2019-05-20 medium6.5 CVE-2019-12217 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer 2019-05-20 medium6.5 CVE-2019-12216 An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.0.4. libsdl · sdl2_image, libsdl · simple_directmedia_layer, fedoraproject · fedora +2 2019-05-20 high8.8 CVE-2019-7638 SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in Map1toN in video/SDL_pixels.c. libsdl · simple_directmedia_layer, debian · debian_linux, opensuse · leap +2 2019-02-08 high8.8 CVE-2019-7637 SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer overflow in SDL_FillRect in video/SDL_surface.c. libsdl · simple_directmedia_layer, debian · debian_linux, opensuse · leap +2 2019-02-08 high8.1 CVE-2019-7636 SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in SDL_GetRGB in video/SDL_pixels.c. libsdl · simple_directmedia_layer, opensuse · leap, debian · debian_linux +2 2019-02-08 high8.1 CVE-2019-7635 SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a heap-based buffer over-read in Blit1to4 in video/SDL_blit_1.c. libsdl · simple_directmedia_layer, opensuse · backports_sle, opensuse · leap +3 2019-02-08

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.