BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, a BACnet/SC peer can trigger a heap out-of-bounds read (up to 3 bytes), pre-authentication, in the BACnet/SC header-option decoder. bvlc_sc_decode_proprietary_option() reads the vendor-id and option-type at fixed offsets [3],[4],[5] before checking the option's declared header length, and the option-list validator never enforces a minimum length for proprietary options. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, there is a remote global-buffer-overflow in the official router-ipv6 application shipped with bacnet-stack, this results in an out-of-bounds write to the global transmit buffer under ASan. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, the bsc_node_parse_urls() function in src/bacnet/datalink/bsc/bsc-node.c contains three distinct bugs when parsing space-separated WebSocket URIs from a BACnet/SC Address Resolution ACK message. Two bugs cause out-of-bounds writes past the utf8_urls[10][129] array in the static BSC_ADDRESS_RESOLUTION structure. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0-rc2, a reachable out-of-bounds write exists when encoding the device.address-binding property. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0-rc2.
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. From versions 1.4.2 to before 1.4.5, and 1.5.0 to before 1.5.1, a signed fileStartPosition taken from AtomicReadFile and AtomicWriteFile stream-access requests is not validated tightly enough before it reaches the RAM file backends. Practical impact includes: reliable denial of service via process crash, out-of-bounds read that may expose adjacent memory contents, or out-of-bounds write that may corrupt heap memory and destabilize the process. This issue has been patched in versions 1.4.5 and 1.5.1.
A reflected Cross-site Scripting (XSS) vulnerability exists in the Dimitri Grassi Salon booking system up to version 10.31.14. This vulnerability arises from improper neutralization of input during web page generation, allowing an attacker to inject malicious scripts that execute in the context of a victim's browser. The vulnerability has a high severity score of 7.1 (CVSS 3.1) and impacts confidentiality, integrity, and availability.
The AVRCP browsing channel's L2CAP receive-buffer callback, browsing_avrcp_l2cap_alloc_buf() in subsys/bluetooth/host/classic/avrcp.c, allocated from the shared avctp_browsing_rx_pool with K_FOREVER. L2CAP invokes that callback from the Bluetooth RX work queue thread (bt_workq, "BT RX WQ"), both for the head buffer of a new SDU and — through l2cap_br_alloc_frag() and net_buf_append_bytes() — for every further fragment of a reassembled SDU. That same thread is the only context that ever releases these buffers, after bt_l2cap_br_recv_seg() delivers a completed SDU and calls net_buf_unref(), so a wait taken there can never be satisfied.
The pool holds CONFIG_BT_MAX_CONN + 1 buffers of CONFIG_BT_AVRCP_BROWSING_L2CAP_MTU bytes (two buffers of 339 bytes in the default configuration). A connected browsing peer can drain it because bt_l2cap_br_recv_seg() in subsys/bluetooth/host/classic/l2cap_br.c accepts the SDU length declared in an SAR_START segment without bounding it by br_chan->rx.mtu: a peer that announces a large SDU and then streams continuation segments forces one pool buffer per segment-worth of data. Once the pool is empty the next allocation blocks forever inside the callback.
Triggering the flaw requires a build with CONFIG_BT_CLASSIC and the experimental CONFIG_BT_AVRCP_BROWSING option, an application that registers AVRCP callbacks, and a BR/EDR peer that has established the AVRCP control channel and then the browsing channel, which requires an encrypted (paired) link. No malformed packet is needed — a few hundred bytes of ordinary segmented L2CAP traffic suffice.
The consequence is a permanent hang of the whole Bluetooth host, not just of AVRCP: the blocked thread drains bt_dev.rx_queue for all HCI ACL data and low-priority events and also runs the host's internal work items, so all connections stop being serviced and the state is unrecoverable without a reboot. There is no memory-corruption or information-disclosure component. The fix allocates with K_NO_WAIT, so an empty pool now yields a local-busy indication or a channel disconnect that the application can recover from.
This security update for the zbar library addresses two vulnerabilities: an undefined behavior issue in the Code 128 decode6() function (CVE-2026-88371) and a 1-byte heap buffer overflow write in Structured-Append QR text extraction (CVE-2026-95516). Both issues could potentially lead to memory corruption. The update fixes these vulnerabilities to prevent such undefined behavior and buffer overflow conditions.
An unbounded decompression vulnerability exists in actix-http before 3.20.1 and actix-web before 4.18.2 in the encoding::Decoder component. This flaw allows remote attackers to exhaust server memory and CPU resources by sending small, highly compressed request bodies using gzip, deflate, Brotli, or zstd compression. The vulnerability affects various extractors such as Json, Form, Bytes, or String, as well as awc clients, potentially causing denial of service.
FrankenPHP standalone static binaries from version 1.8.0 up to but not including 1.13.2 include a statically linked PHP brotli extension with Brotli 1.2.0. This version of Brotli contains an out-of-bounds write vulnerability (CVE-2026-111497) in its decoder. Unauthenticated remote attackers can exploit this by sending crafted data to applications that use brotli_uncompress_add(), potentially causing the FrankenPHP process to crash and possibly leading to memory disclosure or code execution.
Addressable URI normalization in krane versions starting from 2.2.5 up to 2.9.0 incorrectly resolves some paths containing '..' segments, deviating from RFC 3986. This causes paths that should be normalized above the root to be incorrectly resolved, potentially allowing path traversal past allowlist checks. The issue is fixed in version 2.9.1 by aligning normalization with RFC 3986. Applications that use Addressable's normalization for access control but send the original URI to other resolvers may be vulnerable. Workarounds include rejecting paths with '..' segments or using consistent normalization for checks and requests.
Multiple security vulnerabilities were discovered in the Linux kernel (linux-fips), affecting several subsystems including x86 architecture, hardware monitoring drivers, OCFS2 file system, IPv4 networking, Ethernet bridge, Netfilter, and XFRM subsystem. These vulnerabilities could potentially allow an attacker to compromise the system. A security update correcting these flaws is available and requires a system reboot and recompilation of third-party kernel modules due to ABI changes.
This vulnerability exists in the eMudhra emBridge due to missing authorization checks in the FileBrowser API endpoints. These endpoints perform file system enumeration using the LocalSystem account without adequately validating the requesting caller's authorization. An unauthenticated attacker on the same LAN could exploit this vulnerability by sending malicious webpage to the local HTTPS Web API.
Successful exploitation of this vulnerability could allow the attacker to enumerate file and directory names and obtain information about the directory structure of the targeted system.
The vulnerability however, does not provide access to file contents or permit file modification, deletion, or code execution, or access to cryptographic keys and hardware token PINs.
CVE-2026-126192 describes a performance-related vulnerability in Soup Sieve when using a CSS selector with a general sibling combinator inside :has(), such as div:has(a ~ b). This selector runs in quadratic time relative to the number of sibling elements, causing significant CPU delays when processing untrusted HTML with many siblings. The issue arises because the implementation performs nested scans without short-circuiting when the right-hand sibling is absent. This can stall applications that evaluate such selectors on attacker-controlled HTML. The vulnerability affects Soup Sieve versions from 1.1.0.2090 up to but not including 3.0.2_1. A fix is available in version 3.0.2_1. Mitigations include careful use of :has() selectors, avoiding anchors with many children, and restricting inner selectors to combinators like > or + to limit traversal.
A memory denial-of-service vulnerability exists in Pillow's TIFF and EXIF IFD parsing due to overlapping tag data. Crafted image files can cause Pillow to consume thousands of times their size in memory during parsing, leading to process crashes or stalls. This affects TIFF, JPEG, PNG, WebP, and MPO images. The flaw has existed since Pillow 1.0 and involves unbounded memory allocation when reading tag data offsets that overlap or cover the entire file.
SiYuan from 3.6.0 before 3.8.9 contains an information disclosure vulnerability that allows unauthenticated publish visitors to bypass per-document passwords via regex search in getDoc. Attackers can send POST requests to /api/filetree/getDoc with queryMethod 3 and a broad regex to read protected body text returned in the unfiltered keywords field.
NLTK before 3.10.4 contains a denial of service vulnerability in the CCG lexicon parser fromstring that allows remote attackers to exhaust CPU by supplying wide inputs. Attackers can submit lexicon text with long flat bracket bodies or operator chains, triggering quadratic string re-slicing in matchBrackets and augParseCategory that blocks worker threads.