Authentication Bypass

Privilege escalation via capture-replay authentication bypass in Microsoft Exchange Server 2016, 2019, and Subscription Edition exposes organizations to full mailbox and administrative compromise. An already-authorized low-privilege network user can intercept and replay authentication tokens to impersonate higher-privileged accounts, achieving high confidentiality, integrity, and availability impact. No public exploit code or CISA KEV listing exists at time of analysis, but Microsoft has released patches across all affected cumulative update tracks.

Denial-of-service in Microsoft .NET runtimes and Visual Studio allows unauthenticated remote attackers to crash or hang .NET applications by supplying crafted input that exploits an unchecked loop termination condition. Affected are .NET 8.0 (all releases through 8.0.29), .NET 9.0 (through 9.0.18), .NET 10.0 (through 10.0.10), and bundled Visual Studio 2022 and 2026 installations. No public exploit has been identified at time of analysis, but the low attack complexity and lack of authentication requirement make this a credible automated threat against any internet-exposed .NET service. Vendor-released patches are available and should be applied promptly, particularly for externally reachable endpoints. Note: the ENISA EUVD tags this as 'Authentication Bypass,' which conflicts with the description and CVSS impact metrics (C:N/I:N/A:H); this discrepancy should be verified with Microsoft's advisory.

Remote code execution via double free (CWE-415) in the Windows Secure Socket Tunneling Protocol (SSTP) service enables a network-adjacent, unauthenticated attacker to corrupt heap memory and execute arbitrary code. The vulnerability spans virtually every supported Windows Server and Windows 10/11 release, from Server 2012 through Server 2025 and Windows 11 26H1, making the remediation footprint extremely broad. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the CVSS AC:H rating indicates exploitation requires specific race or protocol conditions rather than a trivial spray-and-pray approach.

Privilege escalation in Microsoft .NET Framework via incorrect authorization (CWE-863) allows network-authenticated low-privilege attackers to elevate their privileges, achieving full compromise of confidentiality, integrity, and availability on affected systems. Affected release families span .NET Framework 3.5 through 4.8.1, covering a broad swath of Windows enterprise deployments across multiple independently-installed runtime versions. No public exploit has been identified at time of analysis; a vendor-released patch with specific fix version thresholds is available through the Microsoft Security Response Center.

Privilege escalation in Microsoft SharePoint allows an authenticated low-privilege attacker to elevate to higher permissions over a network, exploiting improper authentication logic (CWE-287). Three on-premises SharePoint versions are confirmed affected - Enterprise Server 2016, Server 2019, and the current Subscription Edition - with vendor-released patches available for all. No public exploit or CISA KEV listing has been identified at time of analysis, though the CVSS 8.8 score and full High C/I/A impact profile make this a serious priority for organizations running unpatched on-premises SharePoint.

Remote code execution in Windows DNS Server allows unauthenticated network attackers to exploit a race condition in concurrent DNS request processing to achieve full system compromise. The flaw spans Windows Server 2016 through 2025 and select Windows 10 builds, targeting the server-side DNS component; the 'Authentication Bypass' tag indicates the race window undermines an internal access control that would otherwise gate execution. Microsoft has released build-specific patches; no public exploit code or CISA KEV listing has been identified at time of analysis, though the network vector and full C/I/A impact make this a high-priority patching target for any organization running the Windows DNS Server role.

Remote code execution in Windows Routing and Remote Access Service (RRAS) allows unauthenticated network attackers to fully compromise affected hosts across an exceptionally broad range of Windows versions, from Server 2012 through Server 2025 and Windows 10/11. The root cause is a use-after-free memory corruption flaw (CWE-416) combined with an authentication bypass, enabling an attacker to execute arbitrary code without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-exposed attack surface, zero-authentication barrier, and breadth of affected platforms make this a high-priority patching target. A vendor-released patch is available via Microsoft MSRC.

Privilege escalation in Windows License Manager exposes a critical authenticated-but-low-privileged local attacker path to full SYSTEM-level control across a wide range of Windows client and server builds. The root cause (CWE-306) is a missing authentication gate on a privileged License Manager function - an authorized standard user can invoke it without satisfying the elevated-privilege check that should protect it. Microsoft has released patches covering Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H1), and Windows Server 2016 through 2025; no public exploit code or CISA KEV listing has been identified at time of analysis.

Local privilege escalation in Windows Installer (msiexec) affects virtually the entire modern Windows ecosystem - from Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through 2025 - via an incorrect authorization flaw (CWE-863). An attacker with low-privilege authenticated local access can exploit the broken authorization check within the Installer service to elevate to SYSTEM-level privileges, achieving full confidentiality, integrity, and availability impact on the host. No public exploit code has been identified at time of analysis, though Microsoft has released patches across the full affected version matrix per MSRC advisory.

Privilege escalation in Windows Remote Desktop Services affects a broad range of Windows Server and client platforms, allowing a locally authenticated low-privilege user to elevate to SYSTEM-level access by invoking a critical RDS function that lacks proper authentication enforcement (CWE-306). The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H reflects low attack complexity and full confidentiality, integrity, and availability impact once local access is established. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor-released patches are available for all affected versions.

Privilege escalation in Windows Remote Desktop Services (RDS) via a missing authentication check (CWE-306) allows a locally authenticated, low-privileged user to gain SYSTEM or administrator-level access on the target machine. The vulnerability affects an exceptionally broad range of Microsoft Windows releases - from Windows Server 2012 through Windows Server 2025 and Windows 10/11 across multiple feature updates - multiplying the organizational exposure. No active exploitation is confirmed by CISA KEV and no public exploit code is identified at time of analysis, though the low attack complexity (AC:L) and absence of required user interaction make the technique straightforward once a local foothold is achieved.

Privilege escalation in Windows Remote Desktop Services affects a broad range of Windows 10, Windows 11, and Windows Server versions from 2012 through 2025, allowing a locally authenticated low-privilege attacker to elevate to full SYSTEM-level control. The root cause is CWE-306 - a critical RDS function entirely lacking an authentication gate - meaning any low-privilege account holder can invoke it without proper authorization. Microsoft has released patches across all affected product lines, though no public exploit code or CISA KEV listing was present in the available intelligence.

Privilege escalation in Windows Remote Desktop Services (RDS) exploits a missing authentication check for a critical internal function, allowing a locally authenticated attacker to gain SYSTEM-level or equivalent elevated privileges. Affected platforms span Windows 10, Windows 11, and Windows Server 2019 through 2025, covering a broad swath of modern Microsoft deployments. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vendor-confirmed patch availability and low attack complexity make rapid patching urgent.

Remote code execution via race condition in the Windows Remote Desktop Client enables unauthenticated network attackers to execute arbitrary code on affected systems across a broad sweep of Windows versions - from the aging Windows Server 2012 through the current Windows 11 26H1 and Windows Server 2025. The flaw (CWE-362) arises from improper synchronization of shared resources during concurrent execution within the RDP client stack, allowing an adversary who can win a precise timing window to achieve full code execution. No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as none, though the CVSS base score of 8.1 and total technical impact classification make this a meaningful patching priority.

Remote code execution in Visual Studio Code (versions 1.0.0 through 1.132.0) is enabled by a missing authorization check (CWE-862) on a network-accessible code path, allowing an unauthenticated network attacker to execute arbitrary code on a victim's machine with high impact across confidentiality, integrity, and availability. Exploitation requires user interaction (CVSS UI:R), meaning the victim must engage with attacker-controlled content. A vendor-released patch is available in version 1.132.1; no public exploit code or CISA KEV listing is confirmed at time of analysis.

Security feature bypass in Visual Studio Code (versions 1.0.0 through 1.132.1) exploits CWE-639, where authorization decisions rely on attacker-controllable keys, allowing a local attacker to circumvent an intended access control with high impact across confidentiality, integrity, and availability. The attack requires no elevated attacker privileges but does require a legitimate VS Code user to interact with the manipulated environment, pointing to shared-workstation or social-engineering delivery paths. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog at time of analysis; a vendor-released patch is available at version 1.132.1.

Spoofing via origin validation failure in Windows Network Address Translation (NAT) exposes Windows Server 2025 and Windows 11 (versions 24H2 through 26H1) to network-layer address spoofing by unauthenticated attackers on an adjacent network. The flaw, rooted in CWE-346, allows crafted packets to bypass NAT's origin-trust enforcement, potentially enabling man-in-the-middle interception or manipulation of traffic transiting the NAT boundary. The CVSS scope change (S:C) reflects that the impact extends beyond the host running NAT to other systems whose traffic passes through it. No public exploit code or active exploitation has been confirmed at time of analysis.

Security feature bypass in the Python extension for Visual Studio Code (versions prior to 1.132.1) allows a local attacker to load functionality from an untrusted control sphere, achieving full compromise of confidentiality, integrity, and availability. The attack requires user interaction - specifically opening a malicious workspace or project directory - making it highly relevant in developer supply-chain and social engineering scenarios such as cloning a weaponized repository. No public exploit code or CISA KEV listing has been identified at the time of analysis, but the full CIA impact and low attack complexity elevate real-world concern for development environments.

Privilege elevation in Microsoft Azure Kubernetes Service (AKS) lets a network-based, unauthenticated attacker gain elevated privileges by reaching a critical function that lacks an authentication check (CWE-306). Microsoft rates it 9.4 (Critical) with an AV:N/AC:L/PR:N/UI:N vector, indicating trivial remote reachability and no user interaction, though scope is unchanged. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the missing-auth root cause and high confidentiality/integrity impact make it a high-priority cloud-platform issue.

Local privilege escalation in the Windows RPC API exploits a missing authentication gate on a critical function (CWE-306), enabling any low-privileged authenticated local user to attain SYSTEM-level control across a sweeping range of Windows 10, Windows 11, and Windows Server editions from 2012 through 2025. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms low-complexity exploitation requiring only a standard user account with no user interaction. No public exploit code is identified at time of analysis, and CISA SSVC rates current exploitation status as none, though technical impact is rated total.

Authentication bypass in Zoho ManageEngine DDI Central versions prior to 6201 lets remote unauthenticated attackers hijack the password-reset workflow to seize control of arbitrary accounts. Successful takeover of an administrative account grants full control over the DNS, DHCP, and IPAM management platform, with total impact to confidentiality, integrity, and availability. There is no public exploit identified at time of analysis and it is not on CISA KEV, though CISA's SSVC framework rates the flaw as fully automatable with total technical impact.

Incorrect Authorization (CWE-863) in Adobe ColdFusion 2023 and 2025 allows adjacent-network attackers to bypass authorization controls and execute arbitrary code in the context of the ColdFusion service account. The vulnerable administrative component is confined to an administrative network zone by default, limiting internet-scale exposure but leaving internal networks and misconfigured deployments at significant risk. No public exploit code or CISA KEV listing has been identified at time of analysis, though the complete CIA impact and zero-authentication requirement make this a high-priority patch target for any organization running ColdFusion.

Incorrect Authorization in Adobe ColdFusion 2023 and 2025 enables unauthenticated remote attackers to bypass security controls and gain limited unauthorized read and write access to protected resources, with a limited disruption to availability. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms the attack requires no authentication, no user interaction, and is reachable over the network under low complexity conditions. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Improper Input Validation in Adobe ColdFusion 2023 and 2025 allows unauthenticated remote attackers to bypass security controls, gaining unauthorized read and limited write access to affected systems. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is a low-complexity, network-exploitable flaw requiring no privileges or user interaction, elevating real-world risk for any internet-facing ColdFusion deployment. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but ColdFusion's history as a high-value target warrants prompt patching.

Hard-coded cryptographic key in Adobe ColdFusion 2023 and 2025 enables a local low-privileged attacker to bypass security controls and gain unauthorized read and write access with scope change to components beyond the vulnerable server. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H) confirms local access with minimal complexity is sufficient - no user interaction is needed. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the deterministic, non-rotating nature of a hard-coded key means any attacker who extracts it retains persistent capability until the key is replaced via patch.

Security feature bypass in Adobe ColdFusion 2023 and 2025 lets attackers with adjacent network access defeat authorization checks (CWE-863, Incorrect Authorization) and obtain unauthorized read and write access, potentially forcing an application denial-of-service. The flaw carries a CVSS 9.6 (scope-changed) rating and requires no user interaction, though the vulnerable component sits inside an administrative network zone by default. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so treat the 9.6 as high potential rather than confirmed active abuse.

Privilege escalation in Adobe ColdFusion 2023 and 2025 allows a low-privileged local user to gain unauthorized read and write access through an Incorrect Authorization flaw (CWE-863). Exploitation requires only a low-privileged local account and no user interaction, yielding full confidentiality, integrity, and availability impact on the affected system. Adobe has published advisory APSB26-90; no public exploit code or CISA KEV listing has been identified at time of analysis.

Privilege escalation in the Alias Checking Trusted Module (ACTM) firmware for certain Intel Xeon processors allows a local privileged attacker to escalate to System Management Mode (SMM) execution, achieving high confidentiality and integrity impact across both the directly compromised system and subsequent systems such as co-hosted hypervisors or tenant workloads. The attack requires high-complexity local technique combined with pre-existing privileged user access, placing it firmly in the advanced persistent threat actor category. No public exploit has been identified at time of analysis, and Intel has published advisory INTEL-SA-01439 to address this firmware flaw.

Improper authentication (CWE-287) in Intel's Trust Domain Extensions (TDX) module allows a Ring-0 system software adversary with high privileges to breach Trust Domain isolation boundaries, enabling information disclosure and privilege escalation. Affects select Intel platforms running TDX with a high-complexity, locally-executed attack path - no user interaction required. No public exploit identified at time of analysis, but the confidential-computing trust model is fundamentally undermined if exploited: an adversary with hypervisor-level access could read or modify memory intended to be protected from exactly that privilege tier.

Privilege escalation in Intel PROSet/Wireless WiFi Software for Windows exposes local systems to code execution by unprivileged attackers via a Ring 2 (device driver layer) improper access control flaw. Any local process with no privileges required and no user interaction can leverage the driver's failure to enforce access boundaries to achieve local code execution, with follow-on high confidentiality impact on the broader system - consistent with a kernel-level scope change. No public exploit identified at time of analysis, and no CISA KEV listing; however, the low complexity and zero-privilege requirement make this a credible post-compromise escalation vector for threat actors with any form of local code execution already established.

Improper access control in Intel PROSet/Wireless WiFi Software device drivers (Ring 2) allows a local unprivileged process to cause a denial of service affecting both the wireless subsystem and, to a lesser extent, downstream system integrity. Affected systems running Intel wireless drivers are exposed to any unprivileged local code - no authentication, no elevated privileges, and no user interaction are required. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in the CISA KEV catalog.

Improper access control within Ring 3 (user application space) of Intel processors permits privilege escalation from authenticated local user-level access to higher system privilege levels, with high confidentiality and integrity impact on the vulnerable system. Exploitation demands local access, low-privilege authentication, high attack complexity, and specialized internal knowledge of Intel processor microarchitecture internals - substantially narrowing the realistic attacker population. No public exploit code has been identified and no CISA KEV listing exists at time of analysis, consistent with a threat relevant primarily to sophisticated, targeted adversaries.

Typebot's webhook resume endpoint exposes an insecure direct object reference flaw that allows any authenticated user holding read access to at least one typebot to inject arbitrary JSON payloads into a suspended webhook session owned by a completely different typebot on the same instance. The handler validates authorization against the caller-supplied typebotId but then resolves the session result record solely by resultId without binding it to the authorized typebot, enabling an attacker to mix a legitimately authorized typebotId and blockId with a foreign live resultId to hijack cross-tenant execution flow and advance the victim's business logic. No public exploit has been identified at time of analysis; vendor-released patch version 3.17.0 is available and resolves the flaw.

Cross-workspace credential injection in Typebot's Google Sheets OAuth callback allows an authenticated attacker to plant Google Sheets credentials into workspaces they do not own, and - if target IDs are known - attach those credentials to blocks inside victim Typebots. The root cause is that the OAuth callback decodes and blindly trusts a client-supplied, unprotected base64 JSON state parameter without verifying the authenticated user holds write access to the referenced workspaceId or typebotId. All Typebot versions prior to 3.17.0 are affected; no public exploit has been identified and this vulnerability is not listed in the CISA KEV catalog.

Privilege escalation in CamaleonCMS 2.9.2 and earlier allows any authenticated low-privileged user to overwrite administrator passwords and achieve full site takeover via a parameter confusion flaw in the UsersController's updated_ajax endpoint. The authorization filter and the action body each resolve the target user from a different parameter key, enabling an attacker to pass their own ID to satisfy the self-authorization check while simultaneously directing the mutation at any victim account. No public exploit tool has been identified at time of analysis, but the upstream fix commit is available on GitHub (PR #1185, commit 2634503), with a formally tagged patched release not yet independently confirmed.

Unauthorized cross-workspace Google Sheets credential exposure in Typebot prior to version 3.17.0 allows any authenticated user to call the `POST /api/sheets/getSheets` endpoint with an arbitrary workspace ID, bypassing membership checks entirely. The handler decrypts and returns the target workspace's stored Google Sheets OAuth tokens along with spreadsheet metadata (sheet names, IDs, and column headers), constituting a direct credential theft vector against any workspace with a Google Sheets integration configured. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the low exploitation complexity makes this a credible insider or multi-tenant threat.

Account takeover in Rapid7 Velociraptor is possible when the platform is configured to use an external OIDC Identity Provider for authentication. Velociraptor maps OIDC email claims directly to internal usernames without validating the IdP's email_verified flag, enabling an attacker with any account on the same IdP to change their registered email address to match a target user's and seamlessly inherit that user's Velociraptor session and privileges. Given Velociraptor's role as a DFIR and endpoint monitoring platform, successful exploitation could expose sensitive forensic data, endpoint telemetry, and incident response artifacts. No public exploit code has been identified at time of analysis.

Webhook signature verification bypass in AutoGPT Platform before 0.6.70 allows unauthenticated remote attackers to trigger execution of secret-protected generic webhook graphs as their registered owner. The flaw stems from the ingress router selecting the webhook manager from the untrusted URL provider path segment rather than from the stored webhook record, meaning a request routed through the /compass/ path invokes CompassWebhookManager's inherited no-op verify_signature instead of GenericWebhooksManager.verify_signature, neutralizing the X-Webhook-Secret guard entirely. No public exploit or CISA KEV listing has been identified at time of analysis, but the fix is available in the confirmed release v0.6.70.

Cross-tenant authorization bypass in SeaweedFS filer JWT path authorization allows any authenticated tenant to read and write data belonging to sibling tenants whose path names share a string prefix. Versions prior to 4.24 are affected: a scoped JWT issued for /tenant1 inadvertently passes the authorization check for /tenant1234, /tenant1-old, and any other path that begins with the same character sequence, because the check used Go's raw strings.HasPrefix rather than a path-component boundary comparison. No public exploit code has been identified at time of analysis, but the bypass is mechanically trivial for any holder of a valid scoped token and the exact attack patterns are documented in the fix's test suite.

Authentication bypass in SeaweedFS filer before 4.24 exposes the SeaweedIdentityAccessManagement gRPC service without any credential check whenever jwt.filer_signing.key is left unset, which is the default. Any client able to reach the filer's gRPC port can invoke CreateUser, CreateAccessKey, PutPolicy, and related IAM RPCs to mint their own access keys and obtain S3 administrative control over the storage cluster. Rated CVSS 9.8; no public exploit identified at time of analysis, though the upstream fix commit and PR are public.

Cross-tenant IDOR in Roskus Prospero Flow CRM's ticket management component allows any authenticated user - regardless of company affiliation - to read full ticket content (titles, descriptions, attachments), hijack tickets by overwriting their company_id, and delete tickets belonging to any other tenant on the shared instance. The root cause is a missing authorization boundary in three distinct Eloquent query paths that retrieve tickets by numeric ID without scoping results to the authenticated user's company, compounded by the delete controller accepting a generic HTTP request class that bypassed the application's own permission gate entirely. No public exploit code or CISA KEV listing exists at time of analysis; however, the Secur0 advisory documents the attack surface with sufficient detail for reproduction, and the CVSS 4.0 score of 8.6 reflects the genuine severity of multi-tenant isolation failure.

Privilege escalation to administrator in Rapid7 Velociraptor (all versions before 0.77.2) allows an authenticated low-privileged GUI user to impersonate any other user, including admins, by supplying a crafted 'Grpc-Metadata-USER' header, resulting in full account takeover. The flaw stems from the gRPC/GUI layer trusting a client-supplied identity header instead of the authenticated session. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV, but the fix is trivial to reverse-engineer once the header name is known.

Unauthenticated remote code execution affects Siemens SIMATIC IoT2050 Advanced (6ES7647-0BA00-1YA2) gateways running Industrial OS with Node-RED installed, in all versions prior to V4.3.4.1. The Node-RED HTTP interface ships without authentication, exposing programming nodes that run system commands, so any attacker with network reachability can push malicious flows and execute code as the highest-privilege user. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the CVSS 10.0 rating and trivial exploitation make this a top-priority patch for exposed devices.

Broken access control in Craft CMS 5.0.0-RC1 through 5.10.5 lets a control-panel user holding only the viewCategories permission permanently reorder and re-parent categories through the structures/move-element action, despite lacking saveCategories. Because category URIs are derived from structure position, an attacker can silently change category URLs and those of all descendants and corrupt taxonomy-driven navigation menus. Reported by VulnCheck with no public exploit identified at time of analysis; the flaw is an integrity-only bypass fixed in 5.10.6.

Credential authorization bypass in n8n's HTTP Request node allows an authenticated member with edit access to a shared workflow to silently exfiltrate or use another user's credential by setting the credential type field via a dynamic expression. The pre-execution permission check evaluates the unresolved expression string rather than its runtime-resolved value, causing the ownership check to be skipped entirely while the actual credential is loaded at execution time. Versions 1.123.67, 2.31.5, and 2.32.1 contain the fix; no public exploit has been identified at time of analysis.

Credential exfiltration in n8n's AI and LLM workflow nodes allows low-privileged users with use-only access to shared credentials to bypass the 'Allowed HTTP Request Domains' allowlist and redirect credential secrets to attacker-controlled infrastructure. Affected are all n8n npm installations before version 2.31.5 and the 2.32.0 release (fixed in 2.32.1), where at least one credential has domain restrictions configured and is shared with non-owner users. No public exploit code has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog, but the attack is low-complexity for any insider or compromised low-privilege account.

Credential exfiltration in n8n's workflow automation platform allows any user with Editor access to a shared workflow to bypass authorization checks and use or exfiltrate credentials they are not permitted to access. The flaw exists because n8n validates credential permissions only for a node's top-level credential references, not for credentials embedded inside an Execute Sub-workflow node's inline workflow JSON (Source = Parameter); the embedded reference passes both save-time and runtime validation and resolves using the parent workflow's project context. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 7.2 reflects a credible, low-complexity path to high-confidentiality impact when workflow sharing is in use.

Server-side authentication bypass in FreeRDP 3.x (confirmed through 3.27.1) allows an unauthenticated remote attacker to obtain a fully authenticated RDP session without supplying any credentials, GUID, or reconnect cookie when the server has RdstlsSecurity enabled. The flaw combines PDU-type confusion - the server routes inbound messages based solely on the client-supplied wire pduType without enforcing handshake state - with a calloc-zeroed result code that maps directly to RDSTLS_RESULT_SUCCESS, so sending a Capabilities PDU in place of the required Authentication Request PDU produces an unconditional authentication success response. No public exploit code or CISA KEV listing has been identified at time of analysis; the upstream fix commit is confirmed but a released patched version was not independently verified at advisory time.

Unauthenticated account creation in Swing Music 3.0.0 exposes a critical access control gap: the POST /auth/profile/create endpoint is explicitly allowlisted from JWT verification, enabling any network-reachable attacker to register arbitrary user accounts with no credentials. Once registered, the attacker-controlled account can be used to authenticate and access server-protected functionality such as media libraries or administrative features. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, though the low-complexity network vector makes opportunistic exploitation straightforward against exposed instances.

Unauthenticated remote access to all contact form submissions, including personally identifiable information, is possible in CSZ CMS 1.3.2 due to a broken access control flaw in the admin form-submission viewer. The endpoint omits an authentication check entirely, and the underlying framework authentication helper fails open rather than denying access by default - meaning the bypass is a structural failure, not a simple missing decorator. No public exploit code or active exploitation has been identified at time of analysis, but the trivial exploitation conditions (no credentials, no special configuration) make this a realistic data-exposure risk for any internet-facing CSZ CMS deployment.

Unauthenticated remote access to invoice PDFs in IDURAR ERP CRM 4.1.0 and earlier exposes customer PII due to the /download Express router being mounted globally without authentication middleware, constituting a broken access control flaw (CWE-284). Any internet-reachable attacker can retrieve financial documents by enumerating MongoDB ObjectIds, requiring no credentials, session token, or user interaction. No active exploitation has been confirmed via CISA KEV, and no public exploit code is identified in the available intelligence, though the attack requires only basic HTTP requests and ObjectId pattern knowledge.

Broken access control in Ghost Foundation Ghost 5.x enables any authenticated Author-role user to delete posts owned by other users, including content published by Editors and Administrators. The authorization failure originates in the post model's permissible() cascade, where the combined isAuthor-and-isDestroy condition is not handled, causing the guard to fall through and approve the deletion. No public exploit code has been identified at time of analysis, but the low attack complexity and minimal privilege requirement mean the flaw is trivially abusable by any Author-role account holder on the platform.

Broken access control in BadChoice Handesk (all versions through 2026-07-10) permits any authenticated agent to modify, escalate, or corrupt ticket records belonging to teams they have no membership in, by directly targeting the TicketsController@update endpoint. The endpoint performs neither an authorize() policy check nor a team-scoped ownership validation, meaning a low-privilege agent account is the only barrier to cross-team data tampering. No public exploit has been identified at time of analysis, but exploitation requires only a valid agent credential and a single crafted HTTP request, making this a low-friction privilege abuse risk in any multi-team deployment.

Cross-team lead record overwrite in BadChoice Handesk (all versions through 2026-07-10) is exploitable by any authenticated agent via the LeadsController@update endpoint, which performs no team-ownership authorization check. The Lead model's $guarded property is set to an empty array, disabling Laravel mass-assignment protection and allowing the attacker to set any column value on any lead record regardless of team boundary. No public exploit code or CISA KEV listing has been identified at time of analysis, but the PR:L/AC:L vector makes this trivially exploitable by any insider or compromised agent account in a multi-team deployment.

Broken access control in Peppermint Lab's Peppermint helpdesk platform (through commit ba6e217) allows any authenticated non-administrative user to overwrite platform-wide OIDC/SSO configuration via an unprotected endpoint, enabling full credential harvesting against all platform users. The configuration endpoint applies new OIDC issuer settings without performing any administrative role check (CWE-284), meaning a low-privilege helpdesk agent can silently redirect all SSO logins to an attacker-controlled identity provider. CVSS scores 8.8 (High); no public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.

Broken access control in Peppermint helpdesk (through commit ba6e217) allows any authenticated user to read, modify, or delete tickets, clients, and users owned by any other account. The root cause is that the `Config.roles_active` flag defaults to `false` on all default installations, rendering every permission check on ticket, client, and user handlers a no-op - ownership and administrative access controls are silently bypassed. No public exploit code or active exploitation has been identified at time of analysis, but the flaw is trivially exploitable by any user with a valid account on a default-configured instance.

Insecure direct object reference in Attendize's bulk attendee import endpoint allows authenticated event organizers to inject attendee records into events owned by arbitrary third-party accounts. The postImportAttendee endpoint resolves target events by ID alone, without validating that the requesting organizer has ownership of the referenced event. All Attendize deployments through commit 9289acb are affected; no public exploit code or CISA KEV listing exists at time of analysis, but exploitation requires only a valid organizer account.

Insecure direct object reference in Attendize through commit 9289acb enables any authenticated event organiser to inject attendees and fraudulent orders into events belonging to other accounts via the postInviteAttendee endpoint. The root cause is a missing account-ownership check in the event lookup query - the endpoint resolves events by ID alone without verifying the requesting organiser's ownership. Exploitation allows an attacker to corrupt cross-account financial records and event data, with no public exploit identified and no CISA KEV listing at time of analysis.

Unauthenticated remote write to any contact record is possible in OpenSignLabs OpenSign through version 2.37.0 via the updatecontacttour Parse cloud function, which performs no authentication or authorization checks before accepting and applying updates to arbitrary contact records. Any internet-reachable deployment is vulnerable to data corruption or overwrite of contact records for all users system-wide without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability's zero-prerequisites nature and straightforward exploitation model make it a realistic target for automated abuse.

Unauthenticated contact record enumeration in OpenSignLabs OpenSign through 2.37.0 exposes all stored personally identifiable information to remote attackers without credentials. The `getcontact` Parse cloud function executes with `useMasterKey`, which bypasses Parse Server's native access control layers (ACLs and Class-Level Permissions), and contains no compensating authentication or authorization logic. Any network-reachable attacker can call this function, supply arbitrary object IDs, and retrieve full contact records including PII at scale. No public exploit has been identified at time of analysis, and no KEV listing exists.

Unauthenticated remote attackers can invoke the stripeCreateIntent GraphQL mutation in Chaskiq (through commit 46dfdd1) without any session or credential, enabling manipulation of Stripe payment intents for any tenant on the platform. The root cause is CWE-306 (Missing Authentication for Critical Function): the mutation bypasses all authentication and authorization checks, exposing a financial operation to the open internet. No public exploit or CISA KEV active exploitation has been identified at time of analysis, but the trivially low attack complexity (AV:N/AC:L/PR:N/UI:N) means any internet-reachable instance with Stripe configured is structurally exploitable.

Unauthenticated remote access to Stripe Billing Portal sessions in Chaskiq through commit 46dfdd1 allows any attacker to mint valid customer portal sessions for arbitrary tenants by invoking the `stripeCustomerPortal` GraphQL mutation without credentials. The mutation performs zero authentication or tenant-ownership checks before calling the Stripe API, enabling cross-tenant subscription manipulation - including plan changes and cancellations - against any Chaskiq-hosted tenant with Stripe Billing configured. No public exploit code has been identified at time of analysis, though the attack surface requires only network access and knowledge of a target tenant identifier.

Portainer CE through 2.44.0 exposes root-level Docker host access to any authenticated low-privileged user via a URL path normalization flaw in the Docker proxy endpoint. The authorization middleware evaluates a non-canonical request path (e.g., percent-encoded slashes, double slashes, or traversal sequences) differently from the proxy layer that ultimately forwards it to the Docker daemon - allowing crafted requests to bypass all access controls while executing with full Docker API privileges. No active exploitation has been confirmed (no CISA KEV listing) and no public exploit code has been identified at time of analysis; EPSS data was not provided in the source intelligence.

Authorization bypass in Commvault CommServe allows remote attackers to invoke a limited set of command-execution operations without passing the intended authorization checks, per Commvault security advisory CV_2026_07_9. The flaw carries a CVSS 4.0 base score of 9.2 with high impact to confidentiality, integrity, and availability, and affects Commvault Cloud deployments across the CommServe, Web Server, Command Center, MediaAgents, Clients, and HyperScale X components. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Authorization bypass in Commvault CommServe permits attackers to circumvent the command-execution allowlist, gaining unsanctioned command execution across the backup-management control plane. Because CommServe orchestrates the entire Commvault environment, a successful bypass can cascade to Webservers, Command Center, Media Agents, Clients and HyperScale X, threatening confidentiality, integrity and availability of protected data. Rated CVSS 4.0 9.2 (critical) by Commvault; no public exploit identified at time of analysis and it is not listed in CISA KEV.

IIOP NameService in Red Hat JBoss Enterprise Application Platform (EAP) accepts bind operations without authentication, allowing unauthenticated network attackers to register malicious CORBA object references under arbitrary JNDI names. When legitimate clients subsequently perform JNDI lookups, they resolve the attacker's malicious Object Request Broker (ORB), enabling man-in-the-middle interception of CORBA/RMI-IIOP invocations or denial-of-service on dependent application flows. EPSS data was not provided; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.

Undertow's AJP listener unconditionally trusts the ssl_cert and is_ssl AJP request attributes without requiring a shared-secret, allowing an unauthenticated remote attacker with direct TCP access to port 8009 to impersonate any X.509 client certificate identity and bypass CLIENT-CERT mutual TLS authentication entirely. Deployments where Undertow acts as a back-end behind a reverse proxy - with CLIENT-CERT authentication enforced at the proxy layer but the AJP port exposed on an internal network - are directly at risk of identity spoofing and authorization bypass. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog; however, the bypass primitive is architecturally simple for any attacker who has obtained internal network access to the AJP port.

Privilege escalation in the `openvt -u` utility allows a local low-privileged attacker to obtain passwordless root login on Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. The flaw lies in `authenticate_user()`, which resolves VT ownership via `stat("/proc/<pid>/fd/0")` - a call that follows the symlink to the underlying TTY device node rather than inspecting the owning process, causing the check to read the device node's UID rather than the process owner's UID. When a privileged user logs out and TTY device node ownership reverts to root or the getty owner while an attacker's process still holds fd 0 on that TTY, the check incorrectly authorizes a passwordless `login -f root` execution. No public exploit is identified at time of analysis and there is no CISA KEV listing, but the root-level impact makes this a high priority for environments using the affected `kbrequest`/init deployment pattern.

Privilege escalation in MRTG (Multi Router Traffic Grapher) allows a local low-privileged attacker to gain elevated file ownership on the host system. When the MRTG daemon is launched as root and then drops privileges, a CWE-59 symlink-following flaw in PID file handling lets an attacker pre-place or manipulate a symlink at the expected PID file path, causing the root process to change ownership of an arbitrary existing file to the daemon user. Affected platforms include Red Hat Enterprise Linux 6 through 10; no public exploit code or CISA KEV listing has been identified at time of analysis.

Insecure Direct Object Reference in Chiline Cloud (Inventec Appliances) versions up to and including 4.5.9 exposes sensitive user data to unauthenticated remote attackers. By manipulating a specific request parameter - likely a user identifier or resource key - an attacker can bypass authorization checks and read account data belonging to arbitrary other users. Reported by TWCERT and catalogued under EUVD-2026-55925, no public exploit code or active exploitation has been confirmed at time of analysis, though the trivial exploitation conditions (network-accessible, no authentication, no user interaction) make this a high-priority disclosure risk.

Missing authorization checks in SAP ABAP Developer Tools (the Eclipse-based IDE for ABAP development) allow any low-privileged SAP user to execute unauthorized database operations against SAP NetWeaver AS ABAP backends. The flaw spans a wide range of SAP_BASIS releases (750 through 920) and yields full confidentiality, integrity, and availability compromise of the ABAP application layer - including the ability to read sensitive business data, modify application records, and disrupt legitimate user access. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and broad version coverage elevate real-world risk considerably for enterprises running ADT-connected NetWeaver systems.

Unauthenticated remote access to SAP Manufacturing Integration and Intelligence (MII) scheduling functions is possible due to a missing authorization check on scheduling-related API endpoints. Any network-reachable attacker without credentials can retrieve, create, modify, or delete scheduling data managed by the application, impacting confidentiality, integrity, and availability at a low severity level each. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the trivial exploitation conditions - no authentication, no user interaction, low complexity - lower the barrier to opportunistic abuse significantly.

Missing authorization on the Cost Servlet in SAP Manufacturing Integration and Intelligence (SAP MII) exposes backend operations to unauthenticated remote attackers via crafted HTTP requests with specific parameter values. Successful exploitation grants read, create, modify, and delete access to application-managed business data, producing a limited but tripartite impact across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at this time, though the zero-privilege network vector lowers the bar for opportunistic probing.

SSO-based account takeover in usememos Memos v0.27.1 lets a remote, unauthenticated attacker impersonate any user by exploiting the ssoCredentials path of the SignIn handler (server/router/api/v1/auth_service.go), which matches a federated identity solely on an attacker-controllable identifier (e.g. email or username) instead of the identity provider's stable subject claim. Any deployment that has an OIDC/OAuth SSO provider enabled is affected, and a successful attack yields full control of the targeted account, including potentially administrative accounts. The flaw carries CVSS 9.8 and CWE-287; there is no public exploit identified as weaponized at time of analysis, though a referenced GitHub gist appears to be a researcher write-up, and EPSS is low at 0.22%.

Broken access control in ERPNext's accounts module permits authenticated low-privilege users to invoke privileged write operations across five functions - merge_account, pause_job_for_doc, trigger_job_for_doc, change_release_date, and update_cost_center - without any server-side permission enforcement. All v15 releases prior to 15.112.0 and all v16 releases prior to 16.22.0 are affected. An attacker with any valid ERPNext session can directly call these whitelisted API endpoints to corrupt financial accounts, payment reconciliation jobs, purchase invoices, and cost centers beyond their assigned role, with no public exploit identified at time of analysis.

Broken access control in ERPNext's Accounts Receivable and Payable report engine allows any authenticated user to read cross-company financial data they are not authorized to view. The `ReceivablePayableReport.prepare_conditions()` method fails to enforce Customer and Supplier user permissions against the Payment Ledger Entry dynamic-link party field, meaning permission boundaries set via Frappe's user permission system are silently bypassed for this report path. Fixed in versions 15.112.0 and 16.23.0; no public exploit identified at time of analysis.

Privilege escalation in Red Hat OpenShift AI's Data Science Pipelines component allows authenticated tenants to bypass authorization controls in the setDefaultServiceAccount function by submitting a crafted CreateRun request that references a more privileged ServiceAccount than they are entitled to use. Successful exploitation enables the tenant's pipeline containers to run with elevated Kubernetes RBAC permissions, resulting in cross-namespace secret disclosure and the ability to execute commands inside other tenants' pods. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.

Credential derivation in Red Hat OpenShift AI's Data Science Pipelines Operator allows unauthenticated remote attackers to predict MariaDB root/user passwords and MinIO access/secret keys by exploiting a cryptographically weak PRNG (CWE-338). Any attacker who can reach the MinIO Route or MariaDB Service over the network can compute valid credentials without prior authentication, then access all pipeline artifacts and metadata stored in the system. No active exploitation is confirmed and no public exploit code has been identified at time of analysis, but the CVSS 7.5 High rating with AV:N and PR:N reflects a no-authentication-barrier condition against exposed services.

Privilege escalation in Red Hat OpenShift AI (RHOAI) training operator overlay allows any namespace editor to manage TrainJob resources beyond their intended authorization scope. The RHOAI overlay incorrectly injects trainjobs CRUD permissions into the native Kubernetes edit ClusterRole, violating the principle of least privilege. When chained with a companion flaw (TRN-01) that permits arbitrary pod configuration within TrainJobs, a remote attacker holding namespace editor credentials could escalate to arbitrary code execution - no public exploit is identified at time of analysis, and KEV listing has not been confirmed.

Authorization bypass in Feast's materialization API endpoints within Red Hat OpenShift AI (RHOAI) permits full re-materialization of all feature views by sending a crafted request that omits the feature_views field, circumventing permission checks. The consequence is a multi-tenant Denial of Service through data corruption and significant resource exhaustion, impacting all tenants sharing the deployment. No public exploit code has been identified at time of analysis, but the bypass mechanism is straightforward - a structural omission in the request body - making independent rediscovery likely for any attacker with API access.

Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.

Authentication bypass in TrustyAI Service (TAS) within Red Hat OpenShift AI (RHOAI) exposes the backend API to any pod on the cluster network without requiring valid credentials. The CVSS vector (AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that an attacker with a pod on the cluster-such as through a compromised workload or a malicious tenant pod in a multi-tenant deployment-can read, modify, delete, or poison AI model monitoring data and configurations with no additional barriers. No public exploit code or CISA KEV listing has been identified at time of analysis, but the root cause (CWE-306: Missing Authentication for Critical Function) means exploitation is trivially simple once cluster network adjacency is established.

Authentication bypass in the Models-as-a-Service (MaaS) API component of Red Hat OpenShift AI (RHOAI) lets any pod already running in the cluster impersonate arbitrary users by forging the X-MaaS-Username and X-MaaS-Group HTTP headers, which the service trusts without independent verification. Because the MaaS API performs no first-party authentication and defers entirely to a Kuadrant AuthPolicy gateway that can be circumvented, a low-privileged workload can mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and exfiltrate model-access configuration - a full cross-tenant privilege escalation. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the 9.9 CVSS reflects near-total impact.

The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.

Cross-channel message deletion in Spacebar Server (all commits before 8d126f4) permits authenticated users holding MANAGE_MESSAGES permission in any channel to delete messages residing in channels they do not control. Both the single-delete and bulk-delete API handlers failed to scope their database queries to the channel_id present in the request path, allowing attacker-supplied message IDs from foreign channels to be processed and destroyed. A publicly available exploit exists, with the root cause and fix confirmed by the upstream security advisory GHSA-62g6-28hv-h6hc; no CISA KEV listing has been issued at time of analysis.

Incomplete authorization in Dokploy's WebSocket handlers prior to v0.29.13 allows any authenticated organization member to obtain root terminal access to servers and read logs or statistics for services they were explicitly denied access to. The four affected handlers (terminal.ts, docker-container-terminal.ts, docker-container-logs.ts, docker-stats.ts) verify organization membership but never call checkServiceAccess, getAccessibleServerIds, or accessedServices, nullifying all fine-grained role-based access controls. No public exploit or CISA KEV listing exists; however, the attack requires only a valid low-privilege organization account, making this a meaningful privilege escalation risk in any multi-tenant Dokploy deployment.

Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.

GitHub App provider injection in Dokploy PaaS (prior to v0.29.13) allows unauthenticated remote attackers to insert attacker-controlled GitHub App credentials - including client_secret, webhook_secret, and PEM private key material - into any target organization's configuration by forging the state parameter in the GitHub OAuth callback route. The route /api/providers/github/setup performed no session authentication (CWE-306), blindly trusting organizationId and userId values supplied by the caller in the state query parameter. No public exploit identified at time of analysis; a vendor-released patch is confirmed available as v0.29.13.

Interactive host-shell access in Dokploy prior to 0.29.13 is obtainable by any authenticated platform user due to a missing authorization check in the WebSocket terminal handler. The handler at apps/dokploy/server/wss/terminal.ts validates the session token but never checks whether the user holds an organization role or server-access grant before spawning a terminal for serverId=local, yielding full interactive shell access on the Dokploy host. No confirmed active exploitation or public exploit code has been identified at time of analysis, but the public security advisory and fix diff make reconstruction trivial for any authenticated user.

Privilege escalation via missing authorization in Dokploy, a self-hostable Platform-as-a-Service, lets any authenticated organization member open a root shell inside arbitrary containers on a self-hosted instance. The /docker-container-terminal WebSocket handler authenticated the caller but never checked the attacker-supplied containerId against the caller's role, organization, or service scope before invoking docker exec. Fixed in 0.29.13; no public exploit identified at time of analysis, though the upstream fix commit is public.