NetSight

Security Dashboard

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

Reset
351 matching advisories · page 5 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2025-7700 A flaw was found in FFmpeg’s ALS audio decoder, where it does not properly check for memory allocation failures. 2025-11-07 medium5.3 CVE-2025-57611 An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) Null pointer dereference vulnerability in the dump() method allows an attacker to cause a de… meh.schizofreni · rust-ffmpeg 2025-09-02 medium5.3 CVE-2024-55069 ffmpeg 7.1 is vulnerable to Null Pointer Dereference in function iamf_read_header in /libavformat/iamfdec.c. ffmpeg · ffmpeg 2025-05-02 medium4.3 CVE-2025-1816 A vulnerability classified as problematic has been found in FFmpeg up to 6e26f57f672b05e7b8b052007a83aef99dc81ccb. 2025-03-02 medium6.3 CVE-2025-1594 A vulnerability, which was classified as critical, was found in FFmpeg up to 7.1. ffmpeg · ffmpeg 2025-02-23 medium5.3 CVE-2025-25473 FFmpeg git master before commit c08d30 was discovered to contain a memory leak in the avformat_free_context function in libavutil/mem.c. 2025-02-18 medium4.3 CVE-2025-25471 FFmpeg git master before commit fd1772 was discovered to contain a NULL pointer dereference via the component libavformat/mov.c. 2025-02-18 medium5.3 CVE-2025-22920 A heap buffer overflow vulnerability in FFmpeg before commit 4bf784c allows attackers to trigger a memory corruption via supplying a crafted media file in avfo… 2025-02-18 medium6.5 CVE-2025-22919 A reachable assertion in FFmpeg git-master commit N-113007-g8d24a28d06 allows attackers to cause a Denial of Service (DoS) via opening a crafted AAC file. 2025-02-18 medium6.5 CVE-2025-25468 FFmpeg git-master before commit d5873b was discovered to contain a memory leak in the component libavutil/mem.c. ffmpeg · ffmpeg 2025-02-18 medium6.5 CVE-2025-22921 FFmpeg git-master,N-113007-g8d24a28d06 was discovered to contain a segmentation violation via the component /libavcodec/jpeg2000dec.c. ffmpeg · ffmpeg, debian · debian_linux 2025-02-18 medium5.3 CVE-2025-0518 Unchecked Return Value, Out-of-bounds Read vulnerability in FFmpeg allows Read Sensitive Constants Within an Executable. ffmpeg · ffmpeg 2025-01-16 medium5.3 CVE-2023-6604 A flaw was found in FFmpeg. ffmpeg · ffmpeg 2025-01-06 medium4.7 CVE-2023-6601 A flaw was found in FFmpeg's HLS demuxer. ffmpeg · ffmpeg 2025-01-06 medium6.2 CVE-2024-36613 FFmpeg n6.1.1 has a vulnerability in the DXA demuxer of the libavformat library allowing for an integer overflow, potentially resulting in a denial-of-service … ffmpeg · ffmpeg 2025-01-03 medium5.3 CVE-2023-6602 A flaw was found in FFmpeg's TTY Demuxer. ffmpeg · ffmpeg 2024-12-31 medium6.5 CVE-2024-36616 An integer overflow in the component /libavformat/westwood_vqa.c of FFmpeg n6.1.1 allows attackers to cause a denial of service in the application via a crafte… ffmpeg · ffmpeg 2024-11-29 medium5.9 CVE-2024-36615 FFmpeg n7.0 has a race condition vulnerability in the VP9 decoder. ffmpeg · ffmpeg 2024-11-29 medium6.2 CVE-2024-36618 FFmpeg n6.1.1 has a vulnerability in the AVI demuxer of the libavformat library which allows for an integer overflow, potentially resulting in a denial-of-serv… ffmpeg · ffmpeg 2024-11-29 medium6.2 CVE-2024-36617 FFmpeg n6.1.1 has an integer overflow vulnerability in the FFmpeg CAF decoder. ffmpeg · ffmpeg 2024-11-29 medium5.3 CVE-2024-36619 FFmpeg n6.1.1 has a vulnerability in the WAVARC decoder of the libavcodec library which allows for an integer overflow when handling certain block types, leadi… ffmpeg · ffmpeg 2024-11-29 medium5.5 CVE-2024-35369 In FFmpeg version n6.1.1, specifically within the avcodec/speexdec.c module, a potential security vulnerability exists due to insufficient validation of certai… ffmpeg · ffmpeg 2024-11-29 medium6.3 CVE-2024-7272 A vulnerability, which was classified as critical, was found in FFmpeg up to 5.1.5. ffmpeg · ffmpeg 2024-08-12 medium6.3 CVE-2024-7055 A vulnerability was found in FFmpeg up to 7.0.1. ffmpeg · ffmpeg 2024-08-06 medium6.6 CVE-2024-32228 FFmpeg 7.0 is vulnerable to Buffer Overflow. ffmpeg · ffmpeg 2024-07-01 medium6.7 CVE-2023-51797 Buffer Overflow vulnerability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavfilter/avf_showwaves.c:722:24 in s… ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-19 medium4.0 CVE-2023-50007 FFmpeg v.n6.1-3-g466799d4f5 allows an attacker to trigger use of a parameter of negative size in the av_samples_set_silence function in thelibavutil/samplefmt.… ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-19 medium5.3 CVE-2024-31585 FFmpeg version n5.1 to n6.1 was discovered to contain an Off-by-one Error vulnerability in libavfilter/avf_showspectrum.c. ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-17 medium5.5 CVE-2023-46407 FFmpeg prior to commit bf814 was discovered to contain an out of bounds read via the dist->alphabet_size variable in the read_vlc_prefix() function. ffmpeg · ffmpeg 2023-10-27 medium5.5 CVE-2021-28429 Integer overflow vulnerability in av_timecode_make_string in libavutil/timecode.c in FFmpeg version 4.3.2, allows local attackers to cause a denial of service … ffmpeg · ffmpeg 2023-08-11

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.