CVEs.

Matching CVEs

1. 7.5High

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

   NVIDIA AIStore for Linux contains a vulnerability in the Promote API where an unauthenticated remote attacker may read files accessible to the target process by supplying a crafted absolute source path. A successful exploit may lead to information disclosure.

   NVNVIDIA· Oct 13, 2026

2. 7.3High

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

   NVIDIA DALI contains a vulnerability where an attacker could cause an uncontrolled out-of-bounds read. A successful exploit of this vulnerability mighty lead to information disclosure, data tampering, and denial of service.

   NVNVIDIA· Oct 13, 2026

3. 7.3High

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

   NVIDIA DALI contains a vulnerability where an attacker could cause an uncontrolled out-of-bounds write. A successful exploit of this vulnerability might lead to denial of service, information disclosure, and data tampering.

   NVNVIDIA· Oct 13, 2026

4. 7.3High

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

   NVIDIA DALI contains a vulnerability where an attacker could cause a stack-based buffer overflow. A successful exploit of this vulnerability might lead to code execution, information disclosure, data tampering, and denial of service.

   NVNVIDIA· Oct 13, 2026

5. 7.3High

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

   NVIDIA DALI contains a vulnerability where an attacker could cause an uncontrolled out-of-bounds read. A successful exploit of this vulnerability might lead to information disclosure and denial of service.

   NVNVIDIA· Oct 13, 2026

6. 7.8High

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

   NVIDIA Isaac Lab contains a vulnerability where an attacker could cause an eval injection. A successful exploit of this vulnerability might lead to code execution, information disclosure, data tampering, and denial of service.

   NVNVIDIA· Oct 13, 2026

7. 7.8High

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

   NVIDIA Megatron-LM contains a vulnerability in checkpoint loading where, an attacker could cause an RCE by convincing a user to load a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

   NVNVIDIA· Oct 13, 2026

8. 7.1High

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

   NVIDIA Megatron-LM for all platforms contains a vulnerability in inference, where an attacker could cause hash collisions in the cache used for inference requests. A successful exploit of this vulnerability might lead to data tampering and partial information disclosure.

   NVNVIDIA· Oct 13, 2026

9. 8.1High

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

   NVIDIA AIStore for Linux contains a path traversal vulnerability in the target-side object rename handler, where an unauthenticated remote attacker could cause an improper limitation of a pathname to a restricted directory by submitting a crafted rename destination directly to an AIStore target, resulting in the arbitrary creation or overwrite of a file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, data tampering, and denial of service.

   NVNVIDIA· Oct 13, 2026

10. 8.6High

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

    NVIDIA AIStore for Linux contains a vulnerability in the distributed sort component where an attacker could cause server-side request forgery by supplying a crafted external key map URL. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Oct 13, 2026

11. 7.3High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to inject specially crafted content into AI agent instructions, potentially causing unintended command execution attributed to other users, due to improper neutralization of special elements in AI conversation context construction.

    GIGitLab· Oct 13, 2026

12. 8.7High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to execute arbitrary JavaScript in the context of other users' browser sessions via a specially crafted repository, due to improper sanitization of HTML attributes in syntax-highlighted output.

    GIGitLab· Oct 13, 2026

13. 7.7High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to execute arbitrary CI/CD pipelines in a transferred project with the new group's privileges due to improper cleanup of scheduled pipeline execution policy records.

    GIGitLab· Oct 13, 2026

14. 8.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with Developer role to execute CI/CD pipelines on protected branches without authorization due to improper authorization checks in the downstream pipeline creation service.

    GIGitLab· Oct 13, 2026

15. 8.2High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed a user to poison cached responses for raw repository files, causing targeted users' CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references.

    GIGitLab· Oct 13, 2026

16. 7.0High

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

    A connected peer cluster can modify a Temporal Server cluster's local namespaces, which are never replicated to that peer, because the receiving cluster applies inbound namespace replication updates to them. In a multi-cluster deployment, each cluster pulls replication tasks from the remote clusters an administrator has registered with connection enabled; the sending side excludes local namespaces, but the receiving side does not apply the same rule. When an inbound task names an existing namespace, the server checks at most that the namespace identifiers match, then overwrites its state, desc

    TCTemporal Cloud· Oct 12, 2026

17. 7.3High

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

    Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package supplied to Docker Desktop Installer.exe install -package. An attacker able to provide a crafted package and convince a user to approve the Docker-signed UAC prompt could execute attacker-controlled installer actions as LocalSystem.

    DODocker· Oct 9, 2026

18. 8.1High

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

    Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.

    MAMicrosoft Azure· Oct 8, 2026

19. 8.2High

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

    Improper validation of a BSON array length in the MongoDB Go Driver can cause an out-of-bounds index and runtime panic when an application calls bson.RawArray.Validate or bsoncore.Array.Validate on a malformed four-byte array. An unauthenticated actor who can supply raw BSON array data to an affected application may terminate an unprotected application process, causing a denial of service. No confidentiality or integrity impact has been identified.

    MAMongoDB Atlas· Oct 8, 2026

20. 8.2High

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

    An integer overflow in BSON value-length handling in the MongoDB Go Driver can cause a runtime panic when an application validates or accesses a malformed BSON document. An unauthenticated actor who can supply BSON bytes to an affected application may terminate an unprotected application process, causing a denial of service. The driver's server-monitoring path contains panic recovery and is limited to server-selection failure.

    MAMongoDB Atlas· Oct 8, 2026

21. 8.7High

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

    Improper state management in MongoDB libmongocrypt can cause provider-specific data to be treated as an incompatible type when cleaning up a key document containing duplicate masterKey fields. An authenticated actor who can modify key vault documents, or a server that returns such a key document, can cause invalid memory access and invalid frees in the client process. This can terminate the application or corrupt process memory.

    MAMongoDB Atlas· Oct 8, 2026

22. 7.1High

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

    An integer underflow in the KMS endpoint-parsing logic of MongoDB libmongocrypt can cause an allocation failure that terminates the application process. This can occur when an authenticated user modifies a key document in the key vault collection, or when an application accepts a KMS endpoint containing a colon after its path or query during key creation. The issue does not access memory outside its allocated bounds.

    MAMongoDB Atlas· Oct 8, 2026

23. 7.2High

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

    Vault and Vault Enterprise did not consistently evaluate ACL policies against the canonical form of resource and policy names. This may allow an authenticated user with delegated permissions to bypass an explicit deny restriction and access a protected resource or assign a denied policy, potentially leading to privilege escalation. This vulnerability (CVE-2026-89322) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.

    HAHashiCorp (HCP / Terraform Cloud)· Oct 7, 2026

24. 8.0High

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

    Vault and Vault Enterprise did not consistently verify that stored plugin catalog entries reference binaries within the configured plugin directory. When Vault uses Shamir seals and has an external plugin directory configured, a privileged operator able to restore an Integrated Storage (Raft) snapshot may be able to execute arbitrary code on the Vault host. This vulnerability (CVE-2026-105816) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.

    HAHashiCorp (HCP / Terraform Cloud)· Oct 7, 2026

25. 7.6High

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

    Docker Engine classifies a registry hostname as insecure using an any-match DNS check. loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP fallback for the registry connection.

    DODocker· Oct 7, 2026

26. 7.8High

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

    NVIDIA Model-Optimizer contains a vulnerability where an attacker may cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure.

    NVNVIDIA· Oct 6, 2026

27. 7.1High

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

    Authorization Bypass Through User-Controlled Key (CWE-639) in Elasticsearch can lead to Information Disclosure via a specially crafted cross-cluster search request that references an unauthorized shard identifier. Elasticsearch contains an authorization bypass weakness in its handling of cross-cluster search requests made through the Remote Cluster Security (RCS) 2.0 model. An authorization check validates a request against one identifying attribute of the target shard, while a separate, independently-supplied identifying attribute in the same request determines which shard is actually accesse

    ECElastic Cloud· Oct 6, 2026

28. 7.2High

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

    Incorrect Authorization (CWE-863) in Elasticsearch can lead to Privilege Escalation via a delegated administrative privilege whose scope is not fully enforced during authorization checks. Elasticsearch contains an incorrect authorization weakness in a configurable, non-default privilege that lets an administrator delegate limited role-management capability to another user, scoped to specific indices. The authorization check that enforces this scoping does not correctly account for a role-definition setting that can expand the matched index set. A user holding this delegated privilege with a br

    ECElastic Cloud· Oct 6, 2026

29. 8.8High

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

    Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana could lead to cross-tenant data interception. In this context, "tenant" refers to a user or team sharing the same Kibana deployment, not a separate Elastic Cloud organization or customer. Kibana's Fleet package installation process allowed a user holding delegated Fleet package-management privileges, without direct Elasticsearch administrative privileges, to claim a data stream identifier already in use by another tenant. Because ownership of that identifier was not verified before Fleet applied the uploaded package's generat

    ECElastic Cloud· Oct 6, 2026

30. 8.7High

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

    A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed a repository contributor to cause the appliance to issue requests to attacker-controlled internal hosts, which could be chained to achieve remote code execution on the appliance. The secret scanning validator for GCP service account credentials trusted the token endpoint embedded in a committed credential and issued a request to it without restricting the destination. Exploitation required an authenticated user with permission to push to a repository on an instance with GitHub Advanced Se

    GIGitHub· Oct 6, 2026

31. 7.5High

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

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bi

    DODocker· Oct 5, 2026

32. 7.1High

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

    If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.

    DODocker· Oct 5, 2026

33. 8.8High

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

    Weak authentication in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.

    M3Microsoft 365· Oct 2, 2026

34. 8.3High

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

    Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL that matches images.remotePatterns, allowing the optimized image fetch to reach private IP addresses after the URL passes the allow-list check. Applications without images.remotePatterns are not affected. Administrators unable to upgrade should audit allow-listed hosts and avoid entries whose DNS records are not trusted. This issue is fixed in version 16.3.8.

    VEVercel· Oct 2, 2026

35. 7.1High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode driver where a local user can cause the driver to dereference an untrusted pointer. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

    NVNVIDIA· Sep 30, 2026

36. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the open-source kernel module DMA-BUF import path where an unprivileged local user could cause improper preservation of memory access permissions when importing a read-only buffer from another device's DMA-BUF exporter. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

37. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer where an error-handling path could operate on an improperly initialized resource. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

38. 7.8High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability in the open-source kernel module where an unprivileged local user could cause improper preservation of memory access permissions during DMA mapping. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

39. 7.0High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability in the open-source kernel module event delivery path where an unprivileged local user could cause a use-after-free through a race between asynchronous event delivery and file close. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

40. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the open-source kernel module Resource Server where an unprivileged local user could cause a use-after-free through a missing self-reference guard in the map cleanup path. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

41. 7.0High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an unprivileged user can write to read-only memory because the memory's permissions are not preserved. A successful exploit of this vulnerability might lead to code execution and escalation of privileges.

    NVNVIDIA· Sep 30, 2026

42. 7.8High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an unprivileged user can write to read-only memory because the memory's permissions are not preserved. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

43. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where an unprivileged user may cause a use-after-free condition by issuing a sequence of driver commands. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, data tampering, and information disclosure.

    NVNVIDIA· Sep 30, 2026

44. 7.8High

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer where an unprivileged user can cause an out-of-bounds write. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, and denial of service.

    NVNVIDIA· Sep 30, 2026

45. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer where an unprivileged user could cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

46. 7.8High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an unprivileged user could bypass read-only memory protection due to incorrect authorization, enabling write access to memory marked read-only. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026

47. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where an unprivileged user may cause a use-after-free condition by issuing a sequence of driver commands. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, and information disclosure.

    NVNVIDIA· Sep 30, 2026

48. 7.8High

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where an unprivileged user may cause a use-after-free condition by issuing a sequence of driver commands. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, and information disclosure.

    NVNVIDIA· Sep 30, 2026

49. 7.8High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability where an unprivileged user could cause a use-after-free condition by issuing a sequence of driver commands. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service and information disclosure.

    NVNVIDIA· Sep 30, 2026

50. 7.8High

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

    NVIDIA GPU Display Driver for Linux contains a vulnerability where an unprivileged user could cause a use-after-free. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026