CVEs.

Matching CVEs

1. 7.4High

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

   A flaw was found in Rancher Manager. The SAML assertion replay protection introduced by the fix for CVE-2026-44946 recorded consumed assertion IDs in a per-process cache, so each replica only detected replays that reached the same pod. In a high-availability deployment, an attacker holding a captured assertion could replay it once against every other replica to obtain additional authenticated sessions as the victim. This issue affects Rancher: before 2.15.1.

   SUSUSE· Sep 3, 2026

2. 7.1High

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

   Improper handling of an unexpected value size in the decryption path of a client-side encryption library can cause a failed internal check that terminates the process using the library. A party able to place a suitably formed encrypted value where an application will decrypt it, or able to control the responses the application receives, may cause that application to stop running.

   MAMongoDB Atlas· Sep 3, 2026

3. 8.1High

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

   Only self-managed Grafana instances with Auth Proxy authentication and identity caching enabled (sync_ttl greater than zero) are affected. The Auth Proxy cache key concatenated the username and forwarded identity attributes without a delimiter, so distinct identities could collide on one key. An authenticated user who shapes their own attributes to collide with a higher-privileged user's, while that user's cache entry is live, is authenticated as that user, up to Administrator (authentication bypass by spoofing).

   GCGrafana Cloud· Sep 2, 2026

4. 7.8High

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

   Incorrect Permission Assignment for Critical Resource (CWE-732) in Elastic Agent can lead to local privilege escalation via Replace Binaries (CAPEC-642). On Windows systems where Elastic Agent is installed in unprivileged mode, resources used by the agent service are created with access controls broader than required. A local user could take advantage of this to cause the service to execute code of their choosing, ultimately obtaining SYSTEM-level privileges on the host.

   ECElastic Cloud· Sep 2, 2026

5. 7.3High

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

   Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) in the Kibana Fleet feature can lead to the unauthorized deletion of privileged resources via Path Traversal (CAPEC-126). A low-privileged user holding Fleet Settings write access could cause a subsequent administrative action to act on unintended internal resources, resulting in the deletion of privileged resources such as user accounts and other organizational assets. Exploitation requires an administrator to interact with the affected Fleet interface.

   ECElastic Cloud· Sep 2, 2026

6. 7.7High

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

   A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed remote code execution on the instance. Insufficient network isolation allowed malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests to a privileged service, leading to elevated code execution. Exploitation required pre-receive hook networking to be enabled and either site administrator privileges or write access to a repository containing a configured pre-receive hook. This vulnerability affected all versions of GitHub Enterprise Server

   GIGitHub· Sep 1, 2026

7. 7.7High

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

   A time-of-check time-of-use race condition vulnerability was identified in GitHub Enterprise Server that allowed remote code execution. Exploitation required an authenticated user with write access to a repository and precise timing of concurrent upload requests. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.20, 3.18.14, 3.19.11, 3.20.7, and 3.21.5. This vulnerability was reported via the GitHub Bug Bounty program.

   GIGitHub· Sep 1, 2026

8. 8.2High

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

   A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause the Manage API to send crafted outbound requests to an attacker-controlled host. An unauthenticated endpoint parsed an attacker-supplied cluster configuration and issued gateway-to-agent requests whose HMAC authenticated only a timestamp, not the request path or body. An attacker positioned to intercept the outbound request could capture this token and replay it against privileged management agent endpoints. High-availability deployments were not affec

   GIGitHub· Sep 1, 2026

9. 7.1High

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

   Missing Authorization (CWE-862) in the Elasticsearch custom inference service can lead to information disclosure via Privilege Abuse (CAPEC-122). A user holding only inference execution privileges could cause outbound inference traffic to be directed to a destination of their choosing and could cause administrator-provisioned credentials to be exposed.

   ECElastic Cloud· Sep 1, 2026

10. 7.3High

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

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) in Kibana can lead to the unauthorized deletion of privileged resources via Path Traversal (CAPEC-126). A low-privileged user holding tag creation privileges could cause a subsequent administrative action in the tag management interface to act on an unintended target, resulting in the deletion of privileged resources including administrative accounts and other organizational assets. Exploitation requires an administrator to interact with the affected interface.

    ECElastic Cloud· Sep 1, 2026

11. 8.8High

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

    Deserialization of Untrusted Data (CWE-502) in the Elasticsearch machine learning component can lead to remote code execution via Object Injection (CAPEC-586). A specially crafted trained model artifact could cause attacker-controlled logic to execute with a materially broader system-call surface than intended. Exploitation requires an authenticated user with sufficient privileges to create and deploy trained models.

    ECElastic Cloud· Sep 1, 2026

12. 8.3High

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

    Incorrect Authorization (CWE-863) in Kibana can lead to privilege escalation via Exploiting Incorrectly Configured Access Control Security Levels (CAPEC-180). A user holding workflow edit permissions could cause scheduled workflow executions to run with the privileges of a different, higher-privileged user, allowing access to and modification of data beyond their own authorization scope.

    ECElastic Cloud· Sep 1, 2026

13. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

14. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

15. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

16. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

17. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

18. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

19. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

20. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

21. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

22. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

23. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

24. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

25. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

26. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

27. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

28. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

29. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

30. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

31. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

32. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

33. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

34. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

35. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

36. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

37. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

38. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

39. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

40. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

41. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

42. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVNVIDIA· Sep 1, 2026

43. 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

44. 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

45. 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

46. 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

47. 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

48. 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

49. 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

50. 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