A vulnerability in the Abdurrab5 online-makeup-store affects the confirm_logged_in/confirm_user function in the Admin Handler component. Manipulation of the adminid argument can lead to missing authorization, allowing remote attackers to bypass access controls. The vulnerability has a CVSS score of 7.3, indicating a medium severity. The product uses a rolling release system, so specific affected or fixed versions are not disclosed. The vendor was notified early, but no patch information is currently available. Exploit details have been publicly disclosed, but no known exploits are reported in the wild.
A security flaw has been discovered in kvcache-ai mooncake up to 0.3.12/0.3.13.post1/0.3.14-rc1. This issue affects the function ScopedSegmentAccess::MountSegment of the file segment.cpp of the component MountSegment Request Processing. Performing a manipulation results in improper access controls. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability in the sudo utility allows bypass of time-based authorization controls via the TZ environment variable. This flaw affects sudo versions used in Red Hat Enterprise Linux 8 and Red Hat Hardened Images. The issue enables users to circumvent NOTBEFORE/NOTAFTER restrictions that control when sudo commands can be executed. Red Hat has released security updates to address this vulnerability.
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, The management UI uses EJS 1.0 in which <%= ... %> does NOT HTML-escape. connection.ejs:135 renders <%= connection.ssl_details.peer_cert_subject %> (and peer_cert_issuer) directly into the page. The same pattern appears in streamConnection.ejs:102,106,110. The values come from rabbit_ssl:peer_cert_subject/1 which formats the DN as a string without HTML escaping. The verifier corrected the original researcher's claim: this is reachable only when the listener is configured with verify_peer (so the certificate must be signed by a CA in the broker's trust store, not arbitrary self-signed); however, in deployments using mTLS for client authentication, any user who can request a certificate from the organisational CA controls the Subject CN. An attacker who can obtain a TLS client certificate signed by a CA the broker trusts (with verify_peer enabled) can embed JavaScript in the certificate's Subject DN. When any administrator views that connection in the management UI, the script executes in the admin's browser session, allowing full account takeover (create users, export definitions, etc.). The management UI's CSP includes 'unsafe-inline', so inline script execution is not blocked. Preconditions include TLS listener configured with ssl_options.verify = verify_peer Attacker can obtain a CA-signed client certificate with attacker-chosen Subject (e.g. self-service corporate PKI, or rabbitmq_trust_store plugin in use) Administrator views the connection detail page. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Cinnamon's Kotaemon (all versions up to and including v0.12.0) multi-user chat interface contains multiple vulnerabilities due to incorrect authorization and improper access controls. There are four handler methods in `libs/ktem/ktem/pages/chat/control.py` that load a Conversation record by its ID without comparing the requester's `user_id` to the conversation's owner `Conversation.user`. This allows any authenticated user to perform the following actions:
1. Read other user's chat transcripts, RAG retrieval history, AI-generated plots, and chat suggestions.
2. Permanently delete another user's conversation.
3. Rename another user's conversation.
4. Overwrite another user's conversation's chat suggestion list.
This is an academic research survey targeting U.S.-based IT and security professionals at small and medium-sized enterprises (SMEs) that have experienced ransomware attacks between 2021 and 2025. The research aims to empirically study which security controls effectively enable recovery and resilience after ransomware incidents at the SME scale. The survey is IRB-approved, anonymous, and offers no compensation. It does not describe a specific vulnerability or active threat but seeks to gather data on ransomware experiences.
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, Jira search accepts a forbidden project clause because it checks only for the presence of project syntax, Confluence search uses an incomplete case-sensitive space check, and Jira board APIs omit project-filter enforcement. These paths expose issues, boards, or pages outside JIRA_PROJECTS_FILTER or CONFLUENCE_SPACES_FILTER when the operator credentials have broader access. The advisory traces the vulnerable input and processing flow through jira_search, confluence_search, get_board_issues, get_agile_boards, JIRA_PROJECTS_FILTER, and CONFLUENCE_SPACES_FILTER, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
This content describes an upcoming webinar that will analyze real-world breaches of Google Workspace environments. The breaches discussed involve social engineering and malicious OAuth applications to gain unauthorized access. The webinar will cover the initial access methods, the critical first hours of incident response, and the security controls that can most effectively mitigate such breaches. It aims to provide practical lessons for security teams, especially those with limited resources, focusing on response decisions and security improvements rather than generic best practices.
The HUSKY – Products Filter for WooCommerce Professional plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.4 via the 'shortcode' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. This vulnerability is exploitable by unauthenticated users because the only access control is a nonce check against woof_front_nonce, which is publicly emitted into inline JavaScript on every front-end page and is therefore obtainable by any site visitor without authentication.
A security vulnerability identified as CVE-2026-56854 affects Red Hat OpenShift Builds, a Platform as a Service (PaaS) solution for cloud application deployment. The vulnerability allows bypassing of security controls related to NetworkPolicy blocking of kube-apiserver webhook traffic due to hostNetwork limitations. Red Hat has released version 1.9.1 of OpenShift Builds to address this issue and recommends upgrading from version 1.9.0.
CVE-2026-77521 is a critical OS command injection vulnerability in MaxKB, an open-source AI assistant for enterprise. Versions prior to 2.10.5-lts allow untrusted input to execute shell commands without human approval due to improper sandboxing and command execution controls. This can lead to full system compromise by executing arbitrary commands as the application user. The issue is fixed in version 2.10.5-lts.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.27.6, the response_mode=form_post SSO return path in warpgate-protocol-http/src/api/sso_provider_list.rs uses serde_json::to_string inside ReturnToSsoPostResponse without neutralizing a script-closing sequence. The vulnerable value can enter the script block through the attacker-controlled next redirect parameter stored by warpgate-protocol-http/src/api/sso_provider_detail.rs or through IdP-derived error messages that make_redirect_url concatenates without URL encoding. The IdP-derived path is reachable when the attacker controls a configured identity provider, or when the attacker controls the email or username claim on an attacker-controlled account and the configured identity provider permits the required unvalidated claim format. A victim must complete the form_post SSO flow for the injected markup to be rendered. The Warpgate Content-Security-Policy blocks injected JavaScript and event handlers, so the demonstrated impact is content spoofing, a false login form, or a meta refresh rather than script execution. This issue is fixed in version 0.27.6.
Google was fined 403 million euros ($463 million) by the European Union for breaching GDPR privacy rules related to the mishandling of users' location data. The investigation by Ireland’s Data Protection Commission found that Google did not lawfully or transparently process location data collected through its Web & App Activity setting, Location History service, and Location Accuracy feature in Android. The case concerns policies in effect from 2018 to early 2020, which Google states have since been updated with improved privacy controls. This fine is among the largest issued by the Irish regulator, which continues to investigate other privacy issues involving Google.
Tinyauth is an authentication and authorization server. Prior to 5.1.2, Tinyauth compares forwarded hostnames case-sensitively while reverse proxies route equivalent hostnames case-insensitively, allowing an authenticated low-privilege user to bypass per-app access controls with a differently cased hostname. The lookup in internal/service/access_controls_service.go through lookupStaticACLs and GetAccessControls, and the Docker-label fallback in internal/service/docker_service.go through GetLabels, can miss the configured app and return an empty access-control object. internal/controller/proxy_controller.go proxyHandler then treats the empty user, group, OAuth, LDAP, and IP restrictions as permissive and returns an authenticated result for an app that should exclude the user. Unauthenticated users remain subject to login, and global login-time allowlists are not bypassed. This issue is fixed in version 5.1.2.
In late August, an organization was compromised by INC ransomware affecting at least 175 endpoints. The attack unfolded over several weeks with a 17-day gap, indicating involvement of an initial access broker and a separate ransomware affiliate. Early activity included scheduled tasks with randomized names and lateral movement via RDP using compromised credentials. After the pause, attackers deployed AnyDesk for remote access, used Bring Your Own Vulnerable Driver (BYOVD) techniques to disable security controls, and executed ransomware using Impacket tools. Two ransom notes were found: the standard ransom demand and a secondary data leak threat note listing stolen files and threatening to contact media, employees, and partners within 48 hours to pressure the victim.
Ireland's Data Protection Commission fined Google €403 million for multiple GDPR violations related to processing users' location data. The investigation focused on three Google features active from May 2018 through February 2020: Web and App Activity, Location History, and Location Accuracy. The DPC found that Google processed location data without meeting GDPR requirements, failed transparency obligations, and retained data longer than necessary. Google has since updated its policies and implemented improved data management controls. The DPC requires Google to comply within six months. No active exploit or vulnerability is reported.
The FBI's CJIS Security Policy version 6.1 updates encryption requirements and vulnerability scanning frequency for agencies handling Criminal Justice Information (CJI). It raises encryption strength for data in transit and at rest to at least 256-bit and requires monthly vulnerability scans instead of quarterly. While audit requirements are phased, agencies should prepare for more continuous assessments and stricter compliance verification, especially around password and multi-factor authentication (MFA) controls. The policy emphasizes stronger identity verification and device assurance but is not a Zero Trust standard. Agencies are encouraged to review and enhance password policies and MFA coverage to meet the updated requirements.
Improper handling of highly compressed data (data amplification) in Checkmk <2.5.0p14, <2.4.0p37, <2.3.0p51 and 2.2.0 (EOL) allows an attacker who controls a host registered for push mode to exhaust the memory of the agent receiver by sending a small zlib compressed payload that decompresses to an arbitrary size.
CVE-2026-94036 is a high-severity vulnerability in D-Link DIR-X1860 and DIR-X1860Z routers up to version 1.0.2.220120.165402. It involves improper access controls in an unknown function of the /ubus file within the routerd component. The vulnerability arises from manipulation of the passwd_set argument and requires the attacker to be on the local network. Public exploit code is available, increasing the risk of attacks.
The WordLift – AI powered SEO – Schema plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.54.10 via the JSON-LD REST API endpoints. This is due to the plugin registering the /wordlift/v1/jsonld/ routes (jsonld/{id}, jsonld/http/{item_id}, jsonld/post-meta/{meta_key}, jsonld/meta/{meta_key}, and jsonld/{post_type}/{post_name}) with a permission_callback of '__return_true' and the downstream converter retrieving the post via get_post() without verifying the post status or the requesting user's capabilities. This makes it possible for unauthenticated attackers to read the title, content/description, author, publication and modification dates, word count, comment count, and other metadata of private, draft, and pending posts by enumerating post IDs, bypassing WordPress core access controls.