CVE Vulnerability Catalog

Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. In Strimzi 1.0.0 and earlier, deploying only the Topic Operator or only the User Operator through the Kafka custom resource leaves the Entity Operator ServiceAccount with RBAC permissions for both components. The excess permissions can allow access to KafkaUser custom resources and Secrets when the User Operator is absent, or access to KafkaTopic custom resources when the Topic Operator is absent.

mcp-searxng before version 1.2.0 has a vulnerability in the web_url_read URL policy that can be bypassed when MCP_HTTP_HARDEN is enabled and MCP_HTTP_ALLOW_PRIVATE_URLS is not enabled. The bypass is due to lack of revalidation of redirect targets, 0.0.0.0 not being classified as internal, and IPv4-mapped IPv6 literals in hexadecimal form not being recognized. An attacker can influence a tool call to make the MCP server fetch loopback or internal HTTP resources and return their content.

mcp-searxng before version 1.2.0 has a vulnerability where web_url_read passes a caller-supplied URL to the server-side fetch path, and assertUrlAllowed() runs only when MCP_HTTP_HARDEN is enabled, which is disabled by default. In the default configuration, an attacker who influences the URL selected by a user or AI agent can make the server fetch loopback, private-network, or cloud metadata endpoint resources and return their contents into the model context.

Sakai versions from 23.0 to 23.5 and 25.3 have a vulnerability where an authenticated user can delete another user's profile image via the DELETE /api/users/{userId}/profile/image endpoint, because ProfileController.removeProfileImage() passes the attacker-controlled userId to ProfileServiceImpl.removeProfileImage() without verifying ownership. Similarly, the DELETE /api/users/{userId}/profile/pronunciation endpoint also omits session validation and ownership checks before deleting the target user's recording.

Bugsink before version 2.2.2 stores every set of custom tags supplied with an incoming event, allowing a caller with a valid project DSN to submit an unusually large tag set and force excessive tag-row writes. Because of the single-writer database architecture, the expensive write transaction delays digestion of other events and causes a temporary ingestion denial of service.

Inspektor Gadget from version 0.27.0 to 0.53.1 has a vulnerability in the uprobe library resolver that can allow an unprivileged container to consume excessive CPU and block other containers from starting by supplying a crafted /etc/ld.so.cache file while an uprobe-based gadget is active. The parser in pkg/uprobetracer/ldcache_parser.go trusts EntryCount enough to perform excessive iteration, computes cache1Len with overflowing uint32 arithmetic, and repeatedly calls readStringFromBytes, where byte-by-byte immutable string concatenation produces quadratic work.

Apptainer before version 1.5.1 has a vulnerability in Image.AuthorizedPath that applies plain string-prefix matching to the limit container paths directive in apptainer.conf, so an allowed path such as /data/safe also authorizes a sibling path such as /data/safe-but-unsafe. A local user can consequently run a container from a directory outside the administrator's intended allowlist when Apptainer operates in setuid mode.

BharatMLStack up to and including 1.3.0 is vulnerable to Cross Site Scripting (XSS) via the component Trufflebox UI (trufflebox-ui) in ExpressionViewModal.jsx.

In BharatMLStack up to and including v1.3.0, Trufflebox UI stores the JWT authentication token, full user object, and session ID in the browser's localStorage, which is fully accessible to any JavaScript running on the page.

BharatMLStack up to and including v1.3.0 is vulnerable to Cross Site Scripting (XSS) in the component Trufflebox UI (trufflebox-ui) in GenericNumerixTable.jsx.

GitLab CE/EE versions from 18.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 have a vulnerability that under certain conditions could have allowed an authenticated user to bypass SAML SSO sign-in restrictions and authenticate without SSO due to missing authentication enforcement checks.

IBM Cloud Pak for Business Automation is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.

IBM Cloud Pak for Business Automation is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

IBM Cloud Pak for Business Automation is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

IBM Business Automation Workflow (containers and traditional) lacks authorization controls, allowing an authenticated attacker to trigger restricted import actions. The flaw stems from insufficient enforcement of permissions on import operations.

IBM Security Verify Identity Access reverse proxy may allow parameters to be injected in requests to third party services.

IBM ContextForge MCP Gateway <= v1.0.4 allows an authenticated user to bypass protection mechanisms due to incomplete recursive inspection of nested payload content. The flaw enables evasion of security controls through content hidden in nested structures.

IBM Cloud Pak for Business Automation versions 26.0.0 through 26.0.0 Interim Fix 001, 25.0.0 through 25.0.0 Interim Fix 005, 24.0.1 through 24.0.1 Interim Fix 008, and 24.0.0 through 24.0.0 Interim Fix 009 is vulnerable to XPath injection. An authenticated attacker could exfiltrate sensitive application data and/or determine the structure of the XML document.

A security flaw has been discovered in Open5GS up to 2.7.7 in the file lib/pfcp/handler.c of the PFCP Message Handler component. Manipulation leads to denial of service. Remote exploitation is possible, and the exploit has been publicly released. The patch is named 028e1dbb5e3271035ccee906ef417a97fc523f71.

A vulnerability was identified in code-projects Record Management System 1.0 in the file main/reg.php. Manipulation of the desc argument leads to cross-site scripting. The attack can be launched remotely, and the exploit is publicly available and might be used.