A critical SQL Injection vulnerability (CVE-2026-111852) exists in WPdreams Ajax Search Lite plugin versions up to 4.14.6. This vulnerability allows an unauthenticated attacker to perform blind SQL injection attacks, potentially leading to high confidentiality impact and partial denial of service.
A use-after-free vulnerability exists in the gf_filter_packet_destroy function of GPAC Project's MP4Box before version 2.5. This flaw can be triggered by supplying a crafted MPEG-2 file, leading to a Denial of Service (DoS) condition.
A NULL pointer dereference vulnerability exists in the StatSFVec2f function of GPAC Project's MP4Box before version 2.5. This flaw allows attackers to cause a Denial of Service (DoS) by supplying a specially crafted MPEG-4 file.
An out-of-bounds read vulnerability exists in the function gf_odf_ac4_cfg_dsi_v1 within the GPAC Project's MP4Box component prior to version 26.07.0. This flaw can be triggered by processing a specially crafted AC4 file, leading to a denial of service (DoS) condition. No CVSS score is provided, and no known exploits are reported in the wild. The vulnerability affects versions before 26.07.0 of MP4Box.
A NULL pointer dereference vulnerability exists in the dasher_insert_timeline_entry function of GPAC Project/MP4Box versions before 2.5. This flaw can be triggered by supplying a crafted MP4 file, resulting in a denial of service (DoS) condition.
A vulnerability in the dhikshitha29 Insurance-Management-System affects the Policy Holder Update Form component, specifically the file /Agent/includes/UpdatePolicyHolder-inc.php. The flaw involves improper authorization due to manipulation of the Policy_no argument, allowing remote attackers to exploit it. The vulnerability has a CVSS score of 7.3 (medium severity). The project uses rolling releases, so specific affected or fixed versions are not available. The issue was reported early, but no response or patch has been provided yet. Public exploit code is available.
CVE-2024-5563 describes a vulnerability where reCaptcha is not applied to certain authentication flows despite being enabled. This incomplete implementation allows attackers to bypass reCaptcha protections. Successful brute force attacks exploiting this flaw can lead to unauthorized access to user accounts and sensitive information. The vulnerability has a medium severity rating with a CVSS score of 4.8.
Apache bRPC versions prior to 1.18.0 contain vulnerabilities that allow remote attackers to control file paths and cause uncontrolled resource consumption via builtin services. Attackers can create directories and overwrite files with server process privileges by manipulating runtime flags. Additionally, the profiling service can be abused to hold CPU profiling resources for extended periods, causing denial of service.
A NULL pointer dereference vulnerability exists in the RTMP protocol implementation of Apache bRPC versions prior to 1.18.0. This flaw allows remote attackers to cause a denial of service by crashing the server when a crafted createStream command is sent and the client closes the connection prematurely.
Apache bRPC versions prior to 1.18.0 have an interpretation conflict in their HTTP protocol implementation that allows remote attackers to bypass access control rules enforced by a front proxy. This occurs because the bRPC server collapses consecutive slashes in request paths, treating paths with empty segments as equivalent to their collapsed form, contrary to RFC 3986. Additionally, the HTTP/2 implementation does not properly validate the :path pseudo-header, allowing malformed requests to be accepted. This vulnerability affects deployments where bRPC is behind a front proxy that enforces access control on literal paths but forwards requests to bRPC, enabling attackers to reach restricted resources. The issue is fixed in bRPC version 1.18.0.
A use-after-free vulnerability exists in the RTMP protocol implementation of Apache bRPC versions prior to 1.18.0. This flaw occurs when a malicious RTMP peer sends a crafted Abort message that targets a chunk stream concurrently used for sending data, causing the process to crash or potentially corrupt memory. The issue arises due to unsynchronized deletion of an RtmpChunkStream object while it is still in use by sender threads. This affects any application using the bRPC RTMP protocol implementation as a client or server with untrusted remote endpoints.
Apache bRPC versions prior to 1.18.0 have an improper authorization vulnerability that allows remote attackers to access builtin services through the public port. This occurs because protobuf-based protocol dispatch paths do not enforce the security_mode flag, enabling unauthorized invocation of builtin services intended only for internal access. This can lead to disclosure of sensitive runtime information such as metrics, flags, and profiler data. The issue affects any deployment where the public port is reachable from untrusted networks and protobuf-based protocols are enabled alongside ServerOptions.internal_port configuration.
Apache bRPC versions prior to 1.18.0 contain an HTTP request/response smuggling vulnerability due to inconsistent parsing of HTTP/1.1 headers. This allows remote attackers to desynchronize the bRPC parser from front-end proxies or load balancers, enabling request smuggling and header injection such as forged Authorization or X-Forwarded-For headers. The issue arises from bRPC accepting obsolete or non-standard header forms that front-ends reject or interpret differently. The vulnerability is fixed in bRPC version 1.18.0.
A vulnerability in BIND resolver allows specially crafted inbound DNS messages with a particular structure to cause excessive CPU and memory consumption. This affects multiple BIND 9 versions and can lead to denial of service due to resource exhaustion. The issue is identified as CVE-2026-19630 with a high severity rating.
A data race vulnerability exists in the RDMA transport of Apache bRPC versions prior to 1.18.0. This flaw allows a remote, unauthenticated client to cause a denial of service by crashing the server process when RDMA support is enabled both at build time and runtime. The issue arises from unsynchronized access to shared input buffers and parser state between TCP and RDMA message processing during the handshake and subsequent communication.
Apache bRPC versions prior to 1.18.0 contain an uncontrolled recursion vulnerability in the mcpack2pb component. This flaw allows remote attackers to crash the server by sending deeply nested mcpack data. The parser recursively processes nested objects and arrays without a depth limit, leading to stack overflow and process crash. The issue affects bRPC servers handling nshead_mcpack, ubrpc, or public_pbrpc requests with recursive protobuf schemas. The vulnerability is fixed in version 1.18.0 by enforcing a maximum parsing depth of 128 levels.
A missing authorization vulnerability exists in Magepeople inc.'s WpTravelly tour-booking-manager plugin, affecting versions up to 2.3.5. This flaw allows unauthorized users to exploit incorrectly configured access control security levels. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a medium severity level. No known exploits are reported in the wild, and no official patch or remediation guidance is currently provided.
A security vulnerability (CVE-2026-114248) exists in the dhikshitha29 Insurance-Management-System affecting the Plan Management Form component. The vulnerability involves manipulation of the submit, Plan_no, and Name arguments in the /Admin/includes/AddNewPlan-inc.php file, leading to missing authentication. This flaw can be exploited remotely. The vulnerability has a medium severity with a CVSS score of 5.3. The project uses a rolling release model, so no specific affected or fixed versions are available. The issue was reported early but has not yet received a response or patch from the vendor. Public exploit details have been disclosed but no known exploitation in the wild has been confirmed.
The npm package 'peptide-modify' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, uncompromised machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
CVE-2026-113791 is a medium severity vulnerability in the py-pdf pypdf library prior to version 6.21.0. It involves uncontrolled resource consumption where an attacker can craft a PDF with many small operations in a content stream, causing excessive memory usage during parsing. This issue has been fixed in version 6.21.0.