Export limit exceeded: 376587 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 376587 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (376587 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-66380 | 1 Jfrog | 1 Artifactory | 2026-08-12 | 4.3 Medium |
| An authenticated user without repository read permission may access private OCI referrer metadata under specific conditions. | ||||
| CVE-2026-68755 | 1 Jfrog | 1 Artifactory | 2026-08-12 | 4.3 Medium |
| A bundle writer may create misleading release promotion information under specific conditions. | ||||
| CVE-2026-66382 | 1 Jfrog | 1 Artifactory | 2026-08-12 | 4.3 Medium |
| An authenticated user may write files outside the intended Artifactory work directory under specific conditions. | ||||
| CVE-2026-70547 | 1 Jfrog | 1 Artifactory | 2026-08-12 | 4.3 Medium |
| An authenticated user without repository read permission may access package metadata under specific conditions. | ||||
| CVE-2026-65938 | 1 Progress Software | 1 Whatsup Gold | 2026-08-12 | 4.3 Medium |
| In WhatsUp Gold versions released before 2026.0.2, an improper authorization vulnerability in the Scheduled Reports API allows any authenticated user to invoke restricted actions. | ||||
| CVE-2026-15803 | 1 Eclipse | 1 Rdf4j | 2026-08-12 | N/A |
| In Eclipse RDF4J, several XML parser entry points do not fully restrict XML External Entity (XXE) processing when parsing untrusted XML-based RDF data or query results, permitting DOCTYPE declarations, external entity references, and external DTD loading. This is due to an incomplete fix for CVE-2018-1000644: the earlier fix did not cover all parser entry points. The issue is resolved in RDF4J 5.3.2, which rejects or disables DOCTYPE declarations, external entities, and external DTD loading by default. | ||||
| CVE-2026-49467 | 1 Smp46 | 1 Pingvin-share-x | 2026-08-12 | 8.8 High |
| Pingvin Share X is a secure and easy self-hosted file sharing platform. A vulnerability in versions 1.5.0 through 1.18.0 allow an attacker to bypass password verification when managing Time-based One-Time Password (TOTP) settings. The root cause is a missing `await` keyword on calls to the asynchronous `verifyPassword` method in `authTotp.service.ts` and the `authenticateUser` method in `auth.service.ts`. In JavaScript, an unawaited `Promise` is always truthy. So the logic intended to throw a `ForbiddenException` when a password is incorrect. It never executes because the expression evaluates the existence of the `Promise` object rather than its resolved boolean result. The vulnerability is fixed in version 1.18.1 by ensuring all asynchronous authentication calls are properly awaited. There are no official workarounds. If a user is locked out, an administrator must manually reset the user's TOTP status in the database. | ||||
| CVE-2026-44741 | 1 Pimcore | 1 Pimcore | 2026-08-12 | 8.8 High |
| Pimcore's Admin Classic Bundle provides a Backend UI for Pimcore. Versions prior to 2.3.6 and 1.7.18 have a SQL injection vulnerability in Pimcore's translation grid date filter — the user-supplied `property` field from the filter JSON is interpolated directly into a `UNIX_TIMESTAMP(DATE(FROM_UNIXTIME(...)))` SQL expression without parameterization or allowlist validation. Versiosn 2.3.6 and 1.7.18 fix the issue. | ||||
| CVE-2026-19642 | 1 Aws | 1 Aws-sdk-cpp | 2026-08-12 | 5.9 Medium |
| An out-of-bounds write issue in the Base64 decoder in Amazon aws-sdk-cpp before 1.11.862 might allow a remote authenticated user to cause a crash or heap memory corruption in an application that processes crafted Base64-encoded input. To remediate this issue, users should upgrade to version 1.11.862. | ||||
| CVE-2026-17642 | 1 Ibm | 1 I | 2026-08-12 | 8.8 High |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. | ||||
| CVE-2026-18150 | 1 Ibm | 1 I | 2026-08-12 | 4.3 Medium |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to obtain sensitive information due to a race condition. | ||||
| CVE-2026-72508 | 1 Redhat | 1 Acm | 2026-08-12 | 9.9 Critical |
| A flaw was found in the multicloud-operators-subscription component of Red Hat Advanced Cluster Management (RHACM). This vulnerability allows a namespace-admin tenant to perform a confused-deputy attack by creating Subscription Custom Resources (CRs) that leverage a highly privileged ServiceAccount (SA). This enables the tenant to deploy arbitrary cluster-scoped resources, leading to privilege escalation and potential arbitrary code execution across the cluster. | ||||
| CVE-2026-18148 | 1 Ibm | 1 I | 2026-08-12 | 4.3 Medium |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to inject arbitrary content into Navigator log files due to improper output neutralization for logs. | ||||
| CVE-2026-17082 | 1 Ibm | 1 I | 2026-08-12 | 8.8 High |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain elevated privileges due to improper validation of a client-supplied profile name. | ||||
| CVE-2025-13736 | 1 Wso2 | 10 Api Manager, Identity Server, Identity Server As Key Manager and 7 more | 2026-08-12 | 3.7 Low |
| When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts. For valid users, the server resolves and displays their canonical username, while for non-existent users, it echoes the original input. This occurs regardless of the validate_username configuration. The discovery of valid usernames can increase the risk of brute force attacks, social engineering attacks, and targeted information leakage. Attackers can leverage this information to craft more effective phishing campaigns or social engineering tactics to compromise user accounts or extract sensitive data. | ||||
| CVE-2026-17083 | 1 Ibm | 1 I | 2026-08-12 | 9.8 Critical |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code due to a stack-based buffer overflow. | ||||
| CVE-2026-17445 | 1 Ibm | 1 I | 2026-08-12 | 8.2 High |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to bypass security restrictions due to improper validation of an attacker-supplied user profile name. | ||||
| CVE-2026-18382 | 2 Red Hat, Redhat | 3 Cost Management Metrics Operator, Cost Management, Cost Management Metrics Operator | 2026-08-12 | 6.8 Medium |
| A flaw was found in koku-metrics-operator. The operator's CostManagementMetricsConfig custom resource allows a user able to edit the CR to specify an arbitrary OAuth token endpoint. When authentication.type is set to service-account, the operator sends the tenant's Red Hat SSO client_id and client_secret to this user-controlled URL, allowing the attacker to obtain the credentials. | ||||
| CVE-2026-17417 | 1 Ibm | 1 I | 2026-08-12 | 8.8 High |
| IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of shell metacharacters. | ||||
| CVE-2025-15039 | 1 Wso2 | 20 Api Control Plane, Api Manager, Carbon Identity Application Authentication Framework and 17 more | 2026-08-12 | 9.4 Critical |
| The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps. | ||||