CVEs.

Matching CVEs

1. 7.2High

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

   In Progress ShareFile Storage Zones Controller v5.12.5 and below, a party with valid zone credentials can perform path traversal using resumable upload initiation endpoint, allowing the party to write arbitrary content to any location writable by the application's service account. This may result in the execution of attacker-supplied code.

   SHShareFile· Aug 17, 2026

2. 7.1High

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

   A SQL injection vulnerability exists in Security Center that could allow an attacker to access unauthorized data from the application's database.

   TETenable· Aug 14, 2026

3. 8.7High

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

   An input validation vulnerability exists in Security Center's file upload handling, where insufficient sanitization of uploaded filenames could contribute to a downstream command injection issue.

   TETenable· Aug 14, 2026

4. 8.5High

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

   A local privilege escalation vulnerability exists in Security Center. An attacker with write access to a specific configuration file could achieve arbitrary code execution with elevated privileges, without requiring further user or victim interaction.

   TETenable· Aug 14, 2026

5. 8.6High

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

   A privilege escalation vulnerability exists in Tenable Security Center that allows a user with "Security Manager" role and "manage user" permission on a single group to modify users belonging to other groups. This bypasses the intended access control restrictions and enables unauthorized cross-group user management.

   TETenable· Aug 14, 2026

6. 8.6High

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

   A command injection vulnerability exists in Tenable Security Center. An authenticated administrator could modify application configuration values to achieve arbitrary command execution on the underlying operating system when specific backend operations are triggered.

   TETenable· Aug 14, 2026

7. 8.8High

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

   Kibana Agent Builder does not correctly verify that the requesting user holds the privileges required by a separate Kibana feature before it creates and runs a tool that invokes that feature's functionality. This allows privilege escalation and could lead to disclosure of sensitive information that the user is not authorized to read.

   ECElastic Cloud· Aug 13, 2026

8. 7.3High

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

   Relative Path Traversal (CWE-23) in Kibana can lead to the unauthorized deletion of Kibana resources via Relative Path Traversal (CAPEC-139). Kibana Fleet accepted a user-supplied identifier for a Fleet Server host configuration without rejecting relative traversal sequences. The identifier is stored as provided and is later incorporated into the request that Kibana issues when that configuration is removed.

   ECElastic Cloud· Aug 13, 2026

9. 7.1High

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

   Missing Authorization (CWE-862) in Kibana can lead to cross-space information disclosure and unauthorized data modification via Privilege Abuse (CAPEC-122). Kibana Machine Learning carries out its Elasticsearch operations with elevated internal permissions and relies on a per-request space filter to keep the machine learning data of one space separated from another. Part of the Machine Learning functionality did not apply that filter, so operations issued from one space were carried out against the machine learning data of every space in the deployment.

   ECElastic Cloud· Aug 13, 2026

10. 7.7High

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

    The Elastic Security capability that suggests existing field values while a user authors endpoint policy artifacts queries Elastic Defend event data with Kibana's internal Elasticsearch account instead of the account of the requesting user. Only Kibana feature privileges are verified, and the caller's Elasticsearch index privileges are not. An authenticated user who holds Elastic Security feature privileges but no read access to the Elastic Defend event indices can therefore retrieve field values from that data, including process command line arguments, which commonly contain tokens, credentia

    ECElastic Cloud· Aug 13, 2026

11. 7.6High

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

    The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flow, and the routes that read and update that state do not verify ownership. An authenticated user who holds only generic read access to the space can therefore discover the onboarding flows of other users, read their onboarding state, and write arbitrary progress data into them. A tampered flow can also cause the owner's onboarding view to fail with a server error.

    ECElastic Cloud· Aug 13, 2026

12. 8.1High

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

    Missing Authorization (CWE-862) in Kibana can lead to unauthorized execution of Osquery and Elastic Defend response actions on managed hosts via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A Kibana user who is able to author and evaluate Elastic Security detection rules can cause response actions to be carried out against enrolled agents without holding the Osquery live query privileges or the Elastic Defend response action privileges that normally govern those capabilities. Depending on the response action involved, this can result in disclosure of information from the

    ECElastic Cloud· Aug 13, 2026

13. 7.3High

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

    Cross-Site Request Forgery (CWE-352) in Kibana can lead to privilege escalation via Cross Site Request Forgery (CAPEC-62). A user who is permitted to create visualizations can save a specially crafted Vega visualization that, when it is opened by another user, causes authenticated requests to be issued to Kibana in the context of the viewing user's session.

    ECElastic Cloud· Aug 13, 2026

14. 7.1High

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

    Kibana Agent Builder determines whether a caller owns a private agent by comparing a stable user identifier when one is recorded, and falling back to a comparison of the username when it is not. A username is not unique across Elasticsearch authentication realms, so two distinct principals that share a username in different realms are treated as the same owner. This discloses the configuration and instructions of an agent the caller does not own, and allows that agent to be altered or removed.

    ECElastic Cloud· Aug 13, 2026

15. 8.8High

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

    The native inference process that Elasticsearch uses to evaluate uploaded machine learning models accepts a model operation that computes a memory address from an offset supplied inside the model, without validating that the offset stays within the bounds of the underlying storage. A user with the privileges required to upload and deploy a trained model can craft a model that reads and writes memory outside the intended allocation. The result is heap corruption that crashes the inference process, and, with sufficient control over the heap layout, could allow arbitrary code execution in the con

    ECElastic Cloud· Aug 13, 2026

16. 7.1High

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

    Observable Discrepancy (CWE-203) in Kibana Fleet can lead to information disclosure via Excavation (CAPEC-116). Fleet removes the Elasticsearch API key value of an enrolled Elastic Agent from the responses of its agent listing capability, but that capability accepted caller-supplied filter expressions over the stored field that holds the value, and evaluated them with Kibana's own internal Elasticsearch privileges rather than the caller's. Because the number of matching agents is reported back to the caller, the difference between a matching and a non-matching filter formed a side channel from

    ECElastic Cloud· Aug 13, 2026

17. 7.1High

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

    Incorrect Authorization (CWE-863) in Kibana Fleet can lead to privilege escalation via Privilege Abuse (CAPEC-122). Fleet restricts some callers to managing integration policies for one specific integration. When an existing integration policy was updated, that restriction was evaluated against the integration recorded on the stored policy rather than against the replacement integration supplied with the update. An authenticated user holding only the Elastic Defend endpoint policy management privilege was therefore able to convert an endpoint policy they administer into a policy for a differen

    ECElastic Cloud· Aug 13, 2026

18. 7.1High

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

    Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized cross-space access via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). The result is disclosure of inference output from a trained model in a different space that the user is not authorized to list, read, or use, which exposes the behavior of a model. The same pattern also reached the deployment stop and deployment update operations, allowing an active trained model deployment in another space to be stopped or to have its allocated resources altered.

    ECElastic Cloud· Aug 13, 2026

19. 8.4High

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

    A data source definition containing an over-length file path setting may cause the MongoDB BI Connector ODBC Driver setup dialog to write outside the bounds of an allocated buffer. The issue stems from an incorrect buffer capacity calculation in the dialog's file and folder selection handling, and is reached only when a user opens the setup dialog for such a data source and initiates a file or folder selection. Depending on build configuration, the result may range from abnormal process termination to, under certain conditions, execution of unintended code in the context of the user running th

    MAMongoDB Atlas· Aug 12, 2026

20. 8.8High

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

    An application using the MongoDB BI Connector ODBC Driver may experience a memory-safety issue when processing output parameters from a stored procedure. Triggering this issue requires connecting to an untrusted or impersonated database server that returns crafted metadata. This may result in process termination, disclosure of process memory, or, under certain conditions, arbitrary code execution.

    MAMongoDB Atlas· Aug 12, 2026

21. 8.8High

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

    A missing bounds check when parsing stored procedure parameter metadata in the MongoDB BI Connector ODBC Driver can result in an out-of-bounds write in the client application process. Triggering this issue requires control over the server the driver connects to, or the ability to respond in its place, in order to return malformed metadata. The resulting memory corruption may cause the client application to terminate abnormally or, under certain conditions, execute unintended code.

    MAMongoDB Atlas· Aug 12, 2026

22. 7.1High

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

    The MongoDB BI Connector ODBC Driver converts floating point column values into text without checking that the result fits within the destination buffer. When an application reads a sufficiently large floating point value as text, the driver may write beyond the end of that buffer and corrupt adjacent memory. A user who can store data in a collection read through the BI Connector could use this to crash the application performing the read.

    MAMongoDB Atlas· Aug 12, 2026

23. 8.5High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to cause AI usage to be attributed to another namespace, due to improper authorization of identity information supplied in requests.

    GIGitLab· Aug 12, 2026

24. 7.1High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to modify project settings restricted to higher-privileged roles, due to missing authorization checks on a project update endpoint.

    GIGitLab· Aug 12, 2026

25. 8.7High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled values rendered in table cell content by an analytics dashboard component.

    GIGitLab· Aug 12, 2026

26. 8.7High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled data rendered in pagination controls by an analytics dashboard component.

    GIGitLab· Aug 12, 2026

27. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.

    GIGitLab· Aug 12, 2026

28. 8.8High

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

    A low-privileged user may poison cached artifact metadata under specific conditions, potentially causing consumers to retrieve untrusted content.

    JFJFrog· Aug 12, 2026

29. 7.5High

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

    JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources.

    JFJFrog· Aug 12, 2026

30. 8.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute CI/CD pipelines on a protected branch without the required push permissions due to improper authorization in pipeline reference validation.

    GIGitLab· Aug 12, 2026

31. 8.1High

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

    An unauthenticated attacker may cause untrusted package content to be cached under specific conditions, potentially affecting artifact integrity and availability.

    JFJFrog· Aug 12, 2026

32. 7.2High

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

    A holder of a valid integration credential may impersonate other users under specific conditions.

    JFJFrog· Aug 12, 2026

33. 7.5High

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

    A user with access to a valid SAML response may impersonate another user under specific conditions.

    JFJFrog· Aug 12, 2026

34. 7.2High

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

    A Project Resource Manager may gain broader administrative privileges under specific conditions.

    JFJFrog· Aug 12, 2026

35. 8.1High

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

    A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.

    JFJFrog· Aug 12, 2026

36. 7.8High

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

    A maliciously created executable, when executed on the victim's machine, may allow a local low-privileged attacker to inject unauthenticated IPC messages into named pipes, modify pipe permissions or ownership, and potentially impact confidentiality, integrity, and availability.

    AUAutodesk· Aug 12, 2026

37. 8.8High

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

    Description Cloudflare was recently notified by external researchers of vulnerabilities in this archived repository, including a remote code execution issue in `src/index.ts` reachable from certain GitHub Actions workflow configurations. Successful exploitation may expose workflow secrets such as CLOUDFLARE_API_TOKEN and GITHUB_TOKEN to an attacker. Because this repository has been deprecated since 2024, Cloudflare will not be issuing patches. To remediate this issue, we recommend migrating to `cloudflare/wrangler-action` immediately. Consumers who have already migrated are not affected. Sunse

    CLCloudflare· Aug 12, 2026

38. 8.2High

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

    A MongoDB driver component could write sensitive configuration information, including a credential used for outbound network connectivity, to application log output in cleartext during routine client initialization. This occurs automatically as part of normal operation and requires no special privileges to trigger. A party able to read the affected application's logs or downstream log-aggregation storage could recover the credential and reuse it to authenticate to the associated network infrastructure. This issue affects confidentiality only.

    MAMongoDB Atlas· Aug 11, 2026

39. 7.2High

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

    An issue in MongoDB Server's Queryable Encryption maintenance operations could allow an authenticated user with privileges on one encrypted collection to cause unauthorized modification or destruction of data belonging to a different collection. This is due to insufficient validation of certain internal metadata references before they are used to perform operations on other namespaces.

    MAMongoDB Atlas· Aug 11, 2026

40. 7.1High

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

    An issue in MongoDB Server's query execution engine could allow an authenticated user with read and write privileges to cause an internal reference to be used after the underlying memory has been freed, when running certain queries against time-series collections. This could result in a server crash or disclosure of freed memory contents within query results.

    MAMongoDB Atlas· Aug 11, 2026

41. 7.5High

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

    An issue in MongoDB Server's $graphLookup aggregation stage could allow an authenticated user able to issue aggregation and memory-management commands to cause an internal reference to be used after the underlying memory has been freed. This could result in a server crash or, potentially, execution of unintended code.

    MAMongoDB Atlas· Aug 11, 2026

42. 7.1High

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

    An issue in MongoDB Server's Atlas Vector Search feature could allow an authenticated user with read access to one view to retrieve documents from a different, protected view over the same underlying collection. This is due to insufficient handling of certain user-supplied fields when constructing an internal request forwarded to the search process.

    MAMongoDB Atlas· Aug 11, 2026

43. 7.1High

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

    An issue in MongoDB Server's aggregation framework could allow an authenticated user with only read privileges to perform write operations against collections they should not be able to modify. This is due to an internal-use aggregation stage being reachable by external clients without an appropriate authorization check on its embedded operations.

    MAMongoDB Atlas· Aug 11, 2026

44. 7.1High

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

    An issue in MongoDB Server's query subsystem could allow an authenticated user with read privileges to cause the server process to terminate unexpectedly by submitting a specially formed query filter. This could result in a denial of service.

    MAMongoDB Atlas· Aug 11, 2026

45. 8.7High

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

    An issue in MongoDB Server's aggregation framework could allow an unauthenticated party to cause a mongos (router) process to terminate unexpectedly by submitting a specially formed aggregation command. This could result in a denial of service, disrupting client connections routed through the affected mongos instance.

    MAMongoDB Atlas· Aug 11, 2026

46. 7.0High

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

    An issue in MongoDB Server's applyOps command could allow an authenticated user with specific non-default privileges to perform certain data-definition operations, such as dropping or modifying collections, against collections they do not have permission to manipulate. This is due to an inconsistency in how the target collection is determined between the authorization check and the actual operation.

    MAMongoDB Atlas· Aug 11, 2026

47. 7.1High

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

    An issue in MongoDB Server's handling of certain query predicates against time-series collections with a metaField could allow an authenticated user with write access to cause the server process to terminate unexpectedly, resulting in a denial of service.

    MAMongoDB Atlas· Aug 11, 2026

48. 7.1High

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

    An issue in MongoDB Server's geospatial query processing could allow an authenticated user with write privileges to cause certain malformed geometry data to be stored and later processed without proper validation. Subsequent queries against this data could then result in the server accessing memory outside its intended bounds. This could result in a server crash (denial of service) and may expose a limited amount of server process memory.

    MAMongoDB Atlas· Aug 11, 2026

49. 7.2High

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

    An issue in MongoDB Server's handling of timeseries collections could allow an authenticated user with write privileges to cause an internal data structure to become inconsistent through certain document insertions. A subsequent insert into the affected bucket could then result in the server accessing memory outside its intended bounds, potentially causing a server crash (denial of service), exposure of limited memory contents, or memory corruption.

    MAMongoDB Atlas· Aug 11, 2026

50. 7.7High

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

    An issue in MongoDB Server's handling of timeseries bucket lifecycle could allow an authenticated user with write privileges to cause an internal reference to be used after the underlying memory has been freed. Subsequent operations could then result in a server crash or, potentially, execution of unintended code.

    MAMongoDB Atlas· Aug 11, 2026