A vulnerability in web-token jwt-framework and jwt-experimental prior to versions 3.4.10, 4.0.7, and 4.1.7 allows attackers to modify the encrypted content encryption key without detection due to a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm. This flaw discards the Poly1305 authentication tag during encryption and omits it during decryption, weakening the cryptographic protection of the key.
CVE-2026-134461 is a high-severity vulnerability in the web-token jwt-library affecting versions before 3.4.10, 4.0.7, and 4.1.7. It involves uncontrolled resource consumption in the PBES2AESKW::unwrapKey() function, where an attacker can specify an excessively large iteration count in the p2c JWE header, causing lengthy PBKDF2 computations that exhaust server CPU resources. This vulnerability allows unauthenticated attackers to perform denial-of-service attacks by sending specially crafted JSON Web Encryption (JWE) tokens.
CVE-2026-133985 is a high-severity vulnerability in TRENDnet TEW-657BRM version 1.00.1 involving an out-of-bounds read in the /usr/sbin/restore_config.cgi file. The flaw can be exploited remotely without user interaction and requires low attack complexity and privileges. The product is end-of-life and no official patch or fix is available. The vendor has not confirmed the vulnerability but plans to notify customers. Exploit code has been published.
Red Hat has issued a critical security advisory for PHP 7.4 on Red Hat Enterprise Linux 8, addressing multiple vulnerabilities including out-of-bounds read/write, use-after-free, remote code execution, local privilege escalation, request smuggling, cross-site scripting, signature bypass, information disclosure, and denial of service. These vulnerabilities affect various PHP components such as PHP-CGI, PHP-FPM, PHAR, SOAP, and session handling. The update backports security fixes from PHP 8.2.36 to 7.4 and is available for multiple Red Hat Enterprise Linux 8 architectures.
A vulnerability in eigent-ai eigent versions up to 1.0.2 allows remote attackers to bypass authentication in the Local Agent Control API component. This issue affects an unknown functionality in the chat_controller.py file. The vulnerability is fixed in version 1.0.3.
CVE-2025-61963 is a high-severity vulnerability in the AmdPlatformRasSmm driver caused by improper input validation. An attacker with privileged access could exploit this flaw to overwrite SMRAM, potentially leading to arbitrary code execution. No patch information is currently available, and no known exploits are reported in the wild.
CVE-2026-28235 is a vulnerability in the AMD RAID Configuration Driver where improper address validation could allow an attacker with administrative privileges to read arbitrary kernel memory. This may lead to loss of confidentiality of sensitive information stored in kernel memory. The vulnerability requires administrative access and does not involve user interaction.
CVE-2026-0462 describes an insufficient granularity of access control vulnerability in AMD Secure Encrypted Virtualization (SEV) firmware. This flaw could allow a malicious hypervisor to redirect accesses to MMIO memory, potentially compromising the integrity of guest memory. The vulnerability has a medium severity rating with a CVSS score of 5.9. No patch or remediation information is provided, and no known exploits are reported in the wild.
This vulnerability involves incomplete cleanup during VMRUN error handling in Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) environments. It could allow unauthorized access to guest register state, potentially leading to information disclosure and confidentiality impacts. The issue has a medium severity rating with a CVSS score of 4.6. No affected versions or patches are specified, and there are no known exploits in the wild.
A vulnerability exists in the SDO Information Get Object Description and Get Entry Description responses where the object or entry name is copied into a mailbox data buffer without sufficient space for a null terminator. This causes the null terminator byte to be written one byte beyond the buffer's end when the name exactly fills the buffer, resulting in a buffer overflow condition.
This vulnerability involves an object dictionary entry that can have write-access flags despite having a NULL data pointer. Specifically, when a constant value is stored directly in the value field rather than in addressable storage, the CoE SDO download handler fails to verify the presence of storage before writing. This results in the handler writing the master-supplied payload through a NULL pointer, causing an availability impact.
This vulnerability involves the CoE entry gate accepting frames with a mailbox header length smaller than required for a normal SDO Download. Specifically, it accepts lengths as low as 8 bytes, while a proper SDO Download requires at least 10 bytes. This discrepancy causes a miscalculation in the segmented-transfer logic due to unsigned integer wrap, resulting in an unchecked declared SDO size. Consequently, the system reads beyond the actual payload boundary, potentially leading to out-of-bounds memory reads.
CVE-2026-129809 is a vulnerability involving a NULL pointer dereference in the ESC_foeprocess handler. This occurs when an incoming mailbox frame is processed before the application has called FOE_config to initialize necessary file table and buffer pointers. If these pointers are NULL, the handler dereferences them, leading to a crash or denial of service.
CVE-2026-129806 describes a vulnerability in the CoE SDO upload handler where a NULL pointer dereference can occur. This happens when the handler processes entries holding a constant in the value field, which have their data set to NULL. A master requesting such an entry triggers the NULL pointer dereference in the upload path, potentially causing a denial of service.
CVE-2026-129801 is a vulnerability in the FoE DATA frame handler where the payload length is derived from a master-supplied mailbox length field without proper bounds checking against the physical mailbox buffer size. This can lead to reading beyond the buffer when a master declares a large length but sends a shorter frame.
CVE-2026-129810 is a vulnerability involving NULL pointer dereferences in the ESC_eoeprocess and ESC_eoeprocess_tx functions. These functions can be invoked before the application initializes the callback table pointer via EOE_config, leading to dereferencing a NULL pointer during processing of incoming EoE frames and transmit polling cycles. This results in a denial of service due to application crashes.
CVE-2026-129808 describes a vulnerability in the EoE receive and transmit paths where optional callback functions handle_recv_buffer and fetch_send_buffer are called without checking if they are set. If an application omits either callback, this results in a call through a NULL function pointer when processing EoE frames or during transmit polling, causing a denial of service.
The vulnerability involves the sizeOfPDO function, which during state transitions uses the subindex-0 count of SM-assign and PDO-mapping objects as loop bounds without validating these counts against the actual descriptor array sizes. If these subindex-0 values are writable via SDO, a malicious master can write a value of 0xFF, causing sizeOfPDO to read beyond the end of the descriptor arrays during the next transition to SAFEOP.
CVE-2026-129807 describes a vulnerability in the FoE file table where entries can omit a write handler by setting write_function to NULL, making the file read-only. The FOE_fopen function did not verify the presence of a write handler before processing write requests, leading to a NULL pointer dereference when a write request (WRQ) was sent for a read-only file.
CVE-2026-129811 is a vulnerability where the PDO mapping bit lengths in mapping objects can be overwritten by a master via SDO. This allows crafting of mappings with total bit counts exceeding the allocated process data buffers, leading to out-of-bounds writes during process data cycles after the PREOP to SAFEOP transition. The flaw can result in high impact including confidentiality, integrity, and availability compromise.