NetSight

Security Dashboard

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

Reset
156 matching advisories · page 1 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2025-8537 A vulnerability, which was classified as problematic, was found in Axiomatic Bento4 up to 1.6.0-641. axiosys · bento4 2025-08-05 medium5.5 CVE-2025-25947 An issue in Bento4 v1.6.0-641 allows an attacker to trigger a segmentation fault via Ap4Atom.cpp, specifically in AP4_AtomParent::RemoveChild, during the execu… axiosys · bento4 2025-02-19 medium5.5 CVE-2025-25946 An issue in Bento4 v1.6.0-641 allows an attacker to cause a memory leak via Ap4Marlin.cpp and Ap4Processor.cpp, specifically in AP4_MarlinIpmpEncryptingProcess… axiosys · bento4 2025-02-19 medium6.5 CVE-2025-25945 An issue in Bento4 v1.6.0-641 allows an attacker to obtain sensitive information via the the Mp4Fragment.cpp and in AP4_DescriptorFactory::CreateDescriptorFrom… axiosys · bento4 2025-02-19 high7.3 CVE-2025-25944 Buffer Overflow vulnerability in Bento4 v.1.6.0-641 allows a local attacker to execute arbitrary code via the Ap4RtpAtom.cpp, specifically in AP4_RtpAtom::AP4_… axiosys · bento4 2025-02-19 high7.8 CVE-2025-25943 Buffer Overflow vulnerability in Bento4 v.1.6.0-641 allows a local attacker to execute arbitrary code via the AP4_Stz2Atom::AP4_Stz2Atom component located in A… axiosys · bento4 2025-02-19 medium6.5 CVE-2025-25942 An issue in Bento4 v1.6.0-641 allows an attacker to obtain sensitive information via the the mp4fragment tool when processing invalid files. axiosys · bento4 2025-02-19 medium6.5 CVE-2024-57598 A floating point exception (divide-by-zero) vulnerability was discovered in Bento4 1.6.0-641 in function AP4_TfraAtom() of Ap4TfraAtom.cpp which allows a remot… axiosys · bento4 2025-02-05 medium5.6 CVE-2025-0870 A vulnerability was found in Axiomatic Bento4 up to 1.6.0-641. axiosys · bento4 2025-01-30 medium6.3 CVE-2025-0753 A vulnerability classified as critical was found in Axiomatic Bento4 up to 1.6.0. axiosys · bento4 2025-01-27 medium6.3 CVE-2025-0751 A vulnerability classified as critical has been found in Axiomatic Bento4 up to 1.6.0. axiosys · bento4 2025-01-27 high7.5 CVE-2024-30809 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 low2.7 CVE-2024-30808 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 high7.5 CVE-2024-30807 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 medium6.5 CVE-2024-30806 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 high8.1 CVE-2024-31005 An issue in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the Ap4MdhdAtom.cpp,AP4_MdhdAtom::AP4_MdhdAtom,mp4fragment axiosys · bento4 2024-04-02 critical9.8 CVE-2024-31004 An issue in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the Ap4StsdAtom.cpp,AP4_StsdAtom::AP4_StsdAtom,mp4fragment. axiosys · bento4 2024-04-02 high8.8 CVE-2024-31003 Buffer Overflow vulnerability in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the AP4_MemoryByteStream::WritePartial at Ap4B… axiosys · bento4 2024-04-02 critical9.8 CVE-2024-31002 Buffer Overflow vulnerability in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the AP4 BitReader::ReadCache() at Ap4Utils.cpp… axiosys · bento4 2024-04-02 medium6.5 CVE-2024-24155 Bento4 v1.5.1-628 contains a Memory leak on AP4_Movie::AP4_Movie, parsing tracks and added into m_Tracks list, but mp42aac cannot correctly delete when we got … axiosys · bento4 2024-02-29 medium5.5 CVE-2024-25454 Bento4 v1.6.0-640 was discovered to contain a NULL pointer dereference via the AP4_DescriptorFinder::Test() function. axiosys · bento4 2024-02-09 medium5.5 CVE-2024-25453 Bento4 v1.6.0-640 was discovered to contain a NULL pointer dereference via the AP4_StszAtom::GetSampleSize() function. axiosys · bento4 2024-02-09 medium5.5 CVE-2024-25452 Bento4 v1.6.0-640 was discovered to contain an out-of-memory bug via the AP4_UrlAtom::AP4_UrlAtom() function. axiosys · bento4 2024-02-09 medium6.5 CVE-2024-25451 Bento4 v1.6.0-640 was discovered to contain an out-of-memory bug via the AP4_DataBuffer::ReallocateBuffer() function. axiosys · bento4 2024-02-09 medium5.5 CVE-2023-38666 Bento4 v1.6.0-639 was discovered to contain a segmentation violation via the AP4_Processor::ProcessFragments function in mp4encrypt. axiosys · bento4 2023-08-22 medium5.5 CVE-2023-29575 Bento4 v1.6.0-639 was discovered to contain an out-of-memory bug in the mp42aac component. axiosys · bento4 2023-04-21 medium5.5 CVE-2023-29573 Bento4 v1.6.0-639 was discovered to contain an out-of-memory bug in the mp4info component. axiosys · bento4 2023-04-13 medium5.5 CVE-2023-29574 Bento4 v1.6.0-639 was discovered to contain an out-of-memory bug in the mp42avc component. axiosys · bento4 2023-04-12 medium5.5 CVE-2023-29576 Bento4 v1.6.0-639 was discovered to contain a segmentation violation via the AP4_TrunAtom::SetDataOffset(int) function in Ap4TrunAtom.h. axiosys · bento4 2023-04-11 medium6.3 CVE-2022-4584 A vulnerability was found in Axiomatic Bento4 up to 1.6.0-639. axiosys · bento4 2022-12-17

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.