CVEs.

Matching CVEs

1. 6.5Med

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

   Insufficiently protected credentials in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

   M3Microsoft 365· Aug 11, 2026

2. 6.5Med

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

   Relative path traversal in Microsoft Office SharePoint allows an authorized attacker to disclose information over a network.

   M3Microsoft 365· Aug 11, 2026

3. 5.4Med

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

   Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

   M3Microsoft 365· Aug 11, 2026

4. 6.5Med

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

   Server-side request forgery (ssrf) in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

   M3Microsoft 365· Aug 11, 2026

5. 5.4Med

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

   Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

   M3Microsoft 365· Aug 11, 2026

6. 6.5Med

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

   Missing authorization in Dynamics Business Central allows an authorized attacker to disclose information over a network.

   M3Microsoft 365· Aug 11, 2026

7. 6.5Med

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

   Missing bounds check in the annotator function of Zoom Clients allows buffer over-read, which may allow a meeting participant to conduct a denial of service on another participant via network access.

   ZOZoom· Aug 11, 2026

8. 4.9Med

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

   Cross-Site Request Forgery weaknesses in the Administrative Console of PingFederate versions before version 13.1 may allow actors to perform unauthorized actions via specially-crafted links triggered by administrators with active sessions.

   PIPing Identity· Aug 10, 2026

9. 4.3Med

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

   Vault’s ACL policy engine did not consistently enforce a wildcard (glob) deny rule against LIST requests made with a trailing slash on the denied path. This may allow a token holding a broader allow rule alongside a narrower wildcard deny rule to enumerate the names of entries beneath a path it was intended to be denied access to. This vulnerability (CVE-2026-12624) is fixed in Vault Community Edition 2.0.3 and Vault Enterprise 2.0.3, 1.21.8, 1.20.13, and 1.19.19.

   HAHashiCorp (HCP / Terraform Cloud)· Aug 10, 2026

10. 5.3Med

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

    Consul Community Edition and Consul Enterprise 1.3.0 through 2.0.2 are vulnerable to an unauthenticated denial of service in several agent HTTP API endpoints. A remote caller could cause the agent to consume substantial memory before the request was rejected. This vulnerability, CVE-2026-19113, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

11. 6.8Med

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

    Consul Community Edition and Consul Enterprise 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to use the Vault Connect CA provider with JWT or AppRole authentication. A privileged attacker with `operator:write` permission may direct Consul to read and forward credential files outside the intended scope, potentially leading to the exfiltration of sensitive secrets from the Consul server host. This vulnerability, CVE-2026-19017, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

12. 4.2Med

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

    Consul Community Edition and Consul Enterprise 1.19.1 through 2.0.2 did not enforce the {{session:write}} ACL permission for session deletion operations submitted through the transaction API. An authenticated caller with network access to the Consul server RPC port could delete arbitrary sessions without holding the required permission. This vulnerability, CVE-2026-19016, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

13. 5.3Med

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

    Consul Community Edition and Consul Enterprise 1.2.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect CA roots endpoint that may allow a remote caller to grow the agent's Connect CA roots cache without bound, defeating the operator's cache-disable configuration. This vulnerability, CVE-2026-19015, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

14. 4.3Med

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

    Consul Community Edition and Consul Enterprise 1.17.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect authorization endpoint that may allow a caller to grow the agent's intention-match cache without bound, defeating the operator's cache-disable configuration. This vulnerability, CVE-2026-190124, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

15. 5.3Med

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

    Consul Community Edition and Consul Enterprise 1.18.0 through 2.0.2 are vulnerable to an authenticated denial of service in the Enterprise-to-Community Edition downgrade path that may allow an authorized caller to crash the Consul server. A caller with config-entry write permission can submit a service-router configuration entry that causes the agent to exit unexpectedly. This vulnerability, CVE-2026-19012, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

16. 4.2Med

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

    Consul Community Edition and Consul Enterprise 1.20.1 through 2.0.2 are vulnerable to an L7 intention authorization bypass when a service proxy is configured with a custom public listener. An authenticated mesh workload may reach HTTP paths that are blocked by a path-based deny intention. This vulnerability, CVE-2026-15970, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

17. 5.5Med

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

    A maliciously crafted TIF file, when parsed through certain Autodesk products during image import, can cause an Out-of-Bounds Read in the image handling library. A malicious actor can leverage this vulnerability to cause a denial of service

    AUAutodesk· Aug 6, 2026

18. 6.6Med

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

    A denial of service vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause excessive CPU consumption and exhaust the pool of request-handling worker processes by sending a crafted form-encoded HTTP POST request containing deeply nested parameters. Because request parameters were parsed before routing and authentication, any POST endpoint could be used to trigger the condition, which could render the instance unresponsive. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.3, 3.19.

    GIGitHub· Aug 5, 2026

19. 6.3Med

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

    Improper limitation of a pathname to a restricted directory in the get_resource tool in Amazon awslabs.aws-transform-mcp-server 0.1.0 through 0.1.4 might allow a context-dependent actor to write arbitrary files outside the intended working directory via the savePath parameter. To remediate this issue, users should upgrade to version 0.1.5 or later.

    AWAmazon Web Services· Aug 5, 2026

20. 5.3Med

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

    NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause the generation of error messages that contain sensitive information. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Aug 4, 2026

21. 6.5Med

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

    NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to denial of service and data tampering.

    NVNVIDIA· Aug 4, 2026

22. 6.5Med

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

    NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to data tampering and denial of service.

    NVNVIDIA· Aug 4, 2026

23. 6.9Med

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

    Key exchange without entity authentication in the EMR SSH helper commands in Amazon AWS CLI before 1.45.28 and AWS CLI v2 before 2.35.3 might allow man-in-the-middle attackers to intercept SSHsessions and file transfers via network positioning between the client and the EMR cluster endpoint. To remediate this issue, users should upgrade to AWS CLI v1 1.45.28 or later, or AWS CLI v2 2.35.3 or later.

    AWAmazon Web Services· Aug 3, 2026

24. 6.6Med

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

    An allocation of resources without limits vulnerability in the HTTP handler component of Google mcp-toolbox versions up to and including 1.4.0 allows an unauthenticated attacker to cause a denial of service (DoS). The /mcp endpoint handler reads incoming payloads directly into system memory using an unrestricted buffer loop (io.ReadAll) without applying defensive constraints such as http.MaxBytesReader or pre-read Content-Length enforcement. By submitting a single, massive HTTP request body, an attacker can linearly consume available host memory until the runtime process is terminated by an Ou

    GCGoogle Cloud· Jul 31, 2026

25. 5.7Med

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

    An improper authorization and security-boundary bypass vulnerability in the bigquery-execute-sql tool component of Google mcp-toolbox versions 0.16.1 through 1.4.0 allows an authenticated attacker to bypass allowedDatasets validation checks. The toolbox relies on the BigQuery dry-run API to enforce dataset restrictions, but due to a fail-open logic flaw, it bypasses validation when the API returns an empty array for specialized constructs. This allows the attacker to extract structural DDL schemas for explicitly excluded datasets via INFORMATION_SCHEMA, and access downstream federated row data

    GCGoogle Cloud· Jul 31, 2026

26. 5.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthorized user to view project import source information due to a missing authorization check.

    GIGitLab· Jul 29, 2026

27. 5.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.

    GIGitLab· Jul 29, 2026

28. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with guest-role permissions to access test report contents they were not authorized to view due to improper access control enforcement.

    GIGitLab· Jul 29, 2026

29. 4.7Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an attacker to execute arbitrary JavaScript in another user's browser via a crafted URL, due to improper sanitization of user-controlled input.

    GIGitLab· Jul 29, 2026

30. 5.4Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries.

    GIGitLab· Jul 29, 2026

31. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation.

    GIGitLab· Jul 29, 2026

32. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to access information from unauthorized projects due to improper neutralization of untrusted content processed by the AI-assisted code review functionality.

    GIGitLab· Jul 29, 2026

33. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthenticated user to view the title of a confidential issue through a publicly accessible merge request due to improper authorization checks.

    GIGitLab· Jul 29, 2026

34. 4.9Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Maintainer role to modify protected branch configuration due to improper authorization in a projects API endpoint.

    GIGitLab· Jul 29, 2026

35. 5.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to merge code into a protected branch without the required approvals due to a race condition in approval rule processing.

    GIGitLab· Jul 29, 2026

36. 5.5Med

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

    A maliciously crafted DWG or DXF file, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash or disclose sensitive information.

    AUAutodesk· Jul 29, 2026

37. 5.5Med

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

    Mattermost versions 11.8.x <= 11.8.0, 11.7.x <= 11.7.3, 11.6.x <= 11.6.5, 10.11.x <= 10.11.20 fail to verify file deletion path which allows an admin with SAML system-console write permissions to delete arbitrary files outside the config directory from the server via the remove file endpoint.. Mattermost Advisory ID: MMSA-2026-00666

    MCMattermost Cloud· Jul 28, 2026

38. 5.1Med

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

    React Router is a router for React. Versions 6.0.0 through 7.17.0 are vulnerable to Open Redirtect through use of backslashes in <Link> and useNavigate. This issue is a follow up to CVE-2025-68470 and has been fixed in version 7.18.0.

    SHShopify· Jul 27, 2026

39. 6.9Med

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

    React Router is a router for React. In versions 6.30.2 through 6.30.4 and 7.9.6 through 7.12.0, applications that allow open redirects are vulnerable to XSS. An attacker could craft a malicious link that redirects users to an unexpected external site or that exploits an XSS vector.This issue has been fixed in version 7.13.0.

    SHShopify· Jul 27, 2026

40. 6.1Med

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

    React Router is a router for React. In versions 7.11.0 through 7.17.0, the RSCErrorHandler is missing protocol validation, allowing for redirects from untrusted sources. This issue is a follow up to CVE-2026-53667, and only affects consuming applications if they are using the unstable RSC APIs. This issue has been fixed in version 7.18.0.

    SHShopify· Jul 27, 2026

41. 6.1Med

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

    React Router is a router for React. In versions 6.4.0 through 7.17.0, if application code was written in a way that allows attacker-supplied input to overwrite certain aspects of errors caught by the SSR process, then it was possible for an attacker to trigger unexpected constructor execution on the client, which would in turn trigger an outbound network request. This is only possible with very specific (and unlikely) application-layer code. Note that this does not impact an application if it is using Declarative Mode. It only impacts Framework Mode and Data Mode applications that perform manu

    SHShopify· Jul 27, 2026

42. 6.5Med

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

    Build readers can access another repository's environment properties. A caller with read access to an ordinary repository can select a readable repository parameter while retrieving environment properties for a protected build, exposing build environment secrets (confidentiality impact; no integrity or availability impact demonstrated).

    JFJFrog· Jul 27, 2026

43. 6.5Med

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

    A user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response.

    JFJFrog· Jul 27, 2026

44. 6.5Med

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

    JFrog Artifactory support for Terraform remote repositories was found to be susceptible to Server-Side Request Forgery (SSRF). An authenticated user - or, if anonymous access is enabled on the repository, an unauthenticated user - could cause Artifactory to issue outbound HTTP requests to arbitrary destinations and receive the response content.

    JFJFrog· Jul 27, 2026

45. 6.8Med

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

    A URL validation weakness in JFrog Artifactory Ansible repository handling could allow a user, under specific repository access conditions, to cause unintended server-side requests. The issue primarily affects confidentiality and integrity and has been addressed in fixed Artifactory versions.

    JFJFrog· Jul 27, 2026

46. 5.4Med

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

    An authorization weakness in JFrog Artifactory internal metadata handling could allow a user with limited repository access to write to restricted internal metadata areas under specific conditions. Successful abuse is limited to integrity and availability impact at a low level; confidentiality is not affected.

    JFJFrog· Jul 27, 2026

47. 6.5Med

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

    Improper URL validation when handling specific URLs, allows an attacker, under certain conditions, to make unauthorized requests from JFrog Artifactory, potentially exposing internal services and cached response data.

    JFJFrog· Jul 27, 2026

48. 6.0Med

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

    Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(n

    VEVercel· Jul 27, 2026

49. 6.3Med

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

    Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cach

    VEVercel· Jul 27, 2026

50. 6.3Med

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

    Next.js is a React framework for building full-stack web applications. In versions 13.0.0 through 15.5.20 and 16.0.0 through 16.2.10, requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the Edge runtime. This issue has been fixed in versions 15.5.21 and 16.2.11.

    VEVercel· Jul 27, 2026