NetSight

Security Dashboard

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

Reset
282 matching advisories · page 7 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-6914 Computing the MD5 checksum of a malformed BSON object under specific conditions may cause loss of availability in MongoDB server. mongodb · mongodb 2026-04-29 medium4.3 CVE-2026-6231 The bson_validate function may return early on specific inputs and incorrectly report success. mongodb · c_driver 2026-04-13 medium5.3 CVE-2026-5170 A user with access to the cluster with a limited set of privilege actions can trigger a crash of a mongod process during the limited and unpredictable window w… mongodb · mongodb 2026-03-30 medium6.4 CVE-2026-4358 A specially crafted aggregation query with $lookup by an authenticated user with write privileges can cause a double-free or use-after-free memory issue in the… mongodb · mongodb 2026-03-17 medium6.5 CVE-2026-4147 An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command. mongodb · mongodb 2026-03-17 medium6.5 CVE-2026-2303 mongo-go-driver has Heap Out-of-Bounds Read in GSSAPI Error Handling go · go.mongodb.org/mongo-driver, go · go.mongodb.org/mongo-driver/v2 2026-02-10 medium6.5 CVE-2026-25613 An authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index. mongodb · mongodb 2026-02-10 medium6.5 CVE-2026-25610 An authorized user may trigger a server crash by running a $geoNear pipeline with certain invalid index hints. mongodb · mongodb 2026-02-10 medium5.4 CVE-2026-25609 Incorrect validation of the profile command may result in the determination that a request altering the 'filter' is read-only. mongodb · mongodb 2026-02-10 medium6.5 CVE-2026-1850 Complex queries can cause excessive memory usage in MongoDB Query Planner resulting in an Out-Of-Memory Crash. mongodb · mongodb 2026-02-10 medium6.5 CVE-2026-1849 MongoDB Server may experience an out-of-memory failure while evaluating expressions that produce deeply nested documents. mongodb · mongodb 2026-02-10 medium6.5 CVE-2026-1847 Inserting certain large documents into a replica set could lead to replica set secondaries not being able to fetch the oplog from the primary. mongodb · mongodb 2026-02-10 medium6.5 CVE-2026-25612 The internal locking mechanism of the MongoDB server uses an internal encoding of the resources in order to choose what lock to take. 2026-02-10 medium6.5 CVE-2025-14911 User-controlled chunkSize metadata from MongoDB lacks appropriate validation allowing malformed GridFS metadata to overflow the bounding container. 2026-01-27 medium6.5 CVE-2026-0529 Improper Validation of Array Index (CWE-129) in Packetbeat’s MongoDB protocol parser can allow an attacker to cause Overflow Buffers (CAPEC-100) through specia… 2026-01-14 medium4.2 CVE-2025-14345 A post-authentication flaw in the network two-phase commit protocol used for cross-shard transactions in MongoDB Server may lead to logical data inconsistencie… mongodb · mongodb 2025-12-09 medium6.5 CVE-2025-13644 MongoDB Server may experience an invariant failure during batched delete operations when handling documents. mongodb · mongodb 2025-11-25 medium6.5 CVE-2025-13507 Inconsistent object size validation in time series processing logic may result in later processing of oversized BSON documents leading to an assert failing and… mongodb · mongodb 2025-11-25 medium4.2 CVE-2025-12893 Clients may successfully perform a TLS handshake with a MongoDB server despite presenting a client certificate not aligning with the documented Extended Key Us… mongodb · mongodb 2025-11-25 medium6.8 CVE-2025-12119 MongoDB driver extension affected by mongoc_bulk_operation_t's read of invalid memory composer · mongodb/mongodb-extension 2025-11-18 medium5.4 CVE-2025-63291 When processing API requests, the Alteryx server 2022.1.1.42654 and 2024.1 used MongoDB object IDs to uniquely identify the data being requested by the caller. alteryx · alteryx_server 2025-11-14 medium5.0 CVE-2025-12657 The KMIP response parser built into mongo binaries is overly tolerant of certain malformed packets, and may parse them into invalid objects. mongodb · mongodb 2025-11-03 medium5.3 CVE-2025-11979 An authorized user may crash the MongoDB server by causing buffer over-read. mongodb · mongodb 2025-10-20 medium6.5 CVE-2025-10061 An authorized user can cause a crash in the MongoDB Server through a specially crafted $group query. mongodb · mongodb 2025-09-05 medium6.5 CVE-2025-10060 MongoDB Server may allow upsert operations retried within a transaction to violate unique index constraints, potentially causing an invariant failure and serve… mongodb · mongodb 2025-09-05 medium6.5 CVE-2025-10059 An improper setting of the lsid field on any sharded query can cause a crash in MongoDB routers. mongodb · mongodb 2025-09-05 medium6.5 CVE-2025-7259 An authorized user can issue queries with duplicate _id fields, that leads to unexpected behavior in MongoDB Server, which may result to crash. mongodb · mongodb 2025-07-07 medium6.5 CVE-2025-6712 MongoDB Server may be susceptible to disruption caused by high memory usage, potentially leading to server crash. mongodb · mongodb 2025-07-07 medium4.4 CVE-2025-6711 An issue has been identified in MongoDB Server where unredacted queries may inadvertently appear in server logs when certain error conditions are encountered. mongodb · mongodb 2025-07-07 medium4.2 CVE-2025-6707 Under certain conditions, an authenticated user request may execute with stale privileges following an intentional change by an authorized administrator. mongodb · mongodb 2025-06-26

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.