grav-plugin-api versions before 1.0.20 have a privilege escalation vulnerability in the InvitationsController. The flaw allows a non-super user with certain API permissions to create an invitation containing a dot-keyed super flag that bypasses security checks. This enables the creation of a super-admin account without proper authorization, granting full site control upon acceptance of the invitation. The vulnerability has a high severity score of 8.7 and requires no user interaction to exploit.
A vulnerability in grav-plugin-api before version 1.0.20 allows non-super user managers with specific API permissions to modify super-admin accounts. This occurs due to improper validation of group-inherited super permissions in user-management guards. Exploiting this flaw, attackers can patch password fields on super-admin accounts, potentially gaining full administrative control.
The Theme My Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 7.1.15 on Multisite installations. This is due to the `tml_ms_signup_handler()` function's `gimmeanotherblog` branch failing to enforce the network's `active_signup` registration policy, checking only `is_user_logged_in()` while sibling branches such as `validate-blog-signup` apply the full policy gate. This makes it possible for authenticated attackers, with Subscriber-level access and above, to directly POST `stage=gimmeanotherblog` to Theme My Login's signup route, bypassing the configured registration policy entirely — even when it is set to `none` or `user` — which causes `wpmu_create_blog()` to execute with the attacker's user ID, after which WordPress core assigns the Administrator role on the newly created subsite via `add_user_to_blog()`. The privilege gain is scoped to the newly created subsite only; the attacker's account retains Subscriber-level access on the main site and does not obtain Super Admin or network-level capabilities such as `manage_network` or `manage_sites`.
A known issue affecting Microsoft Teams and the new Outlook on ARM-based Windows devices causes crashes and launch failures after installing August 2026 Patch Tuesday updates. The problem impacts devices running Windows 11 24H2 or later, particularly those that have not installed Microsoft Store updates. Microsoft has provided a temporary workaround involving updating the Auto Super Resolution Package and is working on a permanent fix in a future Windows update.
Devtron through 2.2.0 fails to enforce authorization checks on the GET /orchestrator/api-token/webhook endpoint, allowing authenticated users to retrieve admin API tokens. Attackers with any authenticated account can query the endpoint with arbitrary project, environment, and application parameters to retrieve plaintext super-admin JWT tokens for full platform control.
In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: avoid deadlock when canceling IRQ affinity notifier Unregistering IRQ affinity notifiers waits for the callback synchronously. bnxt takes the netdev instance lock in the notifier (to restart the queue) and cancels the work under the same lock. This may obviously deadlock. Move the restart to the async service task. The queue restart isn't super time sensitive. Store the new TPH tag, schedule the task. Safely canceling the service task is already ironed out. In bnxt_request_irq() the order of registering notifier, affinity and initial TPH programming has to be inverted. I think it was racy previously since user may trigger an update as soon as notifier is installed. There's a small known gap - if pcie_tph_get_cpu_st() fails at init and the target tag is 0 we may miss programming the entry. This does not seem worth fixing, the code has skip-on-failure all over the place, anyway.
JetBackup WordPress plugin versions before 3.1.23.5 have an authorization flaw that allows a network main site administrator, who is not a Super Admin, to download full backups of the entire multisite network including all sites' data and the shared webroot. This vulnerability arises from missing multisite authorization checks before serving backup archives and job logs.
In the Linux kernel, the following vulnerability has been resolved: xfs: fix off-by-one in rtrefcount btree root level validation xfs_rtrefcountbt_compute_maxlevels() sets mp->m_rtrefc_maxlevels = min(d_maxlevels, r_maxlevels) + 1; where the trailing "+ 1" already accounts for the inode-root level, so the deepest valid on-disk root level is m_rtrefc_maxlevels - 1 and a cursor must satisfy bc_nlevels <= bc_maxlevels (= m_rtrefc_maxlevels). The two on-disk validation paths, xfs_rtrefcountbt_verify() and xfs_iformat_rtrefcount(), check the root level with ">" instead of ">=", so a crafted rtreflink (metadir + realtime + reflink) image whose /rtgroups/N.refcount inode has bb_level == m_rtrefc_maxlevels is accepted on mount. xfs_rtrefcountbt_init_cursor() then sets bc_nlevels = bb_level + 1, exceeding bc_maxlevels by one. Since the xfs_rtrefcountbt_cur slab object is sized for exactly bc_maxlevels entries, the first btree op on such a cursor indexes bc_levels[m_rtrefc_maxlevels] past the end of the object. This is reached by the first rtrefcount cursor built after mount, via log/CoW recovery (xfs_reflink_recover_cow() during xfs_mountfs()) or an FS_IOC_GETFSMAP over the realtime device. Reject a root level equal to m_rtrefc_maxlevels, matching the ">=" form already used by the sibling data-device refcount/rmap verifiers and the in-memory rtrmap verifier. BUG: KASAN: slab-out-of-bounds in xfs_btree_lookup (fs/xfs/libxfs/xfs_btree.c:2101) Write of size 2 at addr ffff888018391658 by task exploit/144 xfs_btree_lookup (fs/xfs/libxfs/xfs_btree.c:2101) xfs_btree_query_range (fs/xfs/libxfs/xfs_btree.c:5308) xfs_refcount_recover_cow_leftovers (fs/xfs/libxfs/xfs_refcount.c:2113) xfs_reflink_recover_cow (fs/xfs/xfs_reflink.c:1085) xlog_recover_finish (fs/xfs/xfs_log_recover.c:3551) xfs_mountfs (fs/xfs/xfs_mount.c:1158) xfs_fs_fill_super (fs/xfs/xfs_super.c:1940) get_tree_bdev_flags (fs/super.c:1634) vfs_get_tree (fs/super.c:1694) path_mount (fs/namespace.c:4161) __x64_sys_mount (fs/namespace.c:4367) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The buggy address belongs to the cache xfs_rtrefcountbt_cur of size 216 The buggy address is located 8 bytes to the right of allocated 216-byte region [ffff888018391578, ffff888018391650) Kernel panic - not syncing: Fatal exception
CVE-2026-80203 is a critical authorization vulnerability in the getgrav/grav-plugin-api plugin before version 1.0.18. The flaw arises because the requireNotSuperTarget() function in UsersController.php incorrectly checks super-admin privileges based on the acting account rather than the API key's scope. This allows an API key with limited scope but belonging to a super-admin account to perform unauthorized actions against other super-admin accounts, such as disabling two-factor authentication, deleting avatars, creating new API keys under another identity, or deleting existing API keys.
CVE-2026-75797 is a path traversal vulnerability in the AI Engine WordPress plugin before version 3.7.2. It allows users with subscriber-level accounts to read arbitrary files on the server if a non-default public API feature is enabled. Without this feature, administrators (including non-super administrators on multisite setups) can exploit the issue to access network-shared configuration files and secrets.
Taiwanese prosecutors charged nine individuals, including employees from Nvidia and Super Micro, for illegally exporting high-end AI servers to mainland China. These servers contained banned graphics processing units (B300 GPUs) restricted under U.S. export controls. The shipments circumvented regulations through multiple routes including Indonesia, Japan, and Hong Kong. The case highlights ongoing tensions and regulatory enforcement in the AI infrastructure competition between the U.S. and China.
Grav Login plugin versions before 1.0.16 contain an authorization flaw in the onApiUserListRowAction unlock handler. This flaw allows an attacker with api.users.write permission to reset login lockout counters on admin.super accounts, effectively removing brute-force protection from these high-privilege accounts without needing equivalent permissions.
CVE-2026-28167 is a path traversal vulnerability in WebRehab Super Forms versions prior to 6.3.317. It allows attackers to access files outside the intended restricted directory by manipulating pathname inputs. The vulnerability has a high severity rating with a CVSS score of 7.5. A fix is available in version 6.3.317.
A vulnerability in Grav API Plugin prior to version 1.0.6 allows a non-super user with api.users.write permission to create an API key with super-administrator privileges. This occurs because certain user mutation endpoints omit a critical access check, enabling unauthorized privilege escalation and manipulation of two-factor authentication settings. The issue is fixed in version 1.0.6.
A vulnerability in Python 3.10's csv.Sniffer.sniff() function can cause excessive CPU consumption due to super-linear regular expression complexity when processing specially crafted CSV input. This may lead to a denial of service (DoS) condition. The issue affects Red Hat Hardened Images RPMs containing Python 3.10 packages. Most applications are not affected as they do not use the sniff() function on untrusted input. Red Hat has released updated RPMs to address this issue.
A vulnerability in Zabbix allows a Super Admin to leak the OAuth 'Client secret' by setting a malicious 'Token endpoint'. Although the 'Client secret' field cannot be read after saving, this flaw enables potential leakage through manipulation of the token endpoint. Changes have been made to reset the client secret when the token endpoint is changed to mitigate this issue.
Grav CMS versions before 2.0.14 contain a critical vulnerability where the core group blueprint's access field lacks proper admin.super guard. This allows a delegated admin.users operator to escalate privileges to super-admin by setting access[admin][super]=true, thereby gaining high-level capabilities such as scheduler and Twig evaluation.
This article provides an in-depth analysis of Microsoft's new unified Microsoft 365 Copilot super app, detailing its architectural shift that merges consumer and enterprise AI features. It highlights critical cybersecurity and data governance implications, including how Microsoft Entra enforces strict separation between personal and enterprise data to prevent leaks. The piece also outlines deprecated features and advises defenders on monitoring identity switching and file-sharing controls within the new environment.
The Grav API plugin (getgrav/grav-plugin-api) versions >= 1.0.6 and <= 1.0.11 contain a privilege escalation vulnerability. A scoped API key minted on a super-admin account bypasses its declared scope cap on four isSuperAdmin()-gated write endpoints (in GroupsController, AccountsConfigController, PreferencesController, and DashboardWidgetController). These endpoints authorize via a super-admin early-return that never invokes requirePermission()—the sole enforcement point of the scope cap—so a 'read-only'-scoped key (e.g. api.pages.read) can perform super-only write operations, including rewriting group ACL maps to grant super-admin privileges to arbitrary accounts. A leaked or delegated read-only CI/monitoring key can therefore gain full super-admin write capability. Fixed in 1.0.13.