CVE Vulnerability Catalog

Path traversal vulnerability in BlenderMCP before commit 30a3308 in the download_polyhaven_asset method. Attackers can inject '../' sequences in API response include keys, allowing arbitrary file overwrite.

Vulnerability in the SNMP agent in Loytec devices (LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS, L-PAD) up to version 8.4.16 on LINX-A64. Unchecked input for loop condition (CWE-606) allows an unauthenticated remote attacker to cause persistent denial of service via a crafted SNMP GETNEXT request with a large OID component.

In Apache HBase, the thrift and REST services lack owner authorization in scanner fetch and close operations. A user can fetch rows from scanners opened by other users and close scanners belonging to others, breaking data isolation.

In the keycloak-services library, the core component of the Keycloak identity and access management solution, the role-users endpoint fails to check if an administrator has permission to view individual users when listing role members. A restricted administrator can see private information, such as names and email addresses, of users they should not be able to access.

In Devolutions PowerShell Universal 2026.2.2 and earlier, the variables feature stores secret values in cleartext on disk when no vault is selected. A local attacker with file system access can read these secrets.

Improper access control in automation tests and workflows features of Devolutions PowerShell Universal 2026.2.2 and earlier. An authenticated user with Reader role can execute automation tests and modify workflow properties due to missing server-side authorization.

Sensitive information disclosure in the automation jobs API of Devolutions PowerShell Universal 2026.2.2 and earlier. An authenticated user with job or script read permission can obtain another user's OAuth refresh token via API responses that fail to strip the token.

In the Keycloak Admin REST API, used to manage security realms and clients, when processing requests for rotated client secrets stored in a secure vault, a delegated administrator with view-only permissions can retrieve the actual resolved secret instead of the vault placeholder. This occurs due to improper boundary enforcement, leading to exposure of sensitive credentials.

In AVESİS by ABIS Technology Ltd. Co., there is a vulnerability of external control of an assumed-immutable web parameter, allowing access to functionality not properly constrained by ACLs. This affects AVESİS versions before 202606251646.

DOMPurify before version 3.4.12 fails to execute the afterSanitizeElements hook for custom elements allowed via CUSTOM_ELEMENT_HANDLING.tagNameCheck, allowing attributes to bypass application security policies. Attackers can preserve sensitive attributes on custom elements that later re-inject them into innerHTML sinks, creating second-order XSS gadgets.

Parse Server versions from 9.0.0 before 9.10.0-alpha.5 and from 8.2.2 before 8.6.86 return GraphQL validation error messages that name required custom input fields even when public introspection is disabled (graphQLPublicIntrospection: false, the default). A client holding only the public application ID, with no user session, master key, or maintenance key, can trigger validation errors to learn the names of required custom fields on classes it already references by name, partially defeating the schema-hiding intent of disabling public introspection. No stored data, credentials, optional field names, unreferenced class names, or Cloud Code function names are exposed.

Parse Server versions from 9.0.0 before 9.10.0-alpha.6 and from 8.2.2 before 8.6.87 disclose Pointer and Relation target class names through GraphQL validation and input-coercion error messages when public schema introspection is disabled (graphQLPublicIntrospection: false, the default). Because these errors are produced before authentication, authorization, or any resolver runs, an unauthenticated client possessing only the public application ID can trigger errors on Pointer or Relation fields to reconstruct hidden schema class names, partially defeating the schema-hiding protection. Only schema metadata (class names) is exposed; no object data, credentials, or user records are disclosed.

Improper input validation in Apache NimBLE during Mesh Proxy SAR reassembly, potentially passing broken data to the application causing memory pressure and unstable parsing. Affects versions through 1.9.0. Fixed in 1.10.0.

In Apache NimBLE, there is an incorrect calculation of buffer size when processing Legacy Advertising Report HCI events. When a single HCI event bundles multiple reports, NimBLE miscalculates the offset to the next report, potentially causing out-of-bounds reads and delivering bogus data to the application.

In the accountsservice package, the systemd-homed code path for SetIconFile opens a user-supplied filename as root without the validation and privilege drop performed by the classic handler. A local attacker with a systemd-homed-managed account can read arbitrary files accessible to the accounts-daemon process.

In dbus-broker, when the process file-descriptor limit is reached, EMFILE/ENFILE errors during peer setup (notably SO_PEERPIDFD) are handled as fatal failures, causing the broker to exit. A local attacker who can open many connections to the user session bus can trigger this and deny service to the desktop session. Flatpak applications can reach the host session bus through the dbus proxy.

The Ninja Forms plugin for WordPress is vulnerable to generic SQL injection via import files. An authenticated attacker with admin privileges can append SQL queries to existing ones to extract sensitive data from the database.

In Apache OpenNLP before versions 2.5.10 and 3.0.0-M5, a vulnerability allows arbitrary class instantiation. An attacker can supply a crafted model or format name, leading to loading and executing code from dangerous classes.

In GNU coreutils unexpand, a heap-based buffer overflow occurs due to an integer overflow during buffer allocation when processing large -t values. This can lead to out-of-bounds heap write and potentially achieve a heap write primitive.

In the GNU coreutils uniq utility, an out-of-bounds read vulnerability exists due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates byte length by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input, leading to a crash and potential adjacent heap memory exposure.