CVEs.

Latest CVEs

1. 7.1High

   CVE-2024-14047 ↗ (opens in a new tab)

   A local vulnerability in the Winlogbeat Windows installer caused runtime files to be placed in a directory writable by unprivileged users. A low-privileged attacker with existing access to the system could pre-position malicious filesystem links, causing a subsequent elevated Winlogbeat operation to write to or delete arbitrary files. Successful exploitation could result in a denial of service.

   ECElastic Cloud· Sep 1, 2026

2. 8.8High

   CVE-2026-82642 ↗ (opens in a new tab)

   Readest is an open-source e-book reader built on Tauri. In versions prior to 0.11.16, EPUB chapter HTML is sanitized with DOMPurify using a configuration that forbade only the <script> tag (FORBID_TAGS: ['script']) in apps/readest-app/src/services/transformers/sanitizer.ts. DOMPurify does not parse the contents of the srcdoc attribute on <iframe> elements, treating it as an opaque string attribute, so an attacker who can get an <iframe> element to survive sanitization can embed a complete HTML document containing a <script> tag inside srcdoc and have it execute when the browser renders the ifr

   JFJFrog· Aug 30, 2026

3. 8.8High

   CVE-2026-82635 ↗ (opens in a new tab)

   Pake before 3.13.1 joins the JavaScript-supplied filename for the download_file Tauri command onto the user's Downloads directory with no sanitization. A filename containing path traversal sequences (for example ../Library/LaunchAgents/com.evil.plist) or an absolute path resolves outside ~/Downloads. The command then fetches attacker-controlled content from the supplied URL (via Rust HTTP, not the browser) and writes it to that path. A script that can invoke the command can overwrite user-writable files and install persistence (macOS LaunchAgents, Linux autostart, Windows Startup), leading to

   JFJFrog· Aug 30, 2026

4. 6.0Med

   CVE-2026-81533 ↗ (opens in a new tab)

   An application using the MongoDB BI Connector ODBC Driver may encounter a memory-safety issue when a submitted SQL statement contains an unusually long run of digits following a LIMIT clause. The issue occurs only on connections where the driver's optional prefetch setting is enabled, and stems from the driver copying the digit sequence into a fixed-size internal buffer without checking its length. A user able to influence the numeric portion of a LIMIT clause could cause the hosting application process to terminate unexpectedly or corrupt adjacent memory in that process.

   MAMongoDB Atlas· Aug 28, 2026

5. 8.7High

   CVE-2026-81532 ↗ (opens in a new tab)

   A user able to submit SQL through an application using the MongoDB Connector for BI ODBC driver can supply a positioned-cursor statement whose cursor name exceeds the size of an internal fixed-length buffer. Because the name length is not bounded before the driver builds its diagnostic message, memory adjacent to that buffer is overwritten with user-supplied content. This can terminate the hosting application process and may allow unintended code to run within it.

   MAMongoDB Atlas· Aug 28, 2026

6. 8.7High

   CVE-2026-81520 ↗ (opens in a new tab)

   A network-reachable client that has not yet authenticated can hold a MongoDB Connector for BI authentication session open indefinitely by beginning a SASL-based login exchange and then declining to complete it. Because the negotiation loop had no overall time bound and the read from the client had no deadline, each such session retains a worker, a client connection slot, and its associated backend database connections until the process is restarted. Repeated use of this behavior can consume the configured connection capacity and prevent legitimate users from establishing new sessions.

   MAMongoDB Atlas· Aug 28, 2026

7. 8.7High

   CVE-2026-81518 ↗ (opens in a new tab)

   When mongosqld is configured with a client certificate authority file, the listener requests a client certificate during the TLS handshake but does not require one, so a client that presents no certificate is still accepted. In deployments that rely on client certificates as the sole means of identifying users, a remote party with network access to the listener can therefore establish a session and read the MongoDB data exposed through the connector.

   MAMongoDB Atlas· Aug 28, 2026

8. 8.7High

   CVE-2026-81517 ↗ (opens in a new tab)

   An unauthenticated party able to reach the port of a MongoDB Connector for BI (mongosqld) instance may generate enough routine connection log activity to exhaust the storage backing the configured log path. When a log write or log rotation operation subsequently fails, the resulting error is not handled and the shared mongosqld process ends, ending service for all connected SQL clients. The process continues to end on startup until an operator restores available storage, and the diagnostic message explaining the condition is not recorded.

   MAMongoDB Atlas· Aug 28, 2026

9. 8.3High

   CVE-2026-81490 ↗ (opens in a new tab)

   A database user able to create a view in a namespace that MongoDB Connector for BI samples can cause the schema-sampling routine to stop functioning by defining a view whose evaluation reliably fails. The sampling logic classifies the resulting server message as transient and, after the configured retries are exhausted, proceeds without a valid result, ending the schema refresh routine. The mongosqld process continues running without a usable schema, so SQL clients are unable to obtain results until an operator removes the view or excludes its namespace from sampling.

   MAMongoDB Atlas· Aug 28, 2026

10. 9.8Crit

    CVE-2026-82329 ↗ (opens in a new tab)Known exploited

    JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges.

    JFJFrog· Aug 28, 2026

11. 8.5High

    CVE-2026-77586 ↗ (opens in a new tab)

    In MongoDB Connector for BI, MongoDB object names such as collection, field, and index names are placed into the quoted identifiers of the DDL text returned by SHOW CREATE statements without escaping the identifier delimiter. A user with permission to write to a sampled MongoDB collection can choose a name that closes the quoted identifier early, so that additional SQL text becomes part of the generated output. If an operator or automated tool later replays that generated statement against a SQL server, the additional text is executed with the privileges of that session.

    MAMongoDB Atlas· Aug 28, 2026

12. 5.7Med

    CVE-2026-77184 ↗ (opens in a new tab)

    In MongoDB Connector for BI, the description text of a collection's JSON schema validator is incorporated into the comment text of the DDL returned by SHOW CREATE statements without complete escaping of backslash characters. A user with permission to modify a collection's schema validator, in deployments configured to build their SQL schema from those validators, can cause additional SQL text to be embedded in that generated output. If an operator or automated tool later replays that generated statement against a SQL server, the additional text is executed with the privileges of that session.

    MAMongoDB Atlas· Aug 28, 2026

13. 6.9Med

    CVE-2026-76798 ↗ (opens in a new tab)

    The MongoSQL Transition Readiness Tool writes query text and user names read from BI Connector log files into its generated HTML report without encoding them for that output context. A user able to issue queries through the BI Connector can influence log content so that markup supplied in a query is interpreted by the browser when an operator later generates and opens the report, which may disclose other users' logged query text and user names to an external party or present misleading content to the operator. Generating a report over logs containing the affected entries and opening that repor

    MAMongoDB Atlas· Aug 28, 2026

14. 5.8Med

    CVE-2026-76797 ↗ (opens in a new tab)

    The MongoSQL Transition Readiness Tool writes database and collection names into its generated CSV reports without neutralizing leading characters that spreadsheet applications treat as formulas. A user with write privileges on the cluster can choose a namespace name that is later evaluated as a formula when an operator opens the generated report in a spreadsheet application, which may result in unintended disclosure of report contents or execution of external content on the operator's workstation. Generating a report for the affected namespace and opening it in a spreadsheet application is re

    MAMongoDB Atlas· Aug 28, 2026

15. 4.8Med

    CVE-2026-76794 ↗ (opens in a new tab)

    MongoSQL Transition Readiness Tool does not sufficiently encode database metadata before including it in generated HTML. A MongoDB user with write access can introduce crafted metadata that may cause script code to run when another user generates and opens the report, potentially exposing report contents or altering its display.

    MAMongoDB Atlas· Aug 28, 2026

16. 6.8Med

    CVE-2026-81530 ↗ (opens in a new tab)

    A weakness in the client-side encryption configuration surface of the MongoDB C# Driver causes sensitive key-management credential material supplied by the application to be reproduced verbatim in the driver's human-readable diagnostic representation of its client settings, instead of being masked as other secret fields are. A party able to read the application's logs, diagnostic output, or a process memory dump may thereby recover the plaintext credentials and use them to decrypt protected field data.

    MAMongoDB Atlas· Aug 27, 2026

17. 7.1High

    CVE-2026-81529 ↗ (opens in a new tab)

    Improper neutralization of delimiters in connection-URL construction allows connection-option injection in the MongoDB C# Driver. When an application passes untrusted text into the driver's connection-URL builder and round-trips the builder back into a client configuration, the untrusted text is serialized without neutralizing the URL/option delimiters and is then re-parsed as authoritative connection options. A low-privileged user of such an application can thereby introduce or suppress security-relevant connection settings.

    MAMongoDB Atlas· Aug 27, 2026

18. 5.3Med

    CVE-2026-81528 ↗ (opens in a new tab)

    A MongoDB C# driver document-replacement code path omits the element-name/shape validation that the equivalent write paths apply, so a value supplied as a replacement is forwarded to the server without neutralization of query-language special elements. An application that passes untrusted, loosely-typed input as a replacement value therefore allows that input to be interpreted by the database as update logic rather than as data, executing under the application's own database credentials. Applications using strongly-typed document mappings are not affected.

    MAMongoDB Atlas· Aug 27, 2026

19. 6.9Med

    CVE-2026-81527 ↗ (opens in a new tab)

    A NoSQL/expression injection weakness exists in the LINQ-to-aggregation query translation layer of the MongoDB C# Driver, in both aggregation expression and query filter translation. When application-supplied values are embedded in certain query constructs, special elements contained within those values are not properly escaped before the resulting query is transmitted to the database, so portions of the value may be interpreted by the database as query logic rather than as data. A user able to supply values that an application incorporates into an affected query may thereby cause unintended d

    MAMongoDB Atlas· Aug 27, 2026

20. 7.1High

    CVE-2026-81526 ↗ (opens in a new tab)

    The MongoDB Rust Driver does not neutralize special characters in a caller-supplied target identifier before embedding it in the request it sends to the server. An actor able to influence that identifier in an application using the driver may cause write operations to be applied to an unintended target within the same deployment using the application's own credentials. This may result in unauthorized modification of data belonging to another logical boundary enforced by the application.

    MAMongoDB Atlas· Aug 27, 2026

21. 8.6High

    CVE-2026-81525 ↗ (opens in a new tab)

    The MongoDB client library for PHP does not sufficiently sanitize special elements in application-supplied namespace identifiers before using them to construct the target namespace for database operations. An application that incorporates untrusted text into these identifiers may have operations silently directed at a different storage location than the one the application intended.

    MAMongoDB Atlas· Aug 27, 2026

22. 5.3Med

    CVE-2026-81524 ↗ (opens in a new tab)

    A weakness in the MongoDB C Driver allows special elements in caller-supplied database and collection name components to pass without sanitization when the driver composes the target namespace for an operation. An application that incorporates untrusted input into these name components can have operations directed at a resource other than the one intended.

    MAMongoDB Atlas· Aug 27, 2026

23. 2.0Low

    CVE-2026-81523 ↗ (opens in a new tab)

    A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.

    MAMongoDB Atlas· Aug 27, 2026

24. 8.6High

    CVE-2026-81522 ↗ (opens in a new tab)

    A weakness in the MongoDB C++ Driver's handling of caller-supplied namespace identifiers allows special characters embedded in those identifiers. An application that builds a namespace identifier from untrusted input without validating it may therefore have its operation directed at a different target than intended. This can result in limited unauthorized read and write access to data belonging to another logical tenant of the affected application.

    MAMongoDB Atlas· Aug 27, 2026

25. 7.1High

    CVE-2026-81521 ↗ (opens in a new tab)

    The MongoDB Go Driver's client-level bulk write operation may accept a caller-supplied database name containing a reserved separator character without escaping it before the name is used to build the target namespace for the operation. An application that passes untrusted input as a database name could therefore have the write directed at a database and collection other than the ones it intended. Only the Client.BulkWrite API is affected.

    MAMongoDB Atlas· Aug 27, 2026

26. 7.7High

    CVE-2026-75889 ↗ (opens in a new tab)

    Grafana Alloy’s prometheus.operator.servicemonitors component allows a user who can create or modify ServiceMonitor resources in a watched namespace to specify an arbitrary local file through bearerTokenFile. Alloy reads the file and sends its contents as a bearer token to an attacker-controlled scrape endpoint. This may disclose files accessible to the Alloy process, including its projected Kubernetes service account token, potentially granting the attacker Alloy’s Kubernetes permissions. Exploitation requires ServiceMonitor write access and lower privileges than Alloy’s service account.

    GCGrafana Cloud· Aug 27, 2026

27. 9.6Crit

    CVE-2026-75871 ↗ (opens in a new tab)

    GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect outbound model requests to an externally-controlled endpoint via a crafted inline flow configuration that overrides the HTTP Host header, resulting in disclosure of Google Cloud Vertex cloud service credentials and private signing keys.

    GIGitLab· Aug 27, 2026

28. 4.1Med

    CVE-2026-75573 ↗ (opens in a new tab)

    In MongoDB Connector for BI, mongodrdl may write a TLS private-key password to standard error when the password is supplied through both the connection URI and the corresponding command-line option. A local user with access to the captured command output and encrypted key file may use the disclosed password to access the associated TLS client key.

    MAMongoDB Atlas· Aug 27, 2026

29. 8.2High

    CVE-2026-75159 ↗ (opens in a new tab)

    An unauthenticated client that can reach a MongoDB Connector for BI deployment configured with Kerberos authentication may cause mongosqld to terminate when a crafted authentication exchange encounters a specific GSSAPI error-handling condition. This can interrupt BI Connector availability until the process restarts.

    MAMongoDB Atlas· Aug 27, 2026

30. 6.1Med

    CVE-2026-19854 ↗ (opens in a new tab)

    When the ClickHouse plugin uses Native protocol (the default) with PDC or secure SOCKS, it asks for TLS but the connection library ignores that and talks to ClickHouse in the clear. Username, password, queries, and results can be read on the hop after the proxy. The server certificate is never checked, and a configured client certificate is not sent.

    GCGrafana Cloud· Aug 27, 2026

31. 3.5Low

    CVE-2026-7487 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.

    GIGitLab· Aug 26, 2026

32. 6.5Med

    CVE-2026-77801 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, could have allowed an authenticated user to cause a denial of service affecting background job processing, due to missing object count limits.

    GIGitLab· Aug 26, 2026

33. 5.5Med

    CVE-2026-3035 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks.

    GIGitLab· Aug 26, 2026

34. 8.1High

    CVE-2026-18252 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source.

    GIGitLab· Aug 26, 2026

35. 4.3Med

    CVE-2026-15387 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have influenced the execution environment of Pipeline Execution Policy enforcement jobs, due to improper handling of job dependencies.

    GIGitLab· Aug 26, 2026

36. 6.5Med

    CVE-2025-10903 ↗ (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have caused denial of service, due to an unbounded loop triggered by specially crafted input in the SCIM user provisioning feature.

    GIGitLab· Aug 26, 2026

37. 8.8High

    CVE-2026-19042 ↗ (opens in a new tab)

    A command injection vulnerability in TeamViewer Full Client and Host for Linux prior to version 15.81.5 allows a remote attacker to execute arbitrary commands in the context of the current user via a specially crafted URL sent through the out-of-session chat feature. Exploitation requires user interaction by clicking the malicious link.

    TETeamViewer· Aug 26, 2026

38. 7.5High

    CVE-2026-16444 ↗ (opens in a new tab)

    Improper neutralization of path traversal sequences in TeamViewer Desktop Clients prior Version 15.81.5 allows an authenticated remote session participant to write files to unintended locations on the local file system via file transfer or virtual file clipboard mechanisms. An attacker can leverage this behavior to achieve arbitrary file write and potentially execute code with the privileges of the affected user.

    TETeamViewer· Aug 26, 2026

39. 6.3Med

    CVE-2026-19197 ↗ (opens in a new tab)

    A user with organization administrator permissions can delete dashboard snapshots belonging to other organizations on the same Grafana instance, and can recover a snapshot's secret delete key using only its public share key (broken access control).

    GCGrafana Cloud· Aug 26, 2026

40. 8.1High

    CVE-2026-65105 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its inference server setup, where a remote attacker may access the inference service without authentication. A successful exploit of this vulnerability may lead to information disclosure and denial of service.

    NVNVIDIA· Aug 25, 2026

41. 7.8High

    CVE-2026-65099 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its command-line interface, where an attacker could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, information disclosure, and denial of service.

    NVNVIDIA· Aug 25, 2026

42. 9.8Crit

    CVE-2026-65098 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its remote-access helper workflow, where an attacker could cause weak authentication. A successful exploit of this vulnerability might lead to code execution, information disclosure, and data tampering.

    NVNVIDIA· Aug 25, 2026

43. 8.8High

    CVE-2026-65097 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its installation scripts, where an attacker could cause a download of code without integrity check. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

    NVNVIDIA· Aug 25, 2026

44. 7.8High

    CVE-2026-65096 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in the Telegram bridge component, where an attacker could cause an OS command injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

    NVNVIDIA· Aug 25, 2026

45. 9.9Crit

    CVE-2026-65093 ↗ (opens in a new tab)

    NVIDIA OpenShell for Linux contains a vulnerability where an attacker could cause a sandbox escape. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, and information disclosure.

    NVNVIDIA· Aug 25, 2026

46. 8.5High

    CVE-2026-65092 ↗ (opens in a new tab)

    NVIDIA OpenShell Sandbox for Linux contains a vulnerability where an attacker could cause a path traversal bypass of L7 REST network policy. A successful exploit of this vulnerability might lead to information disclosure and data tampering.

    NVNVIDIA· Aug 25, 2026

47. 8.8High

    CVE-2026-65091 ↗ (opens in a new tab)

    NVIDIA OpenShell for all platforms contains a vulnerability where a malicious gateway could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Aug 25, 2026

48. 7.8High

    CVE-2026-65090 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its NIM management component, where an attacker could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, information disclosure, and denial of service.

    NVNVIDIA· Aug 25, 2026

49. 7.8High

    CVE-2026-65089 ↗ (opens in a new tab)

    NVIDIA NemoClaw for Linux contains a vulnerability in its status and logs plugin commands, where an attacker could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, information disclosure, and denial of service.

    NVNVIDIA· Aug 25, 2026

50. 5.5Med

    CVE-2026-65088 ↗ (opens in a new tab)

    NVIDIA NemoClaw contains a vulnerability where an attacker could cause invocation of process using visible sensitive information. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Aug 25, 2026