CVE Vulnerability Catalog

IBM DataStage on Cloud Pak for Data 5.4.0.0 contains a path traversal vulnerability that can lead to denial of service. A remote authenticated attacker can exploit this to disrupt service availability.

IBM Maximo AI Service 9.1.0 and 9.2.0 contains a vulnerability related to improper control of code generation. A remote attacker can exploit this to execute arbitrary code.

Qexo versions 4.0.0 through 4.2.0 expose /api/init_step/ without authentication, authorization, or a setup-completion guard. An unauthenticated requester with a valid CSRF token can reset the INIT setting and re-enter the setup flow, potentially exposing stored PROVIDER configuration including credentials.

Rapyd Admin versions 9.0.0 before 9.20.0 contain hard-coded credentials that allow remote unauthenticated attackers to gain super-admin access through an admin@laravel account with password admin. The account is seeded by the installer and silently re-created on every rpd:make run, bypassing authorization and tenant scoping.

Netcore NR268 version 1.7.121109 contains an argument injection vulnerability in the execvp function of the file /router/DDNSset.cgi in the DDNS component. Manipulating the Hostname argument can lead to argument injection, and the attack can be launched remotely.

GPT-SoVITS through 20250606v2pro contains an OS command injection vulnerability in tools/uvr5/vr.py that allows unauthenticated attackers to execute commands via output folder paths. Attackers can enter shell substitutions like $(...) in the UVR5 WebUI output folder textboxes with mp3 or m4a export to run commands as the server user.

IBM Db2 Mirror for i versions 7.4, 7.5, and 7.6 are vulnerable to privilege escalation. An authenticated attacker could craft a malicious request that bypasses additional authorization and input validation checks to execute malicious code and gain elevated privileges.

HAProxy Data Plane API versions 2.2.0 through 3.4.3 (and corresponding Enterprise Edition releases) have process-global authentication logic that improperly drops security controls across multiple transport types. When a TLS CA is configured and a numeric TLS port is specified, the application globally disables Basic authentication on its shared internal request handler, allowing unauthenticated attackers to reach affected HTTP or UNIX endpoints and completely bypass credentials to gain full API administrative access.

In Privasys Remote Attestation TLS Clients prior to 0.11.0, TEE attestation evidence is accepted without requiring an explicitly authorized platform identity. A network attacker can forge evidence or extract attestation secrets from a compromised unrevoked platform, causing the verifier to accept valid measurements from a different unrevoked TEE platform as though they came from the intended Attester. This allows impersonation of the attested TLS endpoint.

A flaw was found in Quarkus REST Data Panache that allows unauthenticated attackers to bypass security controls on generated endpoints. When a developer customizes a specific operation using @MethodProperties without explicitly re-declaring security roles, the code generator silently drops class-level security requirements. As a result, the affected endpoint defaults to permissive, unauthenticated access.

In PraisonAI prior to praisonaiagents 1.6.59, AgentTeam.launch and the Agents alias register GET /{path}/list, POST /{path}, and POST /{path}/{agent_id} without access-control checks before listing agents or calling agent.chat. A remotely exposed server can therefore let unauthenticated clients enumerate agents, consume model resources, access connected private context, and trigger agent tools or workflow side effects.

In obsidian-tc prior to 1.3.1, tool dispatch does not compare the caller-controlled input.vault value with the vault bound to the caller, the JWT has no vault claim, and the folder access-control list is shared globally. Any valid token can therefore select another configured vault and read, write, or delete its contents through affected tools.

A vulnerability was identified in Edimax BR-6208AC 1.32 in an unknown function of the file /goform/formWlanMP. Manipulation of the readE2P argument leads to command injection. The attack can be initiated remotely, and the exploit is publicly available and may be used.

A vulnerability was determined in Edimax BR-6208AC 1.32 affecting some unknown processing of the file /goform/formAutoFWupgrade. Manipulation of the tftpsIP argument can lead to command injection. The attack may be performed remotely, and the exploit has been publicly disclosed and may be utilized.

A vulnerability has been found in Edimax BR-6208AC 1.32 affecting an unknown part of the file /goform/formWlanMP. Manipulation of the ateBW argument leads to a buffer overflow. The attack can be executed remotely, and the exploit has been disclosed to the public and may be used.

Grav Login OAuth plugin (grav-plugin-login-oauth) before 1.4.3 provisions OAuth accounts as ordinary Grav users with a deterministic '<provider>.<id>' username and an unsalted MD5 hash of the provider identifier as the password, without disabling password login. An unauthenticated remote attacker who learns or guesses a provider identifier can reproduce these credentials and log in, gaining administrative control of privileged accounts.

A vulnerability was found in Edimax BR-6208AC 1.32 in an unknown function of the file '/goform/formWlSiteSurvey'. Manipulation of the 'ifname' argument causes a buffer overflow that can be exploited remotely. The exploit has been published and may be used; the vendor did not respond and the product is no longer supported.

A vulnerability was determined in Netcore NR268 1.7.121109 in the 'user_ok' function of the CGI Execution component. Manipulation causes improper authentication, and the attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized; the vendor did not respond.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not sufficiently isolate user-supplied code executed through certain REST and XDBC evaluation paths from HTTP request, response, and session state. An attacker able to execute code through an affected path could perform unauthorized actions or compromise an authenticated session.

In @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema level or on Query or Mutation types are silently ignored for top-level fields annotated with @cypher. Only @authentication directives placed directly on individual fields are enforced. An application exposing a top-level @cypher field and relying on schema-level or type-level @authentication allows unauthenticated callers to invoke the field and run the configured Cypher statement with the privileges of the GraphQL service account, potentially permitting reading and modifying data. Fixed in 7.6.4.