baserCMS versions 5.2.3 before 5.3.2 and 5.4.0 before 5.4.2 contain a path traversal vulnerability in the optional BcThemeFile plugin's Admin API. The vulnerability arises because encoded path traversal sequences are decoded after validation, allowing an authenticated administrator to write PHP files outside the intended theme directory, such as into the webroot, and execute them. Exploitation requires an administrator session, the non-default plugin enabled, and a same-origin Origin header. The issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, list and detail actions in the Admin and Api/Admin prefixes pass request query parameters, including contain, conditions, fields, finder, and order, directly to the ORM as options. A user able to log into the admin panel can embed SQL fragments in those options to execute arbitrary SQL against the application's database, including reading password hashes from the users table. Public-page and public-API fixes released in 5.3.1 and 5.4.1 did not protect these administrative paths. Setting USE_CORE_ADMIN_API to false does not prevent access through an authenticated browser session. This issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, the public POST /baser/api/bc-mail/mail_messages/add/{mailContentId}.json endpoint accepts submissions without enforcing the form's auth_captcha setting. BcMail\Controller\Api\MailMessagesController::add() and MailMessagesService::create() omit the BcCaptchaService::check() verification of captcha_id and auth_captcha performed by MailController::submit() in the web UI. An unauthenticated attacker who can reach the API can therefore automate submissions without solving the enabled image challenge. The API disables FormProtection and has no rate limit; submissions can generate administrator-inbox spam, send attacker-influenced auto-replies to third parties when an email field is present, and accumulate mail_messages database records when save_info is enabled. The API already enforces the isAccepting() check added for CVE-2026-30878; the missing CAPTCHA check is a separate control failure. This issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS is a website development framework. Starting in version 5.0.0-beta1 and prior to versions 5.3.2 and 5.4.2, `PermissionGroupsService::build()` reads a plugin's `config/permission.php` to decide what each user group may reach. When that file is absent it writes a wildcard allow rule instead: `url` `/baser/<prefix>/<plugin>/*`, `method` `*`, `auth` true, for every non-admin group. BcCustomContent has no such file in any release. After an administrator installs it, the default `operators` group can store and execute arbitrary PHP under the document root. Versions 5.3.2 and 5.4.2 patch the issue.
CVE-2026-112855 is a critical vulnerability in axiomthemes Redy up to version 1.3.5 that allows deserialization of untrusted data leading to object injection. This flaw can result in complete compromise of confidentiality, integrity, and availability of the affected system.
PHP2Shell refers to two critical PHP engine vulnerabilities (CVE-2026-109618 and CVE-2026-109619) that allow unauthenticated remote code execution. These flaws have been exploited in attempts to spread a Mirai-derived botnet variant named Potassium. Despite multiple exploitation attempts and the emergence of an ASLR bypass exploit, no confirmed successful compromises have been reported. The vulnerabilities were patched on October 21, 2026, with PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Organizations have taken precautionary measures including taking systems offline during patching. Exploits require uncommon server configurations and detailed knowledge, limiting their effectiveness in typical production environments.
CVE-2026-99083 is a high-severity vulnerability in the Linux kernel's ksmbd component affecting versions from 5.15.145 up to but not including 5.16, 6.1.40 up to but not including 6.2, 6.4.5 up to but not including 6.5, and version 6.5. The flaw is a heap out-of-bounds write in the krb5_authenticate() function caused by an incorrect calculation of buffer headroom when processing compounded SMB2_SESSION_SETUP requests. This miscalculation allows memcpy() to overwrite adjacent kernel heap memory. The issue has been fixed in Linux kernel versions 5.16, 6.2, and 6.5.
VeloCloud Orchestrator (VCO) on-premises versions contain a critical SQL injection vulnerability (CVE-2026-114625) that allows authenticated users with minimal privileges, such as those with the Enterprise Read Only role, to escalate their access to superuser operator level. This escalation grants unauthorized access to privileged internal functionality, potentially compromising the confidentiality, integrity, and availability of the orchestrator and its managed data. The vulnerability is actively exploited in the wild, with specific malicious IP addresses identified. Fixed versions have been released for affected VCO versions 5.2.x, 6.1.x, and 6.4.x. Hosted and dedicated VCO instances have already been patched. Immediate upgrade to the fixed releases is recommended, along with restricting web interface access and monitoring for suspicious activity.
CVE-2026-98996 is a Linux kernel vulnerability where the system may silently unmount busy mounts during propagation, causing mounts still in use to be detached. This occurs due to propagate_mount_busy() not properly checking references on certain mount copies, allowing synchronous unmounts to succeed incorrectly. The issue affects multiple Linux kernel versions from 4.1.43 up to and including 4.13. The vulnerability has been fixed in Linux kernel versions 4.2, 4.5, 4.10, 4.12, and 4.13.
A concurrency issue in the Linux kernel's cxgb4/ch_ktls component was fixed by disabling softirqs around tid_list erases. The flaw involved improper locking when erasing entries from a shared XArray, which could lead to deadlocks due to softirq interruptions during cleanup. The issue affects specific Linux kernel versions prior to 5.11, between 5.12.9 and 5.13, and version 5.13 itself.
CVE-2026-98964 is a high-severity vulnerability in the Linux kernel's nvmet subsystem. It involves improper handling of the local peer-to-peer (P2P) device pointer during metadata allocation failure, which can lead to incorrect cleanup operations. This flaw was fixed in Linux kernel version 5.13 and other specified commits.
A vulnerability in the Linux kernel's riscv ptrace implementation allows uninitialized stack buffer data to be copied into the target's virtual state and shadow stack pointer due to insufficient zero-initialization before copyin operations. This issue affects Linux kernel versions from 6.5.3 up to and including 6.6 and has been fixed in version 6.6.
This update for mozilla-nss, MozillaFirefox fixes the following issues:
Update to Firefox Extended Support Release 153.5.1 ESR (MFSA 2026-112, bsc#1286385):
- CVE-2026-113470: Cryptographic issue in the Security Block-lists, Allow-lists, and other State component
(bsc#1286261).
PraisonAI is a multi-agent teams system. From version 4.5.110 to before version 4.6.61, praisonai.sandbox.SandlockSandbox is documented and implemented as the kernel-enforced sandbox backend for untrusted code. Its SandboxConfig.native() path lets callers configure allowed filesystem paths and network=False. On systems where the optional sandlock module imports but reports that Landlock is unavailable, SandlockSandbox.execute() and run_command() do not fail closed. They silently fall back to SubprocessSandbox(self.config). That fallback keeps the same high-level native policy object but does not enforce the native filesystem or network boundary during code execution. A sandboxed payload can read files outside the configured allowed path and open network connections despite network=False. This issue has been patched in version 4.6.61.
PraisonAI is a multi-agent teams system. From version 4.5.87 to before version 4.6.61, PraisonAI recipe execution has a dangerous-tool policy that is supposed to block default-denied tools unless the caller explicitly passes allow_dangerous_tools=True. That policy only checks tools declared in TEMPLATE.yaml requires.tools. For steps-based recipes, the actual execution path loads workflow.yaml with YAMLWorkflowParser. That parser resolves agent-level tools: declarations and preserves top-level approve:. Workflow.start() then installs those YAML-approved tools into the approval context. As a result, an untrusted recipe can omit execute_command from TEMPLATE.yaml requires.tools, declare it in workflow.yaml agents.*.tools, and add top-level approve: [execute_command]. The caller did not set allow_dangerous_tools=True, but the recipe policy allows the recipe and the workflow approval path self-approves the critical shell tool. This issue has been patched in version 4.6.61.
PraisonAI is a multi-agent teams system. From version 4.5.126 to before version 4.6.59, PraisonAI's Async Jobs API validates webhook_url when a job request is parsed and again when the internal Job object is constructed. That validation blocks direct loopback/private targets, but it is not bound to the later network request. When a job completes, _send_webhook() passes the original hostname to httpx.AsyncClient.post() with no send-time validation, IP pinning, or guarded transport. An attacker-controlled hostname can therefore resolve to a public IP during Pydantic validation and later resolve to loopback/private/cloud-metadata infrastructure during webhook delivery. This bypasses the intended SSRF guard in current supported releases. This appears to be an incomplete fix / patch bypass for GHSA-8frj-8q3m-xhgm. This issue has been patched in version 4.6.59.
CVE-2026-56836 is an improper authentication vulnerability in MervinPraison PraisonAI affecting versions from 4.5.112 up to but not including 4.6.59. The issue arises because the Recipe HTTP server can be started on a non-localhost interface without authentication, allowing unauthenticated access to the recipe API and potentially the /admin/reload endpoint. This vulnerability has been patched in version 4.6.59.
A vulnerability in the Linux kernel's ntfs3 driver related to improper handling of set_blocksize failures has been resolved. The issue arises because ntfs3 uses buffer_heads, which do not handle block sizes larger than PAGE_SIZE correctly, leading to a kernel BUG_ON during mounting. This bug triggers in folio_set_bh on the first __bread_gfp call. The vulnerability affects Linux kernel version 5.15 and has been fixed in specific commits.
A regular expression used in the OpenTelemetry Python API's TraceState.from_header method causes quadratic CPU time complexity when parsing specially crafted tracestate headers with long runs of spaces or tabs. This can lead to denial of service by blocking the handling worker for several seconds on a single unauthenticated request. The issue affects versions from 1.0.0 through at least v1.45.0 and is fixed in version 5.14.0_18.