CVEs.

Latest CVEs

1. 6.5Med

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

   NVIDIA Flare SDK contains a vulnerability where an Attacker may cause an Improper Input Validation by path traversing. A successful exploit of this vulnerability may lead to information disclosure.

   NVNVIDIA· Apr 28, 2026

2. 8.8High

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

   NVIDIA FLARE SDK contains a vulnerability in FOBS, where an attacker may cause deserialization of untrusted data by sending a malicious FOBS- encoded message. A successful exploit of this vulnerability might lead to code execution.

   NVNVIDIA· Apr 28, 2026

3. 9.8Crit

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

   NVIDIA NVFlare Dashboard contains a vulnerability in the user management and authentication system where an unauthenticated attacker may cause authorization bypass through user-controlled key. A successful exploit of this vulnerability may lead to privilege escalation, data tampering, information disclosure, code execution, and denial of service.

   NVNVIDIA· Apr 28, 2026

4. 3.1Low

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

   LangChain is a framework for building agents and LLM-powered applications. Prior to 1.1.14, langchain-openai's _url_to_size() helper (used by get_num_tokens_from_messages for image token counting) validated URLs for SSRF protection and then fetched them in a separate network operation with independent DNS resolution. This left a TOCTOU / DNS rebinding window: an attacker-controlled hostname could resolve to a public IP during validation and then to a private/localhost IP during the actual fetch.

   L/LangChain / LangSmith· Apr 24, 2026

5. 6.5Med

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

   LangChain is a framework for building agents and LLM-powered applications. Prior to langchain-text-splitters 1.1.2, HTMLHeaderTextSplitter.split_text_from_url() validated the initial URL using validate_safe_url() but then performed the fetch with requests.get() with redirects enabled (the default). Because redirect targets were not revalidated, a URL pointing to an attacker-controlled server could redirect to internal, localhost, or cloud metadata endpoints, bypassing SSRF protections. The response body is parsed and returned as Document objects to the calling application code. Whether this co

   L/LangChain / LangSmith· Apr 24, 2026

6. 9.9Crit

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

   Exposure of sensitive information to an unauthorized actor in Azure IOT Central allows an authorized attacker to elevate privileges over a network.

   MAMicrosoft Azure· Apr 24, 2026

7. 7.5High

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

   Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

   GCGrafana Cloud· Apr 24, 2026

8. 7.5High

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

   Server-side request forgery (ssrf) in Microsoft Dynamics 365 (Online) allows an unauthorized attacker to perform spoofing over a network.

   M3Microsoft 365· Apr 23, 2026

9. 9.3Crit

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

   LeRobot through 0.6.1 contains an unsafe deserialization vulnerability in the async inference pipeline where pickle.loads() is used to deserialize data received over unauthenticated gRPC channels without TLS in the policy server and robot client components. An unauthenticated network-reachable attacker can achieve arbitrary code execution on the server or client by sending a crafted pickle payload through the SendPolicyInstructions, SendObservations, or GetActions gRPC calls.

   HFHugging Face· Apr 23, 2026

10. 7.4High

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

    This vulnerability allows an attacker to create a junction, enabling the deletion of arbitrary files with SYSTEM privileges. As a result, this condition potentially facilitates arbitrary code execution, whereby an attacker may exploit the vulnerability to execute malicious code with elevated SYSTEM privileges.

    TETenable· Apr 23, 2026

11. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed a user to use invalidated or incorrectly scoped credentials to access Virtual Registries under certain conditions.

    GIGitLab· Apr 22, 2026

12. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.4 and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.

    GIGitLab· Apr 22, 2026

13. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that could have allowed an authenticated user to access titles of confidential or private issues in public projects due to improper access control in the issue description rendering process.

    GIGitLab· Apr 22, 2026

14. 6.1Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.1.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an unauthenticated user to access tokens in the Storybook development environment due to improper input validation.

    GIGitLab· Apr 22, 2026

15. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

    GIGitLab· Apr 22, 2026

16. 3.5Low

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user to load unauthorized content into another user's browser due to improper input validation in the Mermaid sandbox.

    GIGitLab· Apr 22, 2026

17. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.3 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user to cause denial of service when importing issues due to improper input validation.

    GIGitLab· Apr 22, 2026

18. 2.7Low

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

    GIGitLab· Apr 22, 2026

19. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service due to insufficient resource allocation limits when retrieving notes under certain conditions.

    GIGitLab· Apr 22, 2026

20. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.4 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service by overwhelming system resources under certain conditions due to insufficient resource allocation limits in the GraphQL API.

    GIGitLab· Apr 22, 2026

21. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service under certain conditions by exhausting server resources by making crafted requests to a discussions endpoint.

    GIGitLab· Apr 22, 2026

22. 8.9High

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

    A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an attacker to extract sensitive environment variables from the instance through a timing side-channel attack against the notebook rendering service. When private mode was disabled, the notebook viewer followed HTTP redirects without revalidating the destination host, enabling an unauthenticated SSRF to internal services. By chaining this with regex filter queries against an internal API and measuring response time differences, an attacker could infer secret values character by character.

    GIGitHub· Apr 21, 2026

23. 7.2High

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

    An improper authorization vulnerability in scoped user-to-server (ghu_) token authorization in GitHub Enterprise Server allows an authenticated attacker to access private repositories outside the intended installation scope, which can include write operations, via an authorization fallback that treated a revoked/deleted installation as a global installation context, which could be chained with token revocation timing and SSH push attribution to obtain and reuse a victim-scoped token. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.

    GIGitHub· Apr 21, 2026

24. 5.3Med

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

    An improper authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated attacker to determine the names of private repositories by their numeric ID. The mobile upload policy API endpoint did not perform an early authorization check, and validation error messages included the full repository name for repositories the caller did not have access to. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. This vulnerability was reported via t

    GIGitHub· Apr 21, 2026

25. 7.5High

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

    An incorrect regular expression vulnerability was identified in GitHub Enterprise Server that allowed an attacker to bypass OAuth redirect URI validation. An attacker with knowledge of a first-party OAuth application's registered callback URL could craft a malicious authorization link that, when clicked by a victim, would redirect the OAuth authorization code to an attacker-controlled domain. This could allow the attacker to gain unauthorized access to the victim's account with the scopes granted to the OAuth application. This vulnerability affected all versions of GitHub Enterprise Server pri

    GIGitHub· Apr 21, 2026

26. 5.3Med

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

    An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed an attacker with admin access on one repository to modify the secret scanning push protection delegated bypass reviewer list on another repository by manipulating the owner_id parameter in the request body. Authorization was verified against the repository in the URL, but the action was applied to a different repository specified in the request body. The impact is limited to assigning existing trusted users as bypass reviewers; it does not allow adding arbitrary external users. This vulnerability affe

    GIGitHub· Apr 21, 2026

27. 8.2High

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

    NVIDIA CUDA-Q contains a vulnerability in an endpoint, where an unauthenticated attacker could cause an out-of-bounds read by sending a maliciously crafted request. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

    NVNVIDIA· Apr 21, 2026

28. 7.7High

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

    NVIDIA KAI Scheduler contains a vulnerability where an attacker could access API endpoints without authorization. A successful exploit of this vulnerability might lead to information disclosure.

    NVNVIDIA· Apr 21, 2026

29. 4.3Med

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

    NVIDIA KAI Scheduler contains a vulnerability where an attacker could cause improper authorization through cross-namespace pod references. A successful exploit of this vulnerability might lead to data tampering.

    NVNVIDIA· Apr 21, 2026

30. 7.7High

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

    Claude Code is an agentic coding tool. Prior to version 2.1.64, Claude Code's sandbox did not prevent sandboxed processes from creating symlinks pointing to locations outside the workspace. When Claude Code subsequently wrote to a path within such a symlink, its unsandboxed process followed the symlink and wrote to the target location outside the workspace without prompting the user for confirmation. This allowed a sandbox escape where neither the sandboxed command nor the unsandboxed app could independently write outside the workspace, but their combination could write to arbitrary locations,

    ANAnthropic (Claude)· Apr 21, 2026

31. 5.4Med

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

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. In versions 4.12.0 through 4.17.1, simultaneous requests that trigger a nonce retry may cause the proxy cache fetcher to perform improper lookups for the token request results. Users are affected if their project uses both the vulnerable versions and the proxy handler /me/* and /my-org/* with DPoP enabled. This issue has been fixed in version 4.18.0.

    AUAuth0· Apr 17, 2026

32. 5.4Med

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

    Claude Code is an agentic coding tool. In versions prior to 2.1.75 on Windows, Claude Code loaded the system-wide default configuration from C:\ProgramData\ClaudeCode\managed-settings.json without validating directory ownership or access permissions. Because the ProgramData directory is writable by non-administrative users by default and the ClaudeCode subdirectory was not pre-created or access-restricted, a low-privileged local user could create this directory and place a malicious configuration file that would be automatically loaded for any user launching Claude Code on the same machine. Ex

    ANAnthropic (Claude)· Apr 17, 2026

33. 6.9Med

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

    Improper neutralization of argument delimiters in the volume handling component in AWS EFS CSI Driver (aws-efs-csi-driver) before v3.0.1 allows remote authenticated users with PersistentVolume creation permissions to inject arbitrary mount options via comma injection. To remediate this issue, users should upgrade to version v3.0.1

    AWAmazon Web Services· Apr 17, 2026

34. 7.5High

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

    Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate operators from completing these workflows. This vulnerability, CVE-2026-5807, is fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.

    HAHashiCorp (HCP / Terraform Cloud)· Apr 17, 2026

35. 8.6High

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

    Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. This may lead to these requests being sent to local network targets, potentially leading to information disclosure. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

    HAHashiCorp (HCP / Terraform Cloud)· Apr 17, 2026

36. 8.8High

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

    If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

    HAHashiCorp (HCP / Terraform Cloud)· Apr 17, 2026

37. 8.1High

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

    An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

    HAHashiCorp (HCP / Terraform Cloud)· Apr 17, 2026

38. 3.3Low

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

    A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records. Due to a backward compatibility condition allowing org_id = 0 records to be returned across organizations, a user with datasource management privileges could read and permanently delete legacy correlation data belonging to another organization. This issue affects correlations created prior to Grafana 10.2 and is fixed in >=11.6.11, >=12.0.9, >=12.1.6, and >=12.2.4. Thanks to Gyu-hyeok Lee (g2h) for reporting this vulnerability.

    GCGrafana Cloud· Apr 15, 2026

39. 5.3Med

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

    The CVE-2021-36156 fix validates the namespace parameter for path traversal sequences after a single URL decode, by double encoding, an attacker can read files at the Ruler API endpoint /loki/api/v1/rules/{namespace} Thanks to Prasanth Sundararajan for reporting this vulnerability.

    GCGrafana Cloud· Apr 15, 2026

40. 9.1Crit

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

    Pyroscope is an open-source continuous profiling database. The database supports various storage backends, including Tencent Cloud Object Storage (COS). If the database is configured to use Tencent COS as the storage backend, an attacker could extract the secret_key configuration value from the Pyroscope API. To exploit this vulnerability, an attacker needs direct access to the Pyroscope API. We highly recommend limiting the public internet exposure of all our databases, such that they are only accessible by trusted users or internal systems. This vulnerability is fixed in versions: 1.15.x: 1.

    GCGrafana Cloud· Apr 15, 2026

41. 8.4High

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

    IdentityIQ 8.5, all IdentityIQ 8.5 patch levels prior to 8.5p2, IdentityIQ 8.4, and all IdentityIQ 8.4 patch levels prior to 8.4p4 allow authenticated users assigned the Debug Pages Read Only capability or any custom capability with the ViewAccessDebugPage SPRight to incorrectly create new IdentityIQ objects. Until a remediating security fix or patches containing this security fix are installed, the Debug Pages Read Only capability and any custom capabilities that contain the ViewAccessDebugPage SPRight should be unassigned from all identities and workgroups.

    SASailPoint· Apr 15, 2026

42. 6.1Med

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

    A vulnerability in the Desktop Agent functionality of Cisco Webex Contact Center could have allowed an unauthenticated, remote attacker to conduct cross-site scripting attacks. Cisco has addressed this vulnerability in the Cisco Webex Contact Center service, and no customer action is needed. This vulnerability existed because HTML and script content was not properly handled. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by persuading a user to follow a malicious link. A successful exploit could have allowed the attacker to steal sensitive info

    WEWebex· Apr 15, 2026

43. 1.3Low

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

    In Grafana's alerting system, users with edit permissions for a contact point, specifically the permissions “alert.notifications:write” or “alert.notifications.receivers:test” that are granted as part of the fixed role "Contact Point Writer", which is part of the basic role Editor - can edit contact points created by other users, modify the endpoint URL to a controlled server. By invoking the test functionality, attackers can capture and extract redacted secure settings, such as authentication credentials for third-party services (e.g., Slack tokens). This leads to unauthorized access and pote

    GCGrafana Cloud· Apr 15, 2026

44. 6.5Med

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

    Mattermost versions 10.11.x <= 10.11.12, 11.5.x <= 11.5.0, 11.4.x <= 11.4.2, 11.3.x <= 11.3.2 fail to enforce atomic single-use consumption of guest magic link tokens, which allows an attacker with access to a valid magic link to establish multiple independent authenticated sessions via concurrent requests.. Mattermost Advisory ID: MMSA-2026-00624

    MCMattermost Cloud· Apr 15, 2026

45. 8.1High

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

    Mattermost versions 10.11.x <= 10.11.12, 11.5.x <= 11.5.0, 11.4.x <= 11.4.2, 11.3.x <= 11.3.2 fail to validate CSRF tokens on an authentication endpoint which allows an attacker to update a user's authentication method via a CSRF attack by tricking a user into visiting a malicious page. Mattermost Advisory ID: MMSA-2026-00625

    MCMattermost Cloud· Apr 15, 2026

46. 2.7Low

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

    Mattermost versions 10.11.x <= 10.11.12 fail to validate whether users were correctly owned by the correct Connected Workspace which allows a malicious remote server connected using the Conntexted Workspaces feature to change the displayed status of local users via the Connected Workspaces API.. Mattermost Advisory ID: MMSA-2026-00603

    MCMattermost Cloud· Apr 15, 2026

47. 6.1Med

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

    Out-of-bounds read in Microsoft Office Word allows an unauthorized attacker to disclose information locally.

    M3Microsoft 365· Apr 14, 2026

48. 8.4High

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

    Use after free in Microsoft Office Word allows an unauthorized attacker to execute code locally.

    M3Microsoft 365· Apr 14, 2026

49. 8.4High

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

    Untrusted pointer dereference in Microsoft Office Word allows an unauthorized attacker to execute code locally.

    M3Microsoft 365· Apr 14, 2026

50. 5.5Med

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

    Improper access control in Microsoft Dynamics 365 (on-premises) allows an authorized attacker to disclose information locally.

    M3Microsoft 365· Apr 14, 2026