NetSight

Security Dashboard

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

Reset
36 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.7 CVE-2026-120208 libheif 1.18.0 before 1.23.3 contains a heap-based buffer overflow vulnerability in unc_decoder_mixed_interleave::processTile() that allows attackers to write … strukturag · libheif 21 days ago high7.1 CVE-2026-48029 libheif is a HEIF and AVIF file format decoder and encoder. struktur · libheif 2026-07-22 high7.5 CVE-2026-47247 libheif is a HEIF and AVIF file format decoder and encoder. struktur · libheif 2026-07-21 high7.5 CVE-2026-57803 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Struktur Core allows PHP… Struktur Core: from n/a 2026-07-13 high7.5 CVE-2026-57802 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Struktur allows PHP Loca… Struktur: from n/a 2026-07-13 high7.1 CVE-2026-49346 libde265 is an open source implementation of the h.265 video codec. struktur · libde265 2026-06-19 high7.1 CVE-2026-49295 libde265 is an open source implementation of the h.265 video codec. struktur · libde265 2026-06-19 high8.1 CVE-2026-41071 libheif is a HEIF and AVIF file format decoder and encoder. struktur · libheif 2026-05-22 high8.8 CVE-2026-32740 libheif is a HEIF and AVIF file format decoder and encoder. struktur · libheif 2026-05-19 high7.4 CVE-2026-45575 epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. maven · com.oviva.telematik:epa4all-client 2026-05-15 high8.1 CVE-2026-45574 epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. maven · com.oviva.telematik:epa4all-client 2026-05-15 high8.1 CVE-2026-44900 epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. maven · com.oviva.telematik:epa4all-client 2026-05-08 high7.5 CVE-2026-33164 libde265 is an open source implementation of the h.265 video codec. struktur · libde265 2026-03-20 high8.1 CVE-2025-69407 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Struktur struktur allows… Struktur: from n/a through 2026-02-20 high8.1 CVE-2024-41311 In Libheif 1.17.6, insufficient checks in ImageOverlay::parse() decoding a heif file containing an overlay image with forged offsets can lead to an out-of-boun… struktur · libheif, debian · debian_linux 2024-10-15 high7.5 CVE-2024-25269 libheif <= 1.17.6 contains a memory leak in the function JpegEncoder::Encode. struktur · libheif 2024-03-05 high8.8 CVE-2023-49468 Libde265 v1.0.14 was discovered to contain a global buffer overflow vulnerability in the read_coding_unit function at slice.cc. struktur · libde265 2023-12-07 high8.8 CVE-2023-49467 Libde265 v1.0.14 was discovered to contain a heap-buffer-overflow vulnerability in the derive_combined_bipredictive_merging_candidates function at motion.cc. struktur · libde265 2023-12-07 high8.8 CVE-2023-49465 Libde265 v1.0.14 was discovered to contain a heap-buffer-overflow vulnerability in the derive_spatial_luma_vector_prediction function at motion.cc. struktur · libde265 2023-12-07 high8.8 CVE-2023-49464 libheif v1.17.5 was discovered to contain a segmentation violation via the function UncompressedImageCodec::get_luma_bits_per_pixel_from_configuration_unci. struktur · libheif 2023-12-07 high8.8 CVE-2023-49463 libheif v1.17.5 was discovered to contain a segmentation violation via the function find_exif_tag at /libheif/exif.cc. struktur · libheif 2023-12-07 high8.8 CVE-2023-49462 libheif v1.17.5 was discovered to contain a segmentation violation via the component /libheif/exif.cc. struktur · libheif 2023-12-07 high8.8 CVE-2023-49460 libheif v1.17.5 was discovered to contain a segmentation violation via the function UncompressedImageCodec::decode_uncompressed_image. struktur · libheif 2023-12-07 high8.1 CVE-2023-43887 Libde265 v1.0.12 was discovered to contain multiple buffer overflows via the num_tile_columns and num_tile_row parameters in the function pic_parameter_set::du… struktur · libde265 2023-11-22 high8.8 CVE-2023-27103 Libde265 v1.0.11 was discovered to contain a heap buffer overflow via the function derive_collocated_motion_vectors at motion.cc. struktur · libde265 2023-03-15 high7.8 CVE-2022-47665 Libde265 1.0.9 has a heap buffer overflow vulnerability in de265_image::set_SliceAddrRS(int, int, int) struktur · libde265 2023-03-03 high7.8 CVE-2022-47664 Libde265 1.0.9 is vulnerable to Buffer Overflow in ff_hevc_put_hevc_qpel_pixels_8_sse struktur · libde265 2023-03-03 high7.8 CVE-2023-25221 Libde265 v1.0.10 was discovered to contain a heap-buffer-overflow vulnerability in the derive_spatial_luma_vector_prediction function in motion.cc. struktur · libde265, debian · debian_linux 2023-03-01 high7.8 CVE-2023-0996 There is a vulnerability in the strided image data parsing code in the emscripten wrapper for libheif. struktur · libheif 2023-02-24 high7.8 CVE-2022-47655 Libde265 1.0.9 is vulnerable to Buffer Overflow in function void put_qpel_fallback<unsigned short> struktur · libde265, debian · debian_linux 2023-01-05

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.