A security vulnerability in the sudo utility allows bypass of time-based authorization controls via the TZ environment variable. This affects Red Hat Enterprise Linux 7 Extended Lifecycle Support versions. The flaw permits users to circumvent NOTBEFORE/NOTAFTER restrictions that control when sudo commands can be executed. Red Hat has issued an important security update to address this issue.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat JBoss Enterprise Application Platform 8.1.9, which is based on the WildFly application runtime. The update fixes issues including information disclosure via CORS header overwrite, denial of service via uncontrolled form parameters, authentication bypass via crafted OIDC tokens, and XML External Entity (XXE) vulnerabilities in Apache CXF components. These vulnerabilities could allow attackers to bypass security controls, cause denial of service, or disclose sensitive information. The advisory rates the update as important and provides fixes in version 8.1.9.
The Echo proxy middleware in github.com/labstack/echo/v5 forwards the X-Real-IP header from incoming requests to upstream services without validation by default. This allows an attacker to supply a spoofed X-Real-IP value, which the proxy relays unchanged. As a result, upstream IP-based access controls, rate limiting, audit logging, and geo-restriction mechanisms relying on X-Real-IP can be bypassed or corrupted. The vulnerability exists because the default configuration leaves IPExtractor unset, preserving legacy behavior that trusts the incoming header. A fix is available in version 5.4.0.
This article discusses the widespread reliance on security questionnaires in B2B transactions despite their inherent weaknesses. It highlights that these self-assessments are distrusted by those who fill them out but accepted by those who receive them, creating a paradox where trust is based on unverified vendor claims. The piece emphasizes that security questionnaires capture intentions rather than verified controls, contributing to persistent third-party breaches. It advocates for shifting from self-reported answers to observable evidence and independent attestations to establish trust between companies.
The Bit Flows plugin for WordPress up to version 1.31.0 is vulnerable to a Local File Inclusion (LFI) flaw via the 'image' parameter used by the ImageHelper node. This vulnerability allows unauthenticated attackers to include and execute arbitrary PHP files on the server if certain webhook configurations are in place, potentially leading to code execution or access control bypass. Exploitation requires an administrator to have configured a webhook-triggered flow using the vulnerable node without additional security controls like bearer secrets or IP allowlists.
The Customer Email Verification plugin for WooCommerce on WordPress has an authentication bypass vulnerability in all versions up to 2.8.2. The flaw arises from a predictable email verification token and lack of proper capability or nonce checks in the authentication function. This allows unauthenticated attackers to log in as verified customers or mark existing accounts as verified, bypassing email verification controls. Exploitation depends on the presence of a password column in a specific database table, which exists only on upgraded sites from older versions.
Tabularis versions prior to 0.28.0 contain an SQL injection vulnerability in the SQLite driver. This flaw allows malicious clients to execute stacked SQL statements by manipulating the table_name parameter in the describe_table tool. Exploitation can bypass read-only mode and write approval controls, enabling unauthorized reading, modification, or deletion of SQLite data. The vulnerability is fixed in version 0.28.0.
Tanium Comply contains an improper access controls vulnerability identified as CVE-2026-108301. This flaw could allow an attacker with low privileges to cause partial compromise of confidentiality, integrity, and availability. The vulnerability has a medium severity rating with a CVSS score of 6. No specific affected versions or patch information is provided.
Adobe Campaign Classic contains an SQL Injection vulnerability that allows a low-privileged attacker to bypass security controls and gain unauthorized read and limited write access without user interaction. The vulnerability affects the product and changes the security scope.
Attackers compromised camera management software (CMS.exe) to gain initial access to multiple organizations. They deployed malware (rs.win32.exe) into user AppData directories and used DLL sideloading with the legitimate Windows binary WpcMon.exe and malicious DLLs to establish beaconing to a command-and-control server. Persistence was maintained via Run Key registry modifications. The affected camera management software, possibly linked to 3R Global and kvision.ai, lacked sufficient security controls and logging. Organizations are advised to treat camera systems and their management platforms as critical attack surfaces and implement access controls and monitoring to detect unusual activity.
An authentication bypass vulnerability exists in JP1/Automatic Job Management System 3 - Manager versions from 10-00 up to but not including 13-50-31. This flaw allows an attacker to bypass authentication controls, potentially leading to full system compromise. The vulnerability has a critical severity with a CVSS score of 9.8, indicating high impact on confidentiality, integrity, and availability.
Apple released security patches on October 26, 2026, addressing 304 vulnerabilities across multiple products including iOS, iPadOS, macOS, tvOS, watchOS, and Safari. The update includes fixes for several critical issues such as a previously exploited CoreGraphics vulnerability, unauthorized camera access by malicious apps, and local attacks on the Keychain. Other vulnerabilities allow privilege escalation, denial-of-service, memory corruption, arbitrary code execution, and bypass of security controls like Gatekeeper and Privacy preferences. The patches cover a wide range of components including Spotlight, Kernel, Mail, AppleAVD, Model I/O, and Screen Sharing Server. No new vulnerabilities are reported as already exploited in the wild in this update. The affected versions include recent releases of iOS, iPadOS, macOS Golden Gate, Tahoe, Sequoia, tvOS, watchOS, visionOS, and Safari.
YesWiki versions prior to 4.7.0 have a vulnerability in the AclService::updateRequestWithACL function where usernames are interpolated into SQL LIKE patterns without escaping wildcard characters. This allows self-registered attackers to bypass read access controls by using specially crafted usernames containing _ or % wildcards, enabling unauthorized reading of restricted pages and Bazar entries via the public Bazar listing API. The issue is fixed in version 4.7.0.
OpenPanel versions prior to 3.0.0 have an unauthenticated SQL injection vulnerability in the ClickHouse database via the projectId parameter in the /live/visitors/:projectId WebSocket endpoint. This flaw allows remote attackers to inject SQL commands without authentication, bypassing session and project access controls. Exploitation can lead to unauthorized reading of other tenants' events and profiles. The vulnerability is fixed in OpenPanel version 3.0.0.
A vulnerability in Johnson Controls Kantech Entrapass before version 9.20 involves the use of a hard-coded cryptographic key, which enables a Padding Oracle Crypto Attack. This security flaw can compromise the confidentiality and integrity of encrypted data within the affected software.
bt_hfp_hf_connect() in subsys/bluetooth/host/classic/hfp_hf.c allocates the per-connection HFP Hands-Free object with hfp_hf_create(), which starts an SDP discovery by passing the object's embedded hf->sdp_param to bt_sdp_discover(). That call links the caller-owned parameter block into the SDP client's request list (session->reqs in subsys/bluetooth/host/classic/sdp.c). If the subsequent bt_rfcomm_dlc_connect() then failed, the affected code wiped the entire object with (void)memset(new_hf, 0, sizeof(*new_hf)) while that discovery was still outstanding, zeroing the sys_snode_t _node that is still linked in the SDP client's list along with the request's func, uuid and pool pointers, and zeroing the hf->slc_work work item that may already be queued on the system workqueue. The discovery could not be retracted instead: bt_sdp_discover_cancel() is declared in include/zephyr/bluetooth/classic/sdp.h but has no implementation.
The failing branch is reachable with peer-supplied input. The documented use of bt_hfp_hf_connect() is to pass the RFCOMM channel read out of the remote Audio Gateway's SDP record; neither bt_sdp_get_proto_param() nor bt_hfp_hf_connect() range-checks that value, so a remote device advertising an HFP AG record with an RFCOMM channel outside 1-30 makes bt_rfcomm_dlc_connect() return -EINVAL and drives the local device into the wipe. The same branch is reached without any application misuse when the remote peer controls connection timing, for example when the RFCOMM session is in BT_RFCOMM_STATE_DISCONNECTING or the ACL is dropped between object creation and the RFCOMM call.
Once the object has been wiped, the Bluetooth host continues to use it: sdp_client_alloc_buf() dereferences session->param->pool, which is now NULL, and the SDP receive paths call session->param->func() through a null function pointer, neither of which is NULL-checked. Because the wipe also clears hf->acl, the pool slot is considered free and a retry or an incoming HFP connection re-appends the same still-linked list node, turning session->reqs into a self-referential list that the host's list walkers never leave. The result is a fault or an unrecoverable hang in the Bluetooth host thread; the stray indirect call is through an all-zero pointer whose target the attacker does not control, so the practical impact is denial of service.
The fix keeps the object allocated and marks it with a new BT_HFP_HF_FLAG_RELEASING flag, letting bt_hfp_hf_discover_cb() release it once the discovery completes instead of destroying it under the SDP client. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_HFP_HF enabled are affected.
CVE-2026-95629 is a path traversal vulnerability in the Apache Camel Docling component that allows an attacker able to set a specific header to write conversion output files to arbitrary directories writable by the Camel process. This occurs because the CamelDoclingOutputFilePath header value is passed verbatim to the external docling tool's output flag without proper normalization or confinement. The issue affects Apache Camel versions from 4.15.0 before 4.18.5 and from 4.19.0 before 4.22.2. The vulnerability is fixed in Apache Camel versions 4.18.5, 4.22.2, and 4.23.0. Users are advised to upgrade and configure the new outputBaseDirectory option to restrict output paths. For those unable to upgrade immediately, mitigating controls include sanitizing or removing the vulnerable header from externally sourced messages.
A security vulnerability exists in HeyCyan App version 1.0.103 on Android involving the FileProvider component, which suffers from improper access controls. This flaw can be exploited remotely without user interaction, potentially leading to limited confidentiality, integrity, and availability impacts. The vendor has not responded to disclosure attempts, and no patch information is available.
CVE-2026-116108 is a medium severity vulnerability in openbq-org OpenBB versions 4.7.0, 4.7.1, 4.7.2, 5.0, and 5.0.0. It involves improper access controls in the Local API Server component, specifically in the file openbb_platform/core/openbb_core/app/model/api_settings.py. The flaw allows remote exploitation without privileges or user interaction. Exploit code has been published, but no vendor response or patch is currently available.