CVE Vulnerability Catalog

In GNU C Library versions 2.38 to 2.44, calling strfmon or strfmon_l can write past the end of the caller-supplied output buffer when a conversion uses right-justified width padding. Exploitation requires an application code path that calls these functions with right-justified width padding into a destination buffer large enough for the padding but too small for the internal memmove call. At the time of publication, no network-facing application impact is known.

gRPC-Go prior to 1.82.2 and 1.83.2 allows servers created with xds.NewGRPCServer() to accept an RPC lacking both the :authority and Host headers. RouteAndProcess assumes an authority value exists and indexes an empty slice, causing an index-out-of-bounds panic that terminates the entire server process.

Cisco Secure Email Gateway and Cisco Secure Email and Web Manager contain vulnerabilities found during an internal security review, related to improper validation of specified quantity in input (CWE-1284).

Laravel MagicLink versions 2.0.0 through 2.25.1 store serialized action objects in the magic_links.action database column and deserialize them without sufficient integrity protection, with an unsafe legacy unserialize() fallback. An attacker able to manipulate database records can insert a malicious serialized object graph and execute arbitrary code when the magic link is visited.

Argos JavaScript SDK before core package version 6.2.1 allows attacker-controlled CI branch or ref values to be interpolated into commands executed by /bin/sh -c. Shell metacharacters in a pull-request branch name can execute arbitrary commands with Argos upload process privileges.

Alchemy CMS before versions 7.4.15, 8.0.15, 8.1.14, and 8.2.6 exposes an unauthenticated GET /api/pages/nested endpoint that returns an unfiltered page tree without authorization. Restricted and unpublished page metadata and element/ingredient content can be retrieved.

gettext-converter before version 1.3.3 in js2i18next() uses dynamic object keys without rejecting __proto__, constructor, or prototype. Converting untrusted translation data can lead to prototype pollution affecting the entire process.

Pimcore before versions 11.5.19, 12.3.10, and 2026.1.6 allows an authenticated user with reports_config permission to inject SQL fragments into report configuration fields. Executing the report can disclose, modify, or delete arbitrary database data.

Pimcore before version 2026.1.5 allows an authenticated user with objects permission to submit a malicious ClassDefinition UID that is used in SQL queries without proper quoting. This can lead to reading or modifying arbitrary database tables, including disclosure of password hashes.

node-opcua before version 2.166.0 stores nonces in a global cache without expiration or size limit. An unauthenticated attacker can repeatedly create sessions with unique nonces, causing unbounded heap growth and crashing the server.

node-opcua before version 2.166.0 in UserNameIdentityToken handling does not verify that trailing bytes match the current serverNonce. This allows an attacker to forge a token with an empty password or replay a captured token in another session.

GIMP when processing a specially crafted lighting preset file does not properly validate the number of light sources in the Lighting Effects filter. This can lead to an out-of-bounds write, potentially causing a crash or enabling arbitrary code execution.

parallax filament-comments through 3.0.0 contains a stored cross-site scripting vulnerability in comment body rendering that allows authenticated panel users to inject malicious scripts. Scripts execute in the browsers of other users, including administrators.

Ekia File Manager 1.2.7 exposes an exported ContentProvider OpenFileProvider without requiring caller permissions. Another local application can map a URI path to an arbitrary file path and perform read, create, overwrite, or delete operations in the context of the File Manager process.

In PraisonAI prior to 4.6.62, setting PRAISONAI_CALL_AUTH to disabled makes verify_token accept requests to /api/v1/agents/{id}/invoke without CALL_SERVER_TOKEN authentication. Deployments using the advertised opt-out can expose registered agents and their connected tools or private context to unauthenticated invocation.

In PraisonAI prior to 4.6.59, the WhatsApp and Linear bot webhook handlers verify HMAC signatures only when WHATSAPP_APP_SECRET or LINEAR_WEBHOOK_SECRET is configured, otherwise parsing and dispatching unsigned request bodies. A remote unauthenticated client reaching the webhook route can forge messages, comments, or agent-session events, impersonate platform users, and disrupt bot processing.

In PraisonAI prior to 4.6.59, the unauthenticated Jobs API accepts an absolute or traversing agent_file path in POST /api/v1/runs and passes it to the job executor without a workspace allowlist or boundary check. A remote caller can cause the server to open files accessible to the service account, exposing credentials, keys, environment variables, and other local data.

In PraisonAI prior to 4.6.59, the CODE_TOOLS wrappers keep _workspace_root as None and pass workspace=None to read_file, search_replace, and apply_diff helpers that enforce path containment only for a truthy workspace. An application exposing code_read_file, code_search_replace, or code_apply_diff before set_workspace can let prompt-influenced calls read and modify files outside the intended project directory.

In OpenTelemetry Operator prior to 0.152.0, TargetAllocator instances with targetAllocator.prometheusCR.enabled set to true preserve a selected ServiceMonitor endpoint's bearerTokenFile value as HTTPClientConfig.Authorization.CredentialsFile. A tenant who can create or update a ServiceMonitor matched by selectors can point bearerTokenFile at a file in the Collector pod, including the service account token, and direct scraping to a tenant-controlled endpoint, disclosing the Collector's service-account JWT or other mounted files.

A weakness has been identified in itsourcecode Leave Management System 1.0. Affected is some unknown functionality of the file /login.php. Manipulation of the user_email argument can lead to SQL injection. The attack may be launched remotely, and the exploit has been made available to the public.