CVE-2026-99237 is a high-severity vulnerability in the Linux kernel version 6.16 involving improper locking in the tracing subsystem. The flaw occurs because trace_types_lock is not held when resetting last boot data from readers, leading to potential double freeing of memory and concurrent modification issues. This can cause serious integrity and availability problems in the kernel tracing functionality. The issue has been fixed in specific commits.
Cybercriminals exploit the popularity of ebooks by distributing malware disguised as ebook files, using search result manipulation, phishing scams, and fake pirate library sites. These attacks can lead to malware infections such as cryptocurrency miners and infostealers, data leaks including personal and financial information, and fraudulent charges via fake bookstore sites. E-readers themselves are less commonly targeted, but vulnerabilities exist in advanced models. Users' reading histories and personal data can also be exposed through data leaks or account compromises. Safe practices include using official bookstores, keeping devices and apps updated, and avoiding unofficial firmware.
CVE-2026-119050 is a critical unsafe reflection vulnerability in agno-agi's agno product up to version 3.1.11. It allows attackers to supply model-controlled function names to Python's getattr(), enabling invocation of arbitrary pandas functions. This can lead to code execution by calling pandas.read_pickle on attacker-controlled paths or reading local files via other pandas readers.
A critical vulnerability in the zip crate (<= 9.0.4) arises from inconsistent parsing of ZIP archive headers between two readers: ZipArchive uses the Central Directory File Header (CDFH) as authoritative, while ZipStreamReader relies on the Local File Header (LFH). This discrepancy allows an attacker to craft a ZIP archive with differing filenames in the headers, enabling security gateways to be bypassed and malicious files to be extracted, leading to arbitrary file overwrite and potential remote code execution.
MIME::Field::ParamVal versions before 5.521 for Perl do not properly flag duplicate boundary parameters when the parameter name contains a nested comment. This causes the parser to store such parameters under their literal names instead of the expected 'boundary' name, allowing a second boundary parameter to go undetected as a duplicate. As a result, MIME::Parser splits the message on the second boundary, while readers that skip comments per RFC 5322 take the first boundary. This discrepancy allows a remote sender to hide an attachment from filters relying on ambiguous_content(), although the recipient's mail client will display the attachment.
Apache Kafka's code-generated protocol readers pre-allocate array collections based on a declared element count that is only loosely validated against the request buffer size. This can lead to excessive heap allocation before elements are read, enabling an attacker to cause an OutOfMemoryError and crash the broker. The vulnerability affects all Kafka API types with array fields and occurs before authorization checks, allowing unauthenticated attackers on unauthenticated listeners to exploit it. Fixed in Apache Kafka versions 4.2.2, 4.3.2, and 4.4.0 by capping pre-allocation and rejecting excessively large array lengths.
Apache Kafka's flexible protocol version readers do not properly limit the count of tagged fields declared by the sender, allowing a client to specify an excessively large number of tagged fields in request headers. This can cause the broker to allocate a large number of objects, exhausting heap memory or causing significant garbage collection delays, resulting in denial of service. The issue affects the parsing of flexible request headers, including pre-authentication APIs, allowing exploitation without authentication. Fixed in Apache Kafka versions 4.2.2, 4.3.2, and 4.4.0 by adding bounds checks on the tagged-field count.
CVE-2026-116269 is a vulnerability in MIME::Field::ParamVal versions before 5.521 for Perl. It causes the recommended_filename() method to return an empty string when processing RFC 2231 filenames with hyphenated language tags, such as 'utf-8'en-US'. This occurs because the decoder fails to properly strip the language suffix when it is not a single word, leading to an empty recommended filename instead of the actual filename. This behavior differs from other mail readers that correctly return the filename. As a result, a remote sender can bypass file extension checks on the recommended filename, potentially allowing disallowed attachments to pass through security policies.
CVE-2026-116265 is a vulnerability in MIME::Field::ParamVal versions before 5.521 for Perl's MIME-tools. It involves ambiguous multipart boundary interpretation due to incomplete checks on RFC 2231 continuation parameters. This ambiguity allows a remote sender to craft a message that splits differently on the recipient's mail client compared to other mail readers, potentially hiding attachments from filters relying on ambiguous_content().
CVE-2026-99203 is a high-severity vulnerability in the Linux kernel related to pipe asynchronous notification handling. It involves improper preservation of existing fasync readers when a writer setup fails, leading to a use-after-free condition. This flaw can cause kernel memory corruption and potentially allow privilege escalation or denial of service. The issue has been fixed in several Linux kernel commits.