CVEs.

Latest CVEs

1. 9.3Crit

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

   This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions. Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents. In some configurations, there may be some sensitive files that make thi

   COConfluence· Oct 5, 2026

2. 9.3Crit

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

   This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions. Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents. In some configurations, there may be some sensitive files that make thi

   JIJira· Oct 5, 2026

3. 9.3Crit

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

   This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions. Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents. In some configurations, there may be some sensitive files that make thi

   JSJira Service Management· Oct 5, 2026

4. 2.3Low

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

   In MongoDB Controllers for Kubernetes, insufficient validation of Ops Manager backup configuration may allow a user who can modify an OpsManager custom resource to cause unintended administrative changes in Ops Manager. This affects deployments using Enterprise Ops Manager backup reconciliation.

   MAMongoDB Atlas· Oct 5, 2026

5. 6.9Med

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

   Docker Buildx Bake does not request the expected fs.read approval for certain filesystem inputs. An untrusted Bake definition can expose a readable file through a pathless secret whose ID is interpreted as a client-side pathname, or consume a local OCI image layout outside the project after entitlement validation checks a different path representation. Users who run untrusted Bake definitions are affected.

   DODocker· Oct 5, 2026

6. 6.0Med

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

   A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.

   DODocker· Oct 5, 2026

7. 6.8Med

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

   The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make buildkitd allocate memory proportional to that file, potentially exhausting memory and terminating the daemon, which interrupts other builds on the same instance. Fixed by rejecting such files above 16 MiB.

   DODocker· Oct 5, 2026

8. 6.9Med

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

   A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

   DODocker· Oct 5, 2026

9. 6.0Med

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

   BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow unintended host device access.

   DODocker· Oct 5, 2026

10. 5.7Med

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

    A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

    DODocker· Oct 5, 2026

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

12. 5.9Med

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

    An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.

    DODocker· Oct 5, 2026

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

14. 6.5Med

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

    A caller who can invoke the convert_playwright_script prompt in mcp-k6 can pass a bare file path as the playwright_script argument and receive the contents of any file readable by the user running the server, including SSH keys and cloud credentials in that user's home directory (path traversal). The working-directory restriction applied to '@'-prefixed paths can also be bypassed with a symbolic link inside the working directory that points outside it.

    GCGrafana Cloud· Oct 5, 2026

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

16. 6.3Med

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

    Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.3.8, pending use cache fills for the same key are shared without separating Draft Mode requests from regular requests. An overlapping regular request can receive unauthenticated unpublished content from an editor's Draft Mode fill, while an overlapping Draft Mode request can receive published content from a regular fill. When the regular request prerenders a page, the draft-dependent content can persist in the generated page and be served to later visitors until revalidation. Sites are affected when Cac

    VEVercel· Oct 2, 2026

17. 6.3Med

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

    Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, self-hosted applications using the Pages Router with statically generated or Incremental Static Regeneration pages can key a response cache entry without sufficiently binding it to the source route. A request can replace one page's cache entry with content from a different route, causing the affected page to serve incorrect content to every visitor until revalidation. Applications deployed on Vercel are not affected. This issue is fixed in versions 15.5.27 and 16.3.8.

    VEVercel· Oct 2, 2026

18. 2.3Low

    CVE-2026-94486 ↗ (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, the next dev development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

    VEVercel· Oct 2, 2026

19. 6.3Med

    CVE-2026-94485 ↗ (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, the `next dev` development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

    VEVercel· Oct 2, 2026

20. 6.3Med

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

    Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes can use a shared response cache key that is insufficiently scoped to the source route. A single unauthenticated crafted request can poison that cache, causing cross-user content substitution or persistent denial of service until the poisoned entry is revalidated or replaced. This issue is fixed in versions 15.5.27 and 16.3.8.

    VEVercel· Oct 2, 2026

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

22. 9.3Crit

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

    A missing authentication vulnerability in the Kernel Memory Access Driver (PSKMAD) used by WatchGuard endpoint security products allows a local, authenticated attacker to bypass the driver's access-control handshake and issue arbitrary privileged commands to the driver, resulting in disclosure of kernel and process memory.

    WAWatchGuard· Oct 1, 2026

23. 6.3Med

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

    Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different v

    VEVercel· Oct 1, 2026

24. 5.3Med

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

    Improperly stored passwords in the config file in Itron MV-90 xi 3.0 allows attackers to decode the passwords and password histories to gain access to the MV-90 application as any user.

    PAPalo Alto Networks· Sep 30, 2026

25. 5.5Med

    CVE-2026-47604 ↗ (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 may access another process's GPU channel state due to missing authorization checks. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Sep 30, 2026

26. 5.5Med

    CVE-2026-47603 ↗ (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 may access another process's GPU channel state due to missing authorization checks. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Sep 30, 2026

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

43. 6.4Med

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

    NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel module where an attacker could cause a use-after-free. 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

44. 7.8High

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where an attacker could cause an integer underflow. 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

45. 5.5Med

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where an attacker with local access could cause a NULL pointer dereference. A successful exploit of this vulnerability might lead to denial of service.

    NVNVIDIA· Sep 30, 2026

46. 7.8High

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where an attacker could cause type confusion. 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.0High

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where an attacker could cause an out-of-bounds write. 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

48. 5.5Med

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where a user could cause improper locking. A successful exploit of this vulnerability might lead to denial of service.

    NVNVIDIA· Sep 30, 2026

49. 7.3High

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

    NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel module where an attacker could cause a missing authorization issue. A successful exploit of this vulnerability might lead to information disclosure and data tampering.

    NVNVIDIA· Sep 30, 2026

50. 7.8High

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

    The NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode driver through which a user might trigger a use-after-free condition. Successful exploitation of this issue could lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

    NVNVIDIA· Sep 30, 2026