NetSight

Security Dashboard

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

Reset
117 matching advisories · page 1 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-114523 Improper Neutralization of Special Elements used in an OS Command ("OS Command Injection") vulnerability in Drupal Ffmpeg Image Toolkit allows OS Command Injec… Drupal · Ffmpeg Image Toolkit 23 days ago critical9.8 CVE-2026-86189 WWBN AVideo contains a path traversal vulnerability in notify.ffmpeg.json.php that allows unauthenticated attackers to write files to arbitrary locations by su… 2026-09-05 critical9.8 CVE-2026-85696 SadTalker contains an OS command injection vulnerability in the video muxing process where uploaded audio filenames are interpolated into ffmpeg commands witho… 2026-09-04 critical9.8 CVE-2026-75143 FFmpeg before commit 1c10bcc contains a heap buffer overflow in the RIST protocol reader (libavformat/librist.c). 2026-08-19 critical9.3 CVE-2024-58286 dizqueTV 1.5.3 contains a remote code execution vulnerability that allows attackers to inject arbitrary commands through the FFMPEG Executable Path settings. 2025-12-11 critical9.8 CVE-2025-25286 Crayfish is a collection of Islandora 8 microservices, one of which, Homarus, provides FFmpeg as a microservice. composer · islandora/crayfish 2025-01-15 critical9.8 CVE-2024-35368 FFmpeg n7.0 is affected by a Double Free via the rkmpp_retrieve_frame function within libavcodec/rkmppdec.c. ffmpeg · ffmpeg 2024-11-29 critical9.1 CVE-2024-35367 FFmpeg n6.1.1 has an Out-of-bounds Read via libavcodec/ppc/vp8dsp_altivec.c, static const vec_s8 h_subpel_filters_outer ffmpeg · ffmpeg 2024-11-29 critical9.1 CVE-2024-35366 FFmpeg n6.1.1 is Integer Overflow. ffmpeg · ffmpeg 2024-11-29 critical9.8 CVE-2024-31581 FFmpeg version n6.1 was discovered to contain an improper validation of array index vulnerability in libavcodec/cbs_h266_syntax_template.c. ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-17 critical9.8 CVE-2024-22862 Integer overflow vulnerability in FFmpeg before n6.1, allows remote attackers to execute arbitrary code via the JJPEG XL Parser. ffmpeg · ffmpeg 2024-01-27 critical9.8 CVE-2024-22860 Integer overflow vulnerability in FFmpeg before n6.1, allows remote attackers to execute arbitrary code via the jpegxl_anim_read_packet component in the JPEG X… ffmpeg · ffmpeg 2024-01-27 critical GHSA-j799-h2mv-f4c4 Malware in @shenmue_dsc/fluent-ffmpeg-multistream-tsMalware npm · @shenmue_dsc/fluent-ffmpeg-multistream-ts 2024-01-21 critical9.8 CVE-2023-39018 FFmpeg 0.7.0 and below was discovered to contain a code injection vulnerability in the component net.bramp.ffmpeg.FFmpeg.<constructor>. maven · net.bramp.ffmpeg:ffmpeg 2023-07-28 critical9.0 CVE-2022-2566 A heap out-of-bounds memory write exists in FFMPEG since version 5.1. ffmpeg · ffmpeg 2022-09-23 critical GHSA-fv6p-2f2f-rwpv Malware in fluetffmpegMalware npm · fluetffmpeg 2022-08-19 critical9.4 CVE-2020-28435 This affects all versions of package ffmpeg-sdk. npm · ffmpeg-sdk 2022-07-25 critical9.8 CVE-2021-38171 adts_decode_extradata in libavformat/adtsenc.c in FFmpeg 4.4 does not check the init_get_bits return value, which is a necessary step because the second argume… ffmpeg · ffmpeg, debian · debian_linux 2021-08-21 critical9.8 CVE-2021-23376 This affects all versions of package ffmpegdotjs. npm · ffmpegdotjs 2021-04-18 critical9.8 CVE-2020-12284 cbs_jpeg_split_fragment in libavcodec/cbs_jpeg.c in FFmpeg 4.1 and 4.2.2 has a heap-based buffer overflow during JPEG_MARKER_SOS handling because of a missing … ffmpeg · ffmpeg, canonical · ubuntu_linux, debian · debian_linux 2020-04-28 critical9.8 CVE-2019-17542 FFmpeg before 4.2 has a heap-based buffer overflow in vqa_decode_chunk because of an out-of-array access in vqa_decode_init in libavcodec/vqavideo.c. ffmpeg · ffmpeg, canonical · ubuntu_linux, debian · debian_linux 2019-10-14 critical9.8 CVE-2019-17539 In FFmpeg before 4.2, avcodec_open2 in libavcodec/utils.c allows a NULL pointer dereference and possibly unspecified other impact when there is no valid close … ffmpeg · ffmpeg, debian · debian_linux, canonical · ubuntu_linux 2019-10-14 critical9.8 CVE-2019-12730 aa_read_header in libavformat/aadec.c in FFmpeg before 3.2.14 and 4.x before 4.1.4 does not check for sscanf failure and consequently allows use of uninitializ… ffmpeg · ffmpeg 2019-06-04 critical9.8 CVE-2018-1999010 FFmpeg before commit cced03dd667a5df6df8fd40d8de0bff477ee02e8 contains multiple out of array access vulnerabilities in the mms protocol that can result in atta… ffmpeg · ffmpeg, debian · debian_linux 2018-07-23 critical9.8 CVE-2017-16840 The VC-2 Video Compression encoder in FFmpeg 3.0 and 3.4 allows remote attackers to cause a denial of service (out-of-bounds read) because of incorrect buffer … ffmpeg · ffmpeg, debian · debian_linux 2017-11-21 critical9.8 CVE-2013-0870 The 'vp3_decode_frame' function in FFmpeg 1.1.4 moves threads check out of header packet type check. ffmpeg · ffmpeg 2017-08-28 critical9.8 CVE-2012-2781 Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2012-2773, CVE-2012-… ffmpeg · ffmpeg 2017-08-09 critical9.8 CVE-2012-2780 Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2012-2773, CVE-2012-… ffmpeg · ffmpeg 2017-08-09 critical9.8 CVE-2012-2778 Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2012-2773, CVE-2012-… ffmpeg · ffmpeg 2017-08-09 critical9.8 CVE-2012-2773 Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2012-2778, CVE-2012-… ffmpeg · ffmpeg 2017-08-09

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.