Snipe-IT before 8.6.0 contains an authorization bypass (insecure direct object reference) in the asset checkout-request cancellation endpoint. The cancel_by_admin and requestingUser values are read from user-controlled URL path segments and used without a server-side authorization check, so any authenticated, low-privileged user can supply a non-empty cancel_by_admin value to bypass the request-ownership check and cancel another user's pending checkout request. Because asset and user identifiers are sequential integers, an attacker can enumerate them to cancel every pending checkout request, disrupting the asset-request workflow. This is fixed in Snipe-IT 8.6.0.
An issue in MongoDB Server's Atlas Vector Search feature could allow an authenticated user with read access to one view to retrieve documents from a different, protected view over the same underlying collection. This is due to insufficient handling of certain user-supplied fields when constructing an internal request forwarded to the search process.
SAP Approuter does not sufficiently validate tenant context in inbound requests. An unauthenticated attacker could send specially crafted requests to spoof the tenant context under conditions not fully within their control. Successful exploitation could allow limited access to another tenant's information, resulting in a low impact on confidentiality. There is no impact on integrity and availability.
IBM Langflow OSS 1.0.0 through 1.10.3 Langflow allows remote authenticated attackers to bypass localhost-only restrictions and write arbitrary MCP server configurations to IDE configuration files on the host system.
An authenticated user with low privileges may be able to perform unauthorized reads and writes on data protected by role-based query-level access controls, due to insufficient validation of certain client-supplied command parameters. The issue affects find, update, delete, and aggregate commands in non-apiStrict configurations.
Eclipse Kura versions prior to 5.6.2 trust the client-supplied X-Forwarded-For HTTP header as the authoritative source of the client IP address in audit log entries. The org.eclipse.kura.web2 (Web Console) and org.eclipse.kura.rest.provider (REST API) components use this header as the primary IP source when initializing audit context, and org.eclipse.kura.jetty.customizer unconditionally installs Jetty's ForwardedRequestCustomizer on all HTTP/HTTPS connectors, causing HttpServletRequest.getRemoteAddr() to reflect the attacker-controlled header value. An unauthenticated remote attacker can exploit this vulnerability to bypass IP-based brute-force protections — such as fail2ban — by spoofing the logged IP address to a non-routable value, allowing a brute-force attack to proceed undetected, or to cause a denial of service against a third party by injecting a victim's IP address and triggering a ban on that address.
pam_usb versions prior to 0.9.2 are vulnerable to environment variable injection via the XRDP_SESSION, DISPLAY, and TMUX variables. These variables affect local-check logic determining session locality in PAM modules running with elevated privileges. An attacker with local access can manipulate these environment variables to influence authentication decisions. This vulnerability has been fixed in version 0.9.2.
e107 is a content management system (CMS). Prior to 2.3.4, a Host Header Injection vulnerability in the password reset page allows attackers to manipulate the Host header to generate password reset links pointing to attacker-controlled domains. This can lead to phishing attacks, account takeover, or other security risks. The severity is high, as the vulnerability affects a critical function related to user authentication. This vulnerability is fixed in 2.3.4.
A vulnerability in Remote Spark SparkView before build 1122 allows an attacker to bypasses the local connection check and achieve arbitrary code execution as root on the server side. Depending on implementation the vulnerability can be exploited by an unauthenticated attacker.
Reliance on Untrusted Inputs in a Security Decision vulnerability in mtrudel bandit allows unauthenticated transport-state spoofing on plaintext HTTP connections.
'Elixir.Bandit.Pipeline':determine_scheme/2 in lib/bandit/pipeline.ex returns the client-supplied URI scheme verbatim, ignoring the transport's secure? flag. HTTP/1.1 absolute-form request targets (e.g. GET https://victim/path HTTP/1.1) and the HTTP/2 :scheme pseudo-header are both attacker-controlled strings that flow through this function. Over a plaintext TCP connection, a client can declare https and Bandit will set conn.scheme = :https even though no TLS was negotiated.
Downstream Plug consumers that branch on conn.scheme are silently misled: Plug.SSL's already-secure branch skips its HTTP→HTTPS redirect, cookies emitted with secure: true are sent over plaintext, audit logs record requests as having arrived over HTTPS, and CSRF/SameSite gating may make incorrect decisions.
This issue affects bandit: from 1.0.0 before 1.11.0.
OpenClaw versions before 2026.3.31 contain a vulnerability where proxied remote requests are misclassified as local loopback connections in the diffs viewer when the allowRemoteViewer setting is disabled. This misclassification allows attackers to bypass access controls and gain unauthorized access to the remote viewer functionality.
OpenClaw versions before 2026.3.28 have a vulnerability where the exec allowlist bypasses the intended security checks. The allow-always persistence mechanism fails to properly unwrap wrapper scripts like /usr/bin/script before storing trust decisions, allowing attackers to persist trust for wrapper binaries that can execute different underlying programs after obtaining user approval for one wrapped command.
OpenClaw versions before 2026.3.28 have a vulnerability in the execution approval mechanism that improperly trusts wrapper carrier executables instead of the actual invoked targets. This flaw allows attackers to exploit positional routing through dispatch wrappers to create broader allowlist entries than intended, weakening execution approval boundaries and potentially allowing unauthorized code execution.
CVE-2026-1789 is a medium-severity vulnerability in Canon Inc. 's imagePRESS Series printers. It involves a weakness in the browser-based remote management interface where reliance on untrusted inputs in security decisions may allow an administrator to access sensitive information via crafted requests. This affects all versions of the product. There is no known exploit in the wild and no official patch or remediation guidance has been provided yet.
OpenClaw versions before 2026.3.28 have an authorization bypass vulnerability in the chat.send gateway method. The flaw arises because ACP-only provenance fields are controlled by client metadata from the WebSocket handshake, which is self-declared and not verified against the actual authorization state. This allows authenticated operator clients to spoof ACP identity labels and inject reserved provenance fields intended only for the ACP bridge by manipulating client metadata during connection.
CVE-2026-35624 is a low-severity vulnerability in OpenClaw before version 2026.3.22. It involves a policy confusion issue in room authorization where the system matches colliding room names instead of stable room tokens. This flaw allows attackers to bypass allowlist policies by exploiting similarly named rooms, potentially gaining unauthorized access to protected Nextcloud Talk rooms.
An attacker could use data obtained by sniffing the network traffic to
forge packets in order to make arbitrary requests to Contemporary
Controls BASC 20T.
CVE-2026-29134 is a medium severity vulnerability in SEPPmail Secure Email Gateway versions before 15.0.3. It allows an external user with low privileges to modify GINA webdomain metadata, which can lead to bypassing per-domain restrictions. This issue stems from reliance on untrusted inputs in a security decision (CWE-807). No official patch or remediation details are provided in the available data. There are no known exploits in the wild at this time.