NetSight

Security Dashboard

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

Reset
21 matching advisories · page 1 of 1Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-44637 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-05-14 high7.4 CVE-2026-44636 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-05-14 high7.8 CVE-2026-33023 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-04-14 high7.3 CVE-2026-33021 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-04-14 high7.1 CVE-2026-33020 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-04-14 high7.1 CVE-2026-33019 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-04-14 high7.0 CVE-2026-33018 libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. saitoha · libsixel 2026-04-14 high8.8 CVE-2022-27046 libsixel 1.8.6 suffers from a Heap Use After Free vulnerability in in libsixel/src/dither.c:388. saitoha · libsixel 2022-04-08 high8.8 CVE-2022-27044 libsixel 1.8.6 is affected by Buffer Overflow in libsixel/src/quant.c:876. saitoha · libsixel 2022-04-08 high8.8 CVE-2020-21548 Libsixel 1.8.3 contains a heap-based buffer overflow in the sixel_encode_highcolor function in tosixel.c. saitoha · libsixel 2021-09-17 high8.8 CVE-2020-21547 Libsixel 1.8.2 contains a heap-based buffer overflow in the dither_func_fs function in tosixel.c. saitoha · libsixel 2021-09-17 high7.5 CVE-2020-36120 Buffer Overflow in the "sixel_encoder_encode_bytes" function of Libsixel v1.8.6 allows attackers to cause a Denial of Service (DoS). saitoha · libsixel 2021-04-14 high8.8 CVE-2019-20205 libsixel 1.8.4 has an integer overflow in sixel_frame_resize in frame.c. saitoha · libsixel 2020-01-02 high8.8 CVE-2019-20140 An issue was discovered in libsixel 1.8.4. saitoha · libsixel 2019-12-30 high8.8 CVE-2019-20094 An issue was discovered in libsixel 1.8.4. saitoha · libsixel 2019-12-30 high8.8 CVE-2019-19778 An issue was discovered in libsixel 1.8.2. saitoha · libsixel 2019-12-13 high8.8 CVE-2019-19777 stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main. nothings · stb_image.h, saitoha · libsixel 2019-12-13 high7.8 CVE-2019-3574 In libsixel v1.8.2, there is a heap-based buffer over-read in the function load_jpeg() in the file loader.c, as demonstrated by img2sixel. saitoha · libsixel 2019-01-02 high7.8 CVE-2018-19762 There is a heap-based buffer overflow at fromsixel.c (function: image_buffer_resize) in libsixel 1.8.2 that will cause a denial of service or possibly unspecif… saitoha · libsixel 2018-11-30 high7.5 CVE-2018-14073 libsixel 1.8.1 has a memory leak in sixel_allocator_new in allocator.c. saitoha · libsixel 2018-07-15 high7.5 CVE-2018-14072 libsixel 1.8.1 has a memory leak in sixel_decoder_decode in decoder.c, image_buffer_resize in fromsixel.c, and sixel_decode_raw in fromsixel.c. saitoha · libsixel 2018-07-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.