Subscribe, build a custom feed, or pitch a sponsorship at hello@acadenix.com
Latest intel// live feed
CVE-2026-43384 — Linux: In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: Fix MAC comparison
In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43383 — Linux: In the Linux kernel, the following vulnerability has been resolved: net/tcp-md5: Fix MAC comparison
In the Linux kernel, the following vulnerability has been resolved: net/tcp-md5: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this. CVSSv3.1 9.4 (CRITICAL)
CVE-2026-43379 — Linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close() opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is being accessed after rcu_read_unlock() has been called. This creates a race condition where the memory could be freed by a concurrent writer between the unlock and the subsequent pointer dereferences (opinfo->is_lease, etc.), leading to a use-after-free. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43378 — Linux Linux_kernel: In the Linux kernel, the following vulnerability has been resolved: smb: server: fix use-after-free
In the Linux kernel, the following vulnerability has been resolved: smb: server: fix use-after-free in smb2_open() The opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is dereferenced after rcu_read_unlock(), creating a use-after-free window. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43377 — Linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: Don't log keys
In the Linux kernel, the following vulnerability has been resolved: ksmbd: Don't log keys in SMB3 signing and encryption key generation When KSMBD_DEBUG_AUTH logging is enabled, generate_smb3signingkey() and generate_smb3encryptionkey() log the session, signing, encryption, and decryption key bytes. Remove the logs to avoid exposing credentials. CVSSv3.1 8.1 (HIGH)
CVE-2026-43376 — Linux: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free by
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free by using call_rcu() for oplock_info ksmbd currently frees oplock_info immediately using kfree(), even though it is accessed under RCU read-side critical sections in places like opinfo_get() and proc_show_files(). Since there is no RCU grace period delay between nullifying the pointer and freeing the memory, a reader can still access oplock_info structure after it has been freed. T CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43365 — Linux: This leads to corrupt logs and unmountable filesystems in generic/617 on a disk with
In the Linux kernel, the following vulnerability has been resolved: xfs: fix undersized l_iclog_roundoff values If the superblock doesn't list a log stripe unit, we set the incore log roundoff value to 512. This leads to corrupt logs and unmountable filesystems in generic/617 on a disk with 4k physical sectors... XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Torn write (CRC failure) detected at log block 0x318e. Truncating head block CVSSv3.1 8.2 (HIGH)
CVE-2026-43362 — Linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix in-place
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix in-place encryption corruption in SMB2_write() SMB2_write() places write payload in iov[1..n] as part of rq_iov. smb3_init_transform_rq() pointer-shares rq_iov, so crypt_message() encrypts iov[1] in-place, replacing the original plaintext with ciphertext. On a replayable error, the retry sends the same iov[1] which now contains ciphertext instead of the original data, resulting in corruptio CVSSv3.1 8.1 (HIGH)
CVE-2026-41588 — RELATE: Prior to commit 2f68e16, there is a timing attack vulnerability in course/auth.py — check_sign_in_key().
RELATE is a web-based courseware package. Prior to commit 2f68e16, there is a timing attack vulnerability in course/auth.py — check_sign_in_key(). This issue has been patched via commit 2f68e16. CVSSv3.1 9.0 (CRITICAL)
CVE-2026-41583 — Zfnd Zebra-script: Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade. Zebra nodes could thus accept and eventually mine a block that would be considered invalid by zcashd nodes, creating a consensus split between Zebra and zcashd nodes. In a s CVSSv3.1 9.1 (CRITICAL)
CVE-2026-41574 — Nhost Nhost\/auth: Prior to version 0.49.1, Nhost automatically links an incoming OAuth identity to an existing
Nhost is an open source Firebase alternative with GraphQL. Prior to version 0.49.1, Nhost automatically links an incoming OAuth identity to an existing Nhost account when the email addresses match. This is only safe when the email has been verified by the OAuth provider. Nhost's controller trusts a profile.EmailVerified boolean that is set by each provider adapter. The vulnerability is that several provider adapters do not correctly populate this field they either silently dr CVSSv3.1 9.8 (CRITICAL)
CVE-2026-41524 — Brave: Prior to commit 6c56603, page and article body content entered through the CKEditor rich-text
Brave CMS is an open-source CMS. Prior to commit 6c56603, page and article body content entered through the CKEditor rich-text editor is stored verbatim in the database and subsequently rendered with Laravel Blade's unescaped output directive {!! !!}. Any JavaScript or HTML injected by an editor-role user is permanently stored and executed in every visitor's browser upon page load. This issue has been patched via commit 6c56603. CVSSv3.1 8.7 (HIGH)
CVE-2026-37431 — Beauty: Parlour Management System v1.1 was discovered to contain a SQL injection vulnerability via
Beauty Parlour Management System v1.1 was discovered to contain a SQL injection vulnerability via the aptnumber parameter in the /appointment-detail.php endpoint. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-44339 — PraisonAI: Prior to praisonai version 4.6.37 and praisonaiagents version 1.6.37, praisonaiagents resolves unresolved tool names
PraisonAI is a multi-agent teams system. Prior to praisonai version 4.6.37 and praisonaiagents version 1.6.37, praisonaiagents resolves unresolved tool names against module globals and __main__ after it fails to match the declared tool list and the registry. With the default agent configuration, _perm_allow is None, so undeclared non-dangerous tool names are not rejected by the permission gate. An attacker who can influence tool-call names can therefore invoke unintended appl CVSSv3.1 8.6 (HIGH)
CVE-2026-44336 — Praison Praisonai: Dropping a Python .pth file into the user site-packages directory escalates this primitive to
PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI's MCP (Model Context Protocol) server (praisonai mcp serve) registers four file-handling tools by default — praisonai.rules.create, praisonai.rules.show, praisonai.rules.delete, and praisonai.workflow.show. Each accepts a path or filename string from MCP tools/call arguments and joins it onto ~/.praison/rules/ (or, for workflow.show, accepts an absolute path) with no containment check. The JSON-RPC di CVSSv3.1 9.6 (CRITICAL)
CVE-2026-44335 — Praison Praisonaiagents: Prior to version 1.6.32, the URL checking logic in PraisonAI has a logical flaw
PraisonAI is a multi-agent teams system. Prior to version 1.6.32, the URL checking logic in PraisonAI has a logical flaw that could be bypassed by attackers, leading to SSRF attacks. This issue has been patched in version 1.6.32. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-44334 — PraisonAI: From version 4.5.139 to before version 4.6.32, CVE-2026-40287's fix gated tools.py auto-import behind PRAISONAI_ALLOW_LOCAL_TOOLS=true
PraisonAI is a multi-agent teams system. From version 4.5.139 to before version 4.6.32, CVE-2026-40287's fix gated tools.py auto-import behind PRAISONAI_ALLOW_LOCAL_TOOLS=true in two files (tool_resolver.py, api/call.py). A third import sink in praisonai/templates/tool_override.py was missed and remains unguarded. It is reached by the recipe runner on every recipe execution and is remotely triggerable through POST /v1/recipes/run with a recipe value pointing at any local abso CVSSv3.1 8.4 (HIGH)
CVE-2026-43341 — Linux: In the Linux kernel, the following vulnerability has been resolved: net/ipv6: ioam6: prevent schema
In the Linux kernel, the following vulnerability has been resolved: net/ipv6: ioam6: prevent schema length wraparound in trace fill ioam6_fill_trace_data() stores the schema contribution to the trace length in a u8. With bit 22 enabled and the largest schema payload, sclen becomes 1 + 1020 / 4, wraps from 256 to 0, and bypasses the remaining-space check. __ioam6_fill_trace_data() then positions the write cursor without reserving the schema area but still copies the 4-byte s CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43334 — Linux: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: force responder
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: force responder MITM requirements before building the pairing response smp_cmd_pairing_req() currently builds the pairing response from the initiator auth_req before enforcing the local BT_SECURITY_HIGH requirement. If the initiator omits SMP_AUTH_MITM, the response can also omit it even though the local side still requires MITM. tk_request() then sees an auth value without SMP_AUTH_MITM an CVSSv3.1 8.8 (HIGH)
CVE-2026-43322 — Linux: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix UAF
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix UAF in le_read_features_complete This fixes the following backtrace caused by hci_conn being freed before le_read_features_complete but after hci_le_read_remote_features_sync so hci_conn_del -> hci_cmd_sync_dequeue is not able to prevent it: ================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/lin CVSSv3.1 8.8 (HIGH)
CVE-2026-43304 — Linux: In the Linux kernel, the following vulnerability has been resolved: libceph: define and enforce
In the Linux kernel, the following vulnerability has been resolved: libceph: define and enforce CEPH_MAX_KEY_LEN When decoding the key, verify that the key material would fit into a fixed-size buffer in process_auth_done() and generally has a sane length. The new CEPH_MAX_KEY_LEN check replaces the existing check for a key with no key material which is a) not universal since CEPH_CRYPTO_NONE has to be excluded and b) doesn't provide much value since a smaller than needed k CVSSv3.1 9.8 (CRITICAL)
CVE-2026-43291 — Linux: In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Fix
In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Fix parameter validation for packet data Since commit 9c328f54741b ("net: nfc: nci: Add parameter validation for packet data") communication with nci nfc chips is not working any more. The mentioned commit tries to fix access of uninitialized data, but failed to understand that in some cases the data packet is of variable length and can therefore not be compared to the maximum packet length CVSSv3.1 8.3 (HIGH)
CVE-2026-41512 — From version 1.0.0 to before version 1.4.1, there is a remote code execution vulnerability
ai-scanner is an AI model safety scanner built on NVIDIA garak. From version 1.0.0 to before version 1.4.1, there is a remote code execution vulnerability via JavaScript injection in `BrowserAutomation::PlaywrightService`. This issue has been patched in version 1.4.1. CVSSv3.1 9.9 (CRITICAL)
CVE-2026-41509 — Cross-crypto Cross-implementation: Prior to commit fc6b7e7, there is a buffer overflow in crypto_sign_open() caused by an
CROSS implementation contains reference and optimized implementations of the CROSS post-quantum signature algorithm. Prior to commit fc6b7e7, there is a buffer overflow in crypto_sign_open() caused by an underflow of the integer mlen. This issue has been patched via commit fc6b7e7. CVSSv3.1 9.8 (CRITICAL)
CVE-2026-41507 — This allows an attacker to execute arbitrary system commands when user-controlled input reaches the
math-codegen generates code from mathematical expressions. Prior to version 0.4.3, string literal content passed to cg.parse() is injected verbatim into a new Function() body without sanitization. This allows an attacker to execute arbitrary system commands when user-controlled input reaches the parser. Any application exposing a math evaluation endpoint where user input flows into cg.parse() is vulnerable to full RCE. This issue has been patched in version 0.4.3. CVSSv3.1 9.8 (CRITICAL)