OpenRemote core versions before 1.31.0 have an authorization bypass vulnerability that allows authenticated users to access gateway tunnel information from other realms. This can expose internal target hosts, ports, and routing data by exploiting the getGatewayActiveTunnelInfos endpoint with manipulated parameters.
OpenRemote core versions before 1.31.0 have an authorization bypass vulnerability that allows realm administrators to impersonate gateways in other realms. This occurs because the GatewayService only verifies the gateway ID without validating the associated realm. Attackers with WRITE:ADMIN privileges in one realm can create a service user named after another realm's gateway ID, enabling them to overwrite assets and establish SSH tunnels into the target realm's local network. The vulnerability has a low CVSS 4.0 base score of 2.1 and does not have known exploits in the wild.
Snipe-IT versions before 8.5.0 have a SAML assertion replay vulnerability that allows attackers to reuse captured assertions due to a non-atomic nonce check in the SAML ACS handler. This flaw enables attackers to send concurrent POST requests with a single captured assertion to create multiple authenticated sessions, bypassing identity provider revocation mechanisms.
Snipe-IT versions before 8.6.3 have a vulnerability where the software ignores the return value of ldap_start_tls() in the LDAP connection process. This allows an attacker positioned on the network path to force LDAP binds to occur in cleartext by responding with a protocol error to the StartTLS request. As a result, attackers can capture sensitive credentials including service-account credentials and end-user login passwords.
CVE-2026-116199 is a critical authentication bypass vulnerability in Snipe-IT versions before 8.6.3. The flaw exists in the GoogleAuthController::handleGoogleCallback method, which allows users to log in via Google SSO if their username matches the Google account email, without checking if the user is deactivated. This enables deactivated users with email-like usernames and active Google identities to regain access at their original permission levels, including administrative privileges.
Snipe-IT versions before 8.7.0 have a vulnerability where sensitive custom-field data can be stored unencrypted in the database if an authenticated API user without the appropriate permission creates assets. This occurs in the Api\AssetsController::store method, leading to plaintext storage of data that should be encrypted. The vulnerability exposes sensitive data through backups, replicas, or direct database access.
Edgeless Systems Contrast versions 1.21.0 up to but not including 1.25.0 have a flaw in the imagepuller component where wildcard registry configurations may be incorrectly preferred over exact domain matches. This can cause credentials or metadata intended for wildcard domains to be applied to specific registries, potentially leaking sensitive information. The vulnerability has a low severity score and requires local attacker privileges with high attack complexity to exploit.
phpMyFAQ versions before 4.1.10 have an object-level authorization bypass vulnerability. This flaw allows unauthenticated attackers to modify or delete visitor questions by providing arbitrary openQuestionID values to the POST /api/faq/create endpoint. Attackers who solve the CAPTCHA can rewrite question categories, forge answered entries in the faqquestion_history, or delete questions permanently if the records.enableDeleteQuestion setting is enabled.
phpMyFAQ versions before 4.1.10 have a server-side request forgery (SSRF) vulnerability in the PDF export feature. This flaw allows attackers who can control FAQ content to embed external image URLs that cause the server to make unintended requests, including to internal or loopback services. The server then includes the responses from these requests in generated PDFs.
vLLM versions from 0.20.1 up to but not including 0.29.0 have an improper input validation vulnerability. This flaw allows remote attackers to crash the engine by providing out-of-vocabulary stop_token_ids in OpenAI chat, completion, generate, or batch requests. The vulnerability can cause engine termination or memory corruption by writing outside the V2 runner's logits buffer.
vLLM versions from 0.8.5 up to but not including 0.31.0 contain a denial of service vulnerability due to the use of uninitialized resources in the logprobsTensors.empty_cpu() function and the V1 model runner. This flaw can cause the EngineCore to crash and drop all co-tenant requests when a client sends specially crafted prompt_logprobs or echo with logprobs against a cached prefix.
vLLM versions from 0.18.0 up to but not including 0.31.0 have a resource exhaustion vulnerability. This flaw allows API clients to bypass the frame-count limit for video/jpeg processing by manipulating the num_frames parameter. By setting num_frames to -1 with a large inline video, the VideoMediaIO.load_base64 function decodes every frame, leading to memory exhaustion and crashing the API frontend.
vLLM versions from 0.20.0 up to but not including 0.30.0 contain a denial of service vulnerability. This flaw allows remote attackers to crash the inference engine by sending malformed multimodal metadata to the /inference/v1/generate endpoint. The issue arises from improper input validation, specifically when replaying valid multimodal items with repeated or overlapping placeholders or mismatched data lists, leading to a negative text span in Qwen2.5-VL position construction that terminates the engine.
vLLM versions from 0.10.2 up to but not including 0.25.0 have an uncontrolled resource consumption vulnerability. This flaw allows unauthenticated attackers to cause memory exhaustion by submitting specially crafted decompression-bomb images to the /v1/chat/completions endpoint. The vulnerability arises because the Nemotron-VL processors globally set Image.MAX_IMAGE_PIXELS to None, disabling limits on image size and enabling denial of service via out-of-memory conditions.
vLLM versions from 0.9.2 up to but not including 0.24.0 contain a server-side request forgery (SSRF) vulnerability. This flaw allows API callers to embed a decoded address in the X-Request-Id header, forcing the server to make outbound connections to attacker-controlled hosts. Exploitation can lead to leakage of NCCL unique_id and KV-cache tensors or cause denial of service by blocking worker processes.
vLLM versions from 0.19.0 up to but not including 0.24.0 contain a decompression bomb vulnerability in the AudioMediaIO multimodal path. Authenticated attackers can send small compressed audio inputs that decompress to very large PCM data, exhausting server memory and potentially causing denial of service.
vLLM versions from 0.22.0 up to but not including 0.24.0 have an improper input validation vulnerability in the Rust gRPC Generate and GenerateStream services. This flaw allows attackers to submit out-of-vocabulary prompt token IDs, causing a fatal embedding lookup failure that terminates the EngineCore process and leaves the server in an unhealthy state.
vLLM versions from 0.22.0 up to but not including 0.24.0 contain a denial of service vulnerability. Remote attackers can exploit this by sending specially crafted Generate or GenerateStream requests with output_logprobs enabled and more than 128 output_candidates.token_ids. This triggers a fatal sampler exception in the Rust gRPC frontend, causing the EngineCore to crash and resulting in denial of service.
vLLM versions from 0.22.0 up to but not including 0.24.0 have an improper input validation vulnerability in the Rust gRPC converter. This flaw allows remote attackers to bypass max_logprobs limits by sending oversized or integer-wrapping top_n values in CandidateTokens.top_n. Exploiting this can cause torch.topk failures that terminate the EngineCore process.
SiYuan 3.5.4 before 3.8.7 on Windows contains a sensitive-path denylist bypass in IsSensitivePath because the Windows extended-length prefix (\\?\) survives filepath.Clean and matches no forbidden prefix. Authenticated API callers can prepend the prefix to localPath in /api/import/importStdMd to copy workspace conf files, including the API token and TLS private keys, into assets served to unauthenticated clients.