NetSight

Security Dashboard

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

Reset
547 matching advisories · page 15 of 19Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-ghmc-22h2-p86w Malware in mongoose-mongodbMalware npm · mongoose-mongodb 2025-05-14 high8.1 CVE-2025-3085 A MongoDB server under specific conditions running on Linux with TLS and CRL revocation status checking enabled, fails to check the revocation status of the in… mongodb · mongodb 2025-04-01 medium6.5 CVE-2025-3084 When run on commands with certain arguments set, explain may fail to validate these arguments before using them. mongodb · mongodb 2025-04-01 high7.5 CVE-2025-3083 Specifically crafted MongoDB wire protocol messages can cause mongos to crash during command validation. mongodb · mongodb 2025-04-01 low3.1 CVE-2025-3082 A user authorized to access a view may be able to alter the intended collation, allowing them to access to a different or unintended view of underlying data. mongodb · mongodb 2025-04-01 high8.4 CVE-2025-0755 The various bson_append functions in the MongoDB C driver library may be susceptible to buffer overflow when performing operations that could result in a final… mongodb · libbson, mongodb · mongodb 2025-03-18 medium6.5 CVE-2025-27017 Apache NiFi 1.13.0 through 2.2.0 includes the username and password used to authenticate with MongoDB in the NiFi provenance events that MongoDB components gen… maven · org.apache.nifi:nifi-mongodb-services 2025-03-12 high7.5 CVE-2025-1756 mongosh vulnerable to local privilege escalation npm · mongosh 2025-02-27 high7.5 CVE-2025-1755 MongoDB Compass may be susceptible to local privilege escalation under certain conditions potentially enabling unauthorized actions on a user's system with ele… mongodb · compass, redhat · enterprise_linux_for_arm_64, redhat · enterprise_linux_for_ibm_z_systems +2 2025-02-27 low3.9 CVE-2025-1693 The MongoDB Shell may be susceptible to control character injection where an attacker with control over the database cluster contents can inject control charac… npm · mongosh 2025-02-27 medium6.3 CVE-2025-1692 The MongoDB Shell may be susceptible to control character injection where an attacker with control of the user’s clipboard could manipulate them to paste text … npm · mongosh 2025-02-27 high7.6 CVE-2025-1691 The MongoDB Shell may be susceptible to control character injection where an attacker with control of the mongosh autocomplete feature, can use the autocomplet… npm · mongosh 2025-02-27 medium6.8 CVE-2024-10921 An authorized user may trigger crashes or receive the contents of buffer over-reads of Server memory by issuing specially crafted requests that construct malfo… mongodb · mongodb 2024-11-14 low2.2 CVE-2024-8013 A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values in expressions for encrypted fields to be sent to… mongodb · mongo_crypt_v1.so, mongodb · mongocryptd 2024-10-28 medium6.5 CVE-2024-8305 prepareUnique index may cause secondaries to crash due to incorrect enforcement of index constraints on secondaries, where in extreme cases may cause multiple … mongodb · mongodb 2024-10-21 medium5.0 CVE-2024-8654 MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are called in internal aggregation stage. mongodb · mongodb 2024-09-10 medium6.4 CVE-2024-8207 In certain highly specific configurations of the host system and MongoDB server binary installation on Linux Operating Systems, it may be possible for a uninte… mongodb · mongodb 2024-08-27 medium5.3 CVE-2024-6384 "Hot" backup files may be downloaded by underprivileged users, if they are capable of acquiring a unique backup identifier. mongodb · mongodb 2024-08-13 high7.3 CVE-2024-7553 Incorrect validation of files loaded from a local untrusted directory may allow local privilege escalation if the underlying operating systems is Windows. mongodb · mongodb, mongodb · c_driver, mongodb · php_driver 2024-08-07 medium6.7 CVE-2024-35143 IBM Planning Analytics Local 2.0 and 2.1 connects to a MongoDB server. ibm · planning_analytics_workspace, ibm · planning_analytics_local 2024-08-04 medium5.3 CVE-2024-6383 The bson_string_append function in MongoDB C Driver may be vulnerable to a buffer overflow where the function might attempt to allocate too small of buffer and… libbson 2024-07-03 medium6.4 CVE-2024-6382 Incorrect handling of certain string inputs may result in MongoDB Rust driver constructing unintended server commands. rust · mongodb 2024-07-02 medium4.0 CVE-2024-6381 The bson_strfreev function in the MongoDB C driver library may be susceptible to an integer overflow where the function will try to free memory at a negative o… mongodb · libbson 2024-07-02 high7.0 CVE-2024-6376 MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of ejson shell parser in Compass' connectio… npm · @mongodb-js/connection-form 2024-07-01 medium5.4 CVE-2024-6375 A command for refining a collection shard key is missing an authorization check. mongodb · mongodb 2024-07-01 medium4.7 CVE-2024-5629 PyMongo Out-of-bounds Read in the bson module pip · pymongo 2024-06-05 medium5.3 CVE-2024-3374 An unauthenticated user can trigger a fatal assertion in the server while generating ftdc diagnostic metrics due to attempting to build a BSON object that exce… mongodb · mongodb 2024-05-14 high7.5 CVE-2024-3372 Improper validation of certain metadata input may result in the server not correctly serialising BSON. mongodb · mongodb 2024-05-14 high7.1 CVE-2024-3371 MongoDB Compass may accept and use insufficiently validated input from an untrusted external source. mongodb · compass 2024-04-24 medium5.5 CVE-2024-26658 In the Linux kernel, the following vulnerability has been resolved: bcachefs: grab s_umount only if snapshotting When I was testing mongodb over bcachefs with … linux · linux_kernel 2024-04-02

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.