Improper Validation of Specified Quantity in Input vulnerability in Magepeople inc. Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows Removing Important Client Functionality.This issue affects Booking and Rental Manager: from n/a through 2.8.0.
CVE-2026-24715 is a medium severity vulnerability in QNAP Systems Inc. QuRouter involving an observable timing discrepancy (CWE-208). This flaw could allow remote attackers to obtain sensitive data. The issue affects QuRouter versions from 2.7.0 up to but not including 2.7.2.113. The vulnerability has been fixed in QuRouter version 2.7.2.113 and later.
CVE-2026-107425 is a missing authorization vulnerability in Magepeople inc.'s Bus Ticket Booking with Seat Reservation software. It affects versions from the initial release up to 5.9.7. The flaw allows attackers to exploit incorrectly configured access control security levels, potentially leading to unauthorized actions that impact integrity and availability. The vulnerability has a CVSS score of 6.5, indicating a medium severity level.
CVE-2026-110458 is a low severity path traversal vulnerability in Ubiquiti Inc's UniFi Protect AI Key. An attacker with network access could exploit this flaw under certain conditions to create or truncate files on the affected device. No known exploits are reported in the wild. The vulnerability affects versions from 0 up to but not including 2.2.8.
CVE-2026-110457 is a path traversal vulnerability in Ubiquiti Inc's UniFi Protect AI Key. An attacker with network access and under certain conditions could exploit this flaw to read information about files on the device. The vulnerability has a low severity score of 3.7 and does not allow modification or denial of service. Affected versions are those prior to 2.2.8. No known exploits or patches are currently reported.
CVE-2026-13138 is a high-severity vulnerability in the Biletiva Ticketing Platform by Divasoft Software and E-Commerce Inc. It involves client-side enforcement of security controls that should be handled server-side, allowing manipulation of application state. The vulnerability affects versions up to and including 2026-07-23. It has a CVSS 3.1 score of 8.6, indicating a significant risk. No patch or remediation details are provided, and no known exploits are reported in the wild.
CVE-2026-104355 is a high-severity authorization vulnerability in Temporal Technologies, Inc.'s Temporal Server affecting multi-cluster deployments. A connected peer cluster can modify local namespaces on another cluster without proper authorization because the receiving cluster applies inbound namespace replication updates without verifying if the namespace is global. This allows a compromised or malicious peer to overwrite namespace metadata such as state, description, retention, and active cluster settings, potentially disrupting workflow operations. Clusters without remote clusters registered with connection enabled are not affected.
LibreNMS versions through 26.9.1.1 have an authorization bypass vulnerability in the SmokePing graph authorization logic. The flaw occurs because the code checks the source probe device rather than the actual target device, allowing restricted users on a probe device to access latency graphs for arbitrary devices. This enables unauthorized viewing of latency data and enumeration of device names.
Crux Agent from 1.9.0 before 2.0.3 uses the full SKA bilocation key as the WireGuard preshared key. When a peering session negotiates use of SHA-512, the key produced is 64 bytes instead of the 32 bytes WireGuard requires. The agent does not validate this size; instead it attempts to use the `wg set` command to update the live tunnel, and write the invalid key to the WireGuard configuration file. The update fails, so the live tunnel keeps using its previous preshared key until the tunnel is shut down. The tunnel will fail to start when restarted.
For a peer which has never successfully negotiated a 32-byte bilocation key in a Crux C2 organization which has the "Enforce SKA Use" setting turned off, no preshared key will be set for the tunnel. Therefore, an attacker who is able to intercept and store the peer's traffic, and has access (or will have access) to a cryptographically relevant quantum computer, will be able to decrypt the tunnel.
CVE-2026-95589 is a missing authorization vulnerability in Magepeople inc.'s Deposits and Partial Payments for WooCommerce plugin. It affects versions from initial release up to but not including 4.0.12. The flaw allows attackers with limited privileges to exploit incorrectly configured access control, potentially leading to unauthorized actions. The vulnerability has a medium severity with a CVSS score of 6.5.
CVE-2026-71884 is a vulnerability in Legion of the Bouncy Castle Inc.'s BC-LTS-JAVA library versions 2.73.4 up to but not including 2.73.13. The native one-shot CTR packet cipher implementation did not validate that the input length fit within the counter space derived from the IV, causing the counter to wrap and the keystream to repeat. This results in two segments of the ciphertext being encrypted under the same keystream, allowing plaintext recovery without the key. The issue affects the native one-shot path only; other implementations validate the counter range properly. The vulnerability has a high severity with a CVSS 4.0 score of 8.2.
FortiBleed is an ongoing global campaign targeting internet-facing Fortinet FortiGate firewalls and SSL VPN gateways. It exploits reused or leaked credentials and legacy SHA-256 password storage to harvest and crack authentication data at scale. Attackers scan for exposed SSL VPN portals, perform credential stuffing and password spraying, and crack stolen password hashes offline. After gaining access, they create new administrative accounts for persistence and conduct Active Directory enumeration to expand access. Organizations may experience account lockouts due to attacker actions. The campaign acts as an initial-access broker with links to ransomware affiliates INC/Lynx and Payload, representing a significant medium-severity threat requiring immediate defensive measures.
src/internal.c in wolfSSL wolfSSH through 1.5.0 admits the server-to-client Diffie-Hellman group exchange messages SSH_MSG_KEX_DH_GEX_GROUP (31) and SSH_MSG_KEX_DH_GEX_REPLY (33) when a server receives them from an unauthenticated client. IsMessageAllowedServer() applies no direction check to the key exchange message range: when the peer is keying and no particular message is expected, which is the state a server is in for the whole window after it processes the client's KEXINIT because nothing sets handshake->expectMsgId there, the function falls out of its expectation branch without a verdict and reaches a numeric bound that admits every message id from 30 through 34. A client that negotiates diffie-hellman-group-exchange-sha256 and then sends message 31 makes the server run the client-side handler DoKexDhGexGroup(), which validates the attacker-supplied group with two 8-round Miller-Rabin primality tests, one on p and one on (p-1)/2, on a value of up to 8192 bits. The handler then returns success: the server stores the attacker's prime and generator, generates a Diffie-Hellman key pair in the attacker's group, and sends the client-role message SSH_MSG_KEX_DH_GEX_INIT (32) back to the attacker. Published RFC 3526 safe primes are the worst-case input and cost the attacker nothing to obtain. The primality validation was added in 1.5.0; versions from 1.2.0 through 1.4.22 admit the same message and enter the same client-role path without the primality cost. Message 33 is admitted as well, but on a server it is rejected before any cryptography because no public key check callback is registered, so it carries no comparable cost. Builds that define WOLFSSH_NO_DH_GEX_SHA256, which is implied by WOLFSSH_NO_DH or NO_SHA256, are unaffected.
Unsigned integer underflow in wstrncat() in src/port.c in wolfSSL wolfSSH from v1.4.11 through v1.5.0 on non-Windows platforms allows an authenticated remote attacker to write one out-of-bounds null byte past the end of a stack buffer by sending a crafted SFTP path. wolfSSH_RealPath() in src/ssh.c appends each path component with a remaining-size bound (outSz - curSz) rather than the full destination size, so once the accumulated path reaches half the output buffer the size_t computation n - strlen(s1) - 1 wraps to near SIZE_MAX. The strncat() call is then effectively unbounded and copies the whole component; when that component exactly fills the remainder of the buffer, its terminating null is written one byte past the end. The caller's own length check keeps the copied data inside the buffer, so the overflow is limited to that single null byte, which may corrupt an adjacent stack value and crash the process. Applications that call the public wolfSSH_RealPath() with an output buffer smaller than the input path are additionally exposed to an unbounded copy, because the word32 expression outSz - segSz in that length check also wraps.
wolfSSH does not validate that the ECDSA curve identifier in a KEXDH_REPLY host key blob matches the algorithm negotiated during key exchange. In ParseECCPubKey() (src/internal.c), the blob's algorithm string is used to derive the curve via NameToId/wcPrimeForId without checking against the negotiated ssh->handshake->pubKeyId, and the RFC 5656 curve identifier string is discarded via GetSkip() rather than compared. An active network man-in-the-middle attacker can substitute a host key blob containing a different ECDSA curve, causing the client to import the key on the wrong curve. Because the attacker controls the private key for the substituted curve, signature verification passes. Exploitation requires an active MitM position and a lax public key check callback (e.g., TOFU, algorithm-name-only check, or fingerprint match against the parsed key).
TP-Link Tapo
C500 v2.0 contains an out-of-bounds stack write vulnerability in its ONVIF PTZ
SOAP handlers. An authenticated ONVIF client can submit an excessive number of
preset-related elements, causing writes beyond the bounds of fixed-size stack
arrays and resulting in a crash of the affected service.
Successful
exploitation may allow an authenticated attacker to cause the affected service
to crash, resulting in a denial-of-service condition. Repeated exploitation may
repeatedly disrupt camera management and PTZ-related functionality until the
service recovers or restarts.
TP-Link Tapo
C500 v2.0 contains an out-of-bounds function-pointer dispatch in its TDP
(TP-Link Device Protocol) daemon. A single unauthenticated UDP datagram can
cause an invalid indirect call, crashing the main service and resulting in a
denial-of-service condition.
Successful
exploitation may allow an unauthenticated attacker with network access to the
affected UDP service to repeatedly crash the TDP daemon, disrupting normal
device operation and availability. No authentication, session establishment, or
pairing is required to trigger the condition.
CVE-2026-25269 is a medium severity vulnerability in Qualcomm Snapdragon products involving an out-of-bounds write due to memory corruption when processing camera requests with excessive batch and IO buffer configurations. This flaw can lead to high impact on confidentiality, integrity, and availability. The vulnerability affects multiple specific Snapdragon versions. No patch information is provided, and no known exploits are reported in the wild.
CVE-2026-25267 is a high-severity vulnerability in Qualcomm Snapdragon products where a missing authorization check allows a non-secure loader to rewrite page tables before secure memory initialization, leading to memory corruption. This flaw affects a wide range of specific Snapdragon hardware versions. The vulnerability has a CVSS 3.1 base score of 7.8, indicating significant impact on confidentiality, integrity, and availability. There is no information about available patches or vendor advisories. No known exploits are reported in the wild.