Authentication Bypass
Monthly
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 lets an unauthenticated attacker run arbitrary code and read or tamper with other users' chat sessions by reaching publicly shared MCP (Model Context Protocol) project endpoints. The flaw stems from Langflow failing to enforce its public-flow security restrictions and session-isolation controls, so exposure exists once a project is shared publicly via an MCP endpoint. No public exploit is identified in the provided data, and the item is not listed in CISA KEV.
Sensitive health-data exposure in the Lenovo Health Android application (distributed exclusively in the Chinese market) stems from hardcoded credentials (CWE-798) that let an attacker access users' health-related information without legitimate authentication. Reported by Lenovo PSIRT and tracked under a single Lenovo advisory, it carries a CVSS 4.0 base of 9.3 driven by high confidentiality impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Local privilege escalation in Lenovo Rescue and Smart Assistant (LMSA) enables a local authenticated user to execute arbitrary code with elevated privileges by exploiting a capture-and-replay authentication bypass (CWE-290) in the application's privileged service layer. The vulnerability is strictly local in scope per the CVSS 4.0 vector (AV:L/PR:L), limiting the threat to attackers who already hold a standard user account on an affected Lenovo device. Lenovo has published advisory LEN-217409 with remediation guidance; no public exploit has been identified at time of analysis.
IBM WebSphere Application Server 8.5 and 9.0 contain improper authentication controls that allow an attacker who already holds a local, low-privileged foothold on the server to bypass security checks and escalate privileges. Successful exploitation yields high confidentiality and integrity impact — protected resources and configuration can be read and modified — though availability is unaffected per the CVSS vector. No public exploit code has been identified, EPSS is very low at 0.12% (3rd percentile), the issue is not in CISA KEV, and a vendor patch is available from IBM.
Authentication/authorization bypass in rclone's dynamic serve interface (versions 1.70.0 through 1.75.0) lets remote attackers reach a fixed filesystem instead of the per-request backend the operator intended. When an FTP or S3 server is spun up via the serve/start RC (remote control) API with a per-server proxyOpt.AuthProxy, the FTP and S3 constructors mistakenly consult the empty process-global proxy.Opt.AuthProxy, so the request-local auth proxy is silently ignored: FTP accepts anonymous logins with any password against the fixed VFS, and S3 with AuthKey serves the fixed RC fs rather than the proxy-selected backend. There is no public exploit identified at time of analysis, and this is not in CISA KEV. Fixed in 1.75.1.
Authentication bypass in rclone's S3 server mode (rclone serve s3) allows any unauthenticated network attacker to impersonate arbitrary S3 access keys. When rclone serve s3 is started with --auth-proxy but without --auth-key, authPairMiddleware registers whatever accessKeyID the client chooses against an empty s3Secret, and gofakes3 then validates the request's SigV4 signature against that same empty secret - so an attacker can pick any access key, sign with an empty secret, and reach whatever backend the auth-proxy script resolves for that identity. Fixed in rclone 1.75.1; no public exploit identified at time of analysis, though the vendor security advisory (GHSA-xwwr-4h3p-r22c) and fix commit are public.
Arbitrary code execution in Dell ThinOS 10 (all builds prior to 2605_10.2616) allows a remote, unauthenticated attacker to run code within the application context of the affected thin client, per Dell advisory DSA-2026-389. The root cause is a protection mechanism failure (CWE-284) that bypasses an intended security control rather than exploiting a memory-corruption bug directly. No public exploit is identified at time of analysis and the CVE is not in CISA KEV, but the network-reachable, no-authentication attack profile makes it high priority.
HTTP/1 request-target parsing in Traefik prior to 2.11.57 and 3.7.13 allows unauthenticated remote attackers to send a rootless URL target (e.g., `http:example.com/admin`) that Go's HTTP library stores in URL.Opaque rather than URL.Path, leaving URL.Path empty. Traefik's routing engine, forwardAuth middleware, and access logger all evaluate against the normalized empty path (treated as `/`), while URL.RequestURI() gives URL.Opaque precedence when forwarding — meaning the backend receives the original opaque target verbatim. The practical consequence is cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion, all requiring no authentication or special client configuration. No public exploit has been identified at time of analysis, though the patch PR includes test cases demonstrating the attack technique in full detail.
Backend connection hijacking in Traefik reverse proxy (2.11.0 through 2.11.56 and 3.0.0 through 3.7.12) lets an unauthenticated remote client impersonate another user over HTTP/3. Because the HTTP/3 entrypoint never calls service.AddTransportOnContext, the kerberosRoundTripper falls back to a shared backend transport instead of one bound to each frontend connection, so when a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can reuse a backend connection already authenticated for a victim, read the victim's data, and act as the victim without ever obtaining their credentials. No public exploit is identified at time of analysis, though the fix PR ships a regression test that effectively demonstrates the flaw.
Traefik's header-security defenses (aliasHeadersStrategy, underscoreHeadersStrategy, forwardedHeaders) inspect req.Header but not req.Trailer, allowing unauthenticated clients on versions 3.2.0 through 3.7.12 to smuggle security-sensitive header values through HTTP/1.1 chunked trailers or HTTP/2 trailers. When retry or buffering middleware is active in the routing chain, attacker-controlled trailer values become accessible before the request is cloned for the backend; backends that merge trailers into their header namespace then receive the spoofed values, bypassing Traefik's documented delete or reject behavior. No public exploit code has been identified and this CVE is not in CISA KEV, but the impact on identity and routing integrity at the backend is classified high by the CVSS 4.0 subsequent-system metrics.
CyberPanel before 3.0.5 allows attackers who have obtained an administrator's password to bypass two-factor authentication entirely on API endpoints by deriving valid API tokens from the password alone, without satisfying the TOTP requirement. This reduces 2FA-protected admin accounts to effective single-factor authentication at the API layer, enabling full administrative operations or session creation. The fix is available in version 3.0.5 per the GitHub security advisory; no public exploit or active exploitation has been identified at time of analysis.
Authentication bypass in Traefik v3.7.0 through v3.7.11 lets remote unauthenticated attackers reach protected Kubernetes backends when an Ingress uses the ingress-nginx compatibility provider with both an authentication annotation and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation. The provider generates a host-only 'sibling' router carrying only a non-terminal RedirectRegex middleware that still routes to the protected backend, so a crafted request evades the redirect and is proxied without any annotation-derived middleware. Reported by VulnCheck with a published advisory; no public exploit is identified at time of analysis, though the technique is fully documented and trivially reproducible.
Improper access control in Capgo (capgo.app) lets any holder of an ordinary full API key forge a trusted SSO provider by writing directly to the public.sso_providers table exposed via Supabase PostgREST, setting status='active' and enforce_sso=true without passing the backend provisioning route. This sidesteps the Enterprise-plan gate, Supabase Management API provider creation, DNS TXT domain-ownership verification, and the pending_verification→verified→active workflow, so an attacker can assert SSO enforcement for arbitrary unverified domains and disrupt normal login. All versions are affected, no patch was available at advisory time, and there is no public exploit identified at time of analysis beyond the VulnCheck write-up.
Capgo's MFA enforcement is defeated by an authentication assurance level (AAL) mismatch across two distinct code paths: the Edge JWT middleware (foundJWT() in supabase/functions/_backend/utils/hono_middleware.ts) accepts Supabase JWTs without inspecting the aal claim, and the direct RBAC path (checkPermissionPg() calling public.rbac_check_permission_direct() in rbac.ts) authorizes operations by user ID alone, bypassing the assurance-level check that public.verify_mfa() correctly enforces. An attacker holding only the victim's account password can authenticate, receive an aal1 JWT, exercise privileged RBAC operations without triggering any MFA challenge, mint a persistent app_admin API key, and modify production OTA channel configurations - all of which survive logout of the original aal1 session. No patched version has been released; all versions of capgo.app are affected, and the advisory includes a validated proof-of-concept demonstrating bundle swap on a production channel.
Improper authorization in Hikvision HikCentral Access Control V2.5.0 and below allows authenticated low-privilege users to invoke API endpoints restricted to higher-privileged roles, resulting in unauthorized access to sensitive data and limited system modification. The CVSS vector (PR:L, C:H, I:L) confirms the attacker requires only a valid low-privilege account but can achieve high confidentiality impact and limited integrity compromise across the network. No public exploit code or CISA KEV listing has been identified at time of analysis, though the straightforward nature of the authorization flaw (unenforced role checks on API routes) makes it readily exploitable by any insider or attacker who obtains basic credentials.
Unauthenticated remote control of GeoVision GV-LPC2211 license-plate-capture cameras (firmware V1.13) is possible because the PTZ control service is exposed on the network with no authentication (CWE-306). Any remote client that can reach the service can query PTZ state and, more critically, issue PTZ movement or raw serial commands to the device and its attached serial peripherals. CVSS is 9.4 and no public exploit has been identified at time of analysis, but the trivial network-reachable, unauthenticated nature makes exploitation straightforward.
Unauthenticated arbitrary WordPress option deletion in the zipMoney (Zip Co) Payments Plugin for WooCommerce before 2.4.0 lets remote attackers destroy site configuration and take the site offline. One front-end request handler performs no authorization checks and does not restrict which option name the caller supplies, so any unauthenticated visitor can delete critical wp_options entries. Publicly available exploit code exists and a vendor patch (2.4.0) is available; no active exploitation has been confirmed (not in CISA KEV).
Two-factor authentication bypass in the miniOrange 2FA WordPress plugin allows an attacker who has already obtained a victim's password to defeat the second factor through unlimited OTP brute-forcing. The plugin keys its attempt-rate limit to a client-controlled identifier rather than the target account, enabling an adversary to rotate that identifier and circumvent lockout entirely; a separate validation endpoint applies no rate limit at all. A publicly available exploit (WPScan) confirms practical exploitability against plugin versions below 6.3.1 and 19.3.
Unauthenticated arbitrary site-option deletion in the miniOrange 2FA WordPress plugin (versions 5.3.24 through before 6.3.1, and 18.0 through before 19.3) lets any visitor delete arbitrary wp_options entries because option names are taken directly from request input without validating a legitimate transaction. Deleting the right options can lock every administrator out of the WordPress dashboard or fully deactivate the two-factor plugin, stripping the site of its 2FA protection. Publicly available exploit code exists (WPScan) and a vendor patch is available; the flaw is rated CVSS 10.0.
Privilege escalation in the Bulk Password Reset WordPress plugin (all versions ≤1.3.3) allows any authenticated subscriber-level user to perform a full administrative account takeover. The plugin fails to validate the requesting user's identity before permitting bulk password changes and email-address updates, meaning an attacker can redirect an administrator's email to an attacker-controlled address, then invoke the standard WordPress password-reset flow to obtain reset credentials for that admin account. No public exploit code has been identified at time of analysis, but source code references from WordPress Plugin Trac directly expose the vulnerable functions at lines 44, 594, 659, and 679 of bulk_password_reset.php.
Pre-authentication queue deletion in Apache Artemis and Apache ActiveMQ Artemis allows unauthenticated remote attackers to destroy message queues by sending a crafted Openwire RemoveSubscriptionInfo command before or after the broker's authentication stage completes. The flaw affects every Apache ActiveMQ Artemis release from 1.0.0 through 2.44.0, and the rebranded Apache Artemis releases from 2.50.0 through 2.56.0, making it an extremely wide-scope exposure for the legacy version range. No public exploit code or CISA KEV listing has been identified at time of analysis, but the pre-authentication nature and low exploitation complexity make this a credible denial-of-service and data-loss vector in any internet- or intranet-exposed Artemis deployment.
Session hijacking in Apache ActiveMQ Artemis and Apache Artemis allows unauthenticated remote attackers to steal authenticated messaging sessions by sending a crafted CORE protocol SESSION_REATTACH packet, granting full control of an existing authenticated session without any credentials. The CORE protocol's session reattachment mechanism - designed for fault-tolerant HA reconnection - performs no identity verification, enabling any network-accessible attacker to impersonate legitimate connected clients. No public exploit or CISA KEV listing is identified at time of analysis, but the vulnerability spans the entire release history of Apache ActiveMQ Artemis (1.0.0 through 2.44.0), meaning essentially all historical deployments are affected.
Cluster credential exposure in Apache ActiveMQ Artemis and Apache Artemis allows a network-adjacent unauthenticated attacker to passively capture cluster administrative credentials during the initial peer-discovery handshake. Both the legacy Apache ActiveMQ Artemis lineage (versions 1.0.0 through 2.44.0) and the newer Apache Artemis distribution (versions 2.50.0 through 2.56.0) are affected, covering effectively the entire supported history of the project. An attacker positioned on the same network segment as a clustering deployment can intercept these credentials without any prior authentication, then use them to authenticate as a cluster administrator and gain full control over the message broker cluster. No public exploit code has been identified at the time of analysis.
Pre-authentication information disclosure in Apache ActiveMQ Artemis and Apache Artemis exposes cluster topology details to any unauthenticated remote attacker. The CORE protocol's SUBSCRIBE_TOPOLOGY request can be submitted before the broker enforces authentication, leaking cluster node configuration including internal broker addresses and cluster membership data. No public exploit code has been identified and it is not listed in CISA KEV, but the zero-prerequisite network vector makes automated scanning trivially feasible at scale.
Unauthenticated remote attackers can create arbitrary durable queues on Apache Artemis and Apache ActiveMQ Artemis brokers via the native CORE protocol due to missing authentication enforcement in the protocol handler. The vulnerability spans the entire Apache ActiveMQ Artemis release history (1.0.0 through 2.44.0) and the recently rebranded Apache Artemis fork (2.50.0 through 2.56.0), making the unpatched population potentially very large. Exploitation enables persistent unauthorized broker state manipulation and denial-of-service through storage and memory exhaustion, with no credentials or user interaction required; no public exploit code has been identified at time of analysis.
Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.
Unauthenticated remote task execution in @yeger/turbo-graph ≤ 2.8.8 allows any adjacent-network attacker to invoke arbitrary Turborepo tasks with the victim developer's OS-level privileges. Two independent implementation flaws combine: the embedded Next.js server omits the hostname argument to Node.js `.listen()`, causing the process to bind on all interfaces (`0.0.0.0`/`::`), while the `/api/run` HTTP endpoint reads task names from an attacker-controlled query string and passes them directly to `spawn()` with no authentication, CSRF protection, or allowlist check. No public exploit database entry or CISA KEV listing was identified, but a fully functional PoC with containerized end-to-end reproduction is included in the GitHub Security Advisory GHSA-2r5q-h53f-9rp3, significantly lowering the bar to exploitation.
OAuth and SCIM identity confusion in Open WebUI 0.6.41-0.10.x (SQLite-backed deployments only) allows unauthenticated remote attackers to hijack arbitrary stored user accounts, including administrator accounts, by presenting an OAuth subject claim containing SQL LIKE wildcard characters. SQLAlchemy's `JSON.contains()` on SQLite compiles to a substring LIKE match rather than an exact equality check, so a crafted `sub` claim such as `%admin%` can resolve to a different stored identity and cause the server to issue the attacker a valid session token for that identity. Vendor-released patch is available in version 0.11.1; no active exploitation has been confirmed.
Authentication bypass in MaxSite CMS versions 0.78 through 109.6 lets unauthenticated remote attackers forge valid administrator session cookies because the framework ships with a hardcoded session encryption key in application/config/config.php that installers never rotate. Using the publicly known key, an attacker computes a valid HMAC-SHA1 over a crafted ci_session cookie to impersonate an admin, defeating the is_login() and mso_check_allow() authorization checks. Publicly available exploit code exists (published by VulnCheck / EviL0rd); there is no evidence of active exploitation in CISA KEV at time of analysis.
Authentication bypass in SSSD's OIDC/IdP provider allows an authenticated IdP user whose subject identifier is a strict lexical prefix of a target user's identifier to impersonate that target user on SSSD-protected Linux systems. The root cause is `eval_access_token_buf()` passing the attacker-controlled identifier's length to `strncmp()`, reducing an identity equality check to a prefix test. All Red Hat Enterprise Linux releases (6-10) and OpenShift Container Platform 4 are affected when SSSD is configured to use an OIDC-based identity provider; no public exploit has been identified at time of analysis.
Unauthenticated firmware injection in Softish EarVision Android Application 1.3.1 paired with the C6 Ear Camera 1.3.1_Code 132 allows an adjacent attacker to deliver arbitrary, unsigned firmware to the physical ear camera device. By spoofing the C6 Ear Camera's wireless identity and eliciting a single user confirmation, the attacker triggers the application to transmit firmware over an update channel that performs neither endpoint authentication nor cryptographic signature verification (CWE-306). No public exploit code has been identified and the vulnerability is absent from the CISA KEV catalog; however, the adjacent-network vector and minimal social engineering threshold make exploitation realistic in clinical or close-proximity consumer settings.
Hardcoded or algorithmically derivable Wi-Fi credentials in the Softish C6 Ear Camera (firmware 1.3.1_Code 132) and companion EarVision Android application (1.3.1) allow an adjacent-network attacker to reconstruct the device's access-point password without authentication. Once the attacker connects to the camera's private Wi-Fi network, the live video stream, device management interfaces, status pages, and the firmware-update endpoint become fully accessible. The vulnerability was disclosed via CISA ICS-CERT advisory VA-26-251-01 and carries a CVSS 4.0 score of 8.7 reflecting high impact across confidentiality, integrity, and availability within the vulnerable system.
Device impersonation via unauthenticated camera spoofing in Softish's EarVision ecosystem exposes Android app users to man-in-the-middle attacks on adjacent networks. The C6 Ear Camera and its companion EarVision Android app (both at version 1.3.1) lack proper device authentication, allowing an adjacent network attacker to emulate the camera, intercept and manipulate device status responses, observe application traffic, and potentially trigger firmware-update behavior on the camera. Reported by CISA ICS-CERT; no public exploit code or KEV listing identified at time of analysis.
Hard-coded credentials in Dell Secure Connect Gateway (SCG) 5.0 expose both the Appliance and Application deployments to unauthenticated remote information disclosure. Any attacker who discovers or reverse-engineers the embedded static credentials - which cannot be changed by administrators - can authenticate to the gateway without valid user accounts and access sensitive information. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no privileges or user interaction; no public exploit or CISA KEV listing is recorded at time of analysis.
Account takeover in Snipe-IT before 8.7.0 allows low-privileged identity-provider users to hijack arbitrary Snipe-IT accounts by registering IdP usernames that are case or Unicode accent variants of existing victim usernames. The vulnerability exploits MySQL's default utf8mb4_unicode_ci collation, which conflates these variants during database lookups, enabling an attacker to be matched to a different user's record across all federated authentication paths - SAML, LDAP, and OAuth. Vendor-released patch 8.7.0 resolves the issue; no public exploit code or active exploitation has been identified at time of analysis.
Snipe-IT before 8.7.0 fails to apply the CheckUserIsActivated middleware to the API middleware group, allowing deactivated accounts to retain full REST API access through their existing Laravel Passport personal access tokens. Any deactivated user whose token has not been explicitly revoked can continue reading and writing assets, users, and licenses at their prior permission level, bypassing the offboarding control that correctly blocks web sessions. The most critical escalation path lets a deactivated account previously holding users.edit permission PATCH its own activation flag via /api/v1/users/{id} to permanently re-enable itself. No public exploit has been identified at time of analysis; a vendor-released patch is available in version 8.7.0.
Hard-coded credentials embedded in Dell Secure Connect Gateway 5.0 allow a remote, unauthenticated attacker to authenticate to the service using the static credentials and access sensitive information. Both the Appliance variant (all versions prior to 5.36.00.16) and the Application variant (all versions prior to 5.36.00.00) are affected, as confirmed by Dell advisory DSA-2026-382. No public exploit code or active exploitation has been identified, but CWE-798 credentials are static across all unpatched installations worldwide, meaning any party with knowledge of them can exploit any exposed instance without further effort.
Hard-coded credentials in Dell Secure Connect Gateway (SCG) 5.0 expose sensitive information to unauthenticated remote attackers across both the Appliance and Application deployment variants. The vulnerability (CWE-798) allows an attacker who discovers or possesses the embedded credentials to authenticate without authorization and access confidential data. Dell has released patched versions under advisory DSA-2026-382, and no public exploits or CISA KEV listing have been identified at time of analysis.
Unauthorized ADMIN access in Dell Secure Connect Gateway (SCG) 5.0 allows a remote unauthenticated attacker to replay a previously captured request indefinitely, forging ADMIN-level access and refresh tokens. Because the token-issuing flow performs no nonce validation and enforces no request expiry, a single intercepted request grants durable administrative control of the gateway. The Appliance edition is affected before 5.36.00.16 and the Application edition before 5.36.00.00; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Remote unauthenticated retrieval of expired one-time secrets in PasswordPusher before 2.11.1 is enabled by a TOCTOU race condition in the expire_after_views view-limit enforcement logic. By issuing multiple simultaneous HTTP requests to the show endpoint, an attacker can read a secret that was configured to self-destruct after a single view, defeating the core confidentiality guarantee the tool is designed to provide. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified, though the technique requires only basic HTTP concurrency tooling.
Authentication bypass in Parse Server's built-in LDAP authentication adapter (versions <= 8.6.87 and 9.0.0 through 9.10.1-alpha.6) lets an unauthenticated attacker who knows a valid directory username obtain a session token for that account, resulting in full account takeover. The adapter forwarded a client-supplied empty password to the directory and treated any non-error bind response as successful authentication, so a zero-length credential triggers an RFC 4513 unauthenticated-simple-bind that directories like Active Directory answer with success. No public exploit identified at time of analysis, but the flaw is trivial to trigger against affected LDAP-backed deployments.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application allows a network-positioned unauthenticated attacker to conduct man-in-the-middle attacks, intercepting and potentially modifying encrypted communications between the SCG and Dell's remote support infrastructure. Affected versions are SCG 5.0 Appliance prior to 5.36.00.16 and SCG 5.0 Application prior to 5.36.00.00, as confirmed by Dell advisory DSA-2026-382. No public exploit code or CISA KEV listing exists at time of analysis, but successful exploitation yields high confidentiality and integrity impact on all intercepted support traffic.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows an unauthenticated network-positioned attacker to conduct man-in-the-middle attacks against both the Appliance (prior to 5.36.00.16) and Application (prior to 5.36.00.00) deployment forms, intercepting and potentially tampering with encrypted remote-support communications to achieve unauthorized access. Dell confirmed the vulnerability under advisory DSA-2026-382 with a CVSS 7.7 (High) rating; the AC:H metric reflects the MITM positioning prerequisite, which is the primary exploitation barrier. No public exploit code has been identified at time of analysis.
Authentication bypass in the shared wp-module-data module (bundled across four Newfold WordPress plugins) allows unauthenticated remote attackers to gain full administrator-level access to any affected WordPress site that lacks a stored Hiive connection token. The defect degenerates the HMAC-style Bearer token verification into a trivially forgeable computation: when the stored connection token is absent, PHP coerces `strrev(false)` to `strrev('')`, reducing the secret salt to the publicly known SHA-256 empty-string hash `e3b0c44...`, while all remaining inputs (HTTP method, URL, body, and the attacker-supplied X-Timestamp header) are fully attacker-controlled, enabling offline token pre-computation. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV at time of analysis, but full technical details including source code references are publicly disclosed by Wordfence, substantially lowering the barrier to exploitation.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows remote unauthenticated attackers to exploit TLS/certificate handling weaknesses, leading to unauthorized access and high-availability impact. Both the Appliance (Virtual Edition) builds prior to 5.36.00.16 and Application builds prior to 5.36.00.00 are affected. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated network vector and CVSS 8.2 score make this a priority patching item for environments running Dell infrastructure monitoring.
Improper certificate validation in Dell Secure Connect Gateway 5.0 exposes both Appliance and Application deployments to unauthenticated remote exploitation, enabling MITM-style attacks that bypass TLS trust enforcement and grant unauthorized access to communications relayed through the gateway. The Appliance variant is affected below version 5.36.00.16 and the Application variant below 5.36.00.00. No active exploitation has been confirmed by CISA KEV and no public exploit code is referenced, but the zero-authentication network vector makes patching urgent for any internet-reachable SCG deployment.
Certificate hostname validation failure in Dell Secure Connect Gateway (SCG) 5.0 enables an unauthenticated remote attacker positioned as a network man-in-the-middle to present a valid TLS certificate for a different host, defeating the connection's trust model and gaining unauthorized access to intercepted communications. Both the Appliance variant (prior to 5.36.00.16) and Application variant (prior to 5.36.00.00) are confirmed affected per Dell DSA-2026-382. No public exploit or CISA KEV listing has been identified at time of analysis; the AC:H CVSS metric reflects the non-trivial network positioning prerequisite.
Improper certificate validation in Dell Secure Connect Gateway 5.0 (both Appliance and Application variants) enables an unauthenticated remote attacker with a man-in-the-middle network position to intercept and modify encrypted communications between the SCG platform and Dell's support infrastructure. Rated CVSS 7.4 (CWE-295) with high confidentiality and integrity impact, this flaw is particularly sensitive given that SCG routinely carries privileged support telemetry and credentials. No public exploit code and no CISA KEV listing have been identified at time of analysis; Dell has released patches in advisory DSA-2026-382.
Authentication bypass in the Next-Cart Store to WooCommerce Migration WordPress plugin (all versions ≤ 3.9.8) allows unauthenticated remote attackers to reach privileged migration endpoints and achieve full site takeover via arbitrary SQL execution and arbitrary file deletion. The root cause is a double design flaw: the `/wp-json/next_cart/v1/migration` REST route is registered with `permission_callback` set to `__return_true` (granting unrestricted access to all callers), and the token check falls back to the hardcoded literal `__token__` via `get_option('nextcart_token', '__token__')` whenever the database option has never been written. Once past the token check, attackers pass attacker-controlled SQL directly to `$wpdb->query()` and `$wpdb->get_results()` - enabling administrator account creation - and pass an attacker-controlled path to `unlink()`, enabling arbitrary file deletion. No public exploit or CISA KEV listing has been identified at time of analysis, though source code confirming the flaw is publicly visible in the WordPress plugin SVN repository.
Secure Boot bypass in InsydeH2O UEFI firmware allows a locally-privileged attacker to leverage the embedded UEFI Shell to execute shell commands or startup scripts that circumvent Secure Boot integrity enforcement, enabling pre-OS code execution outside the chain of trust. The vulnerability affects InsydeH2O across all tracked versions per the CPE wildcard, with remediation details deferred to OEM-specific advisories referenced in Insyde SA-2026004. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope change to C:H/I:H/A:H reflects the catastrophic trust boundary violation once exploited.
Improper access controls (CWE-862 Missing Authorization) in Tanium Comply expose compliance and vulnerability assessment data to authenticated users who lack sufficient privileges to access it. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) scores this at 7.1, with high confidentiality impact and limited integrity risk, exploitable over the network by any low-privileged Tanium account holder with no user interaction required. No public exploit code or active exploitation has been identified at time of analysis.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Authentication bypass in s-pms SPMS-Server (through v1.0) allows remote, unauthenticated attackers to forge valid administrative session tokens because a hardcoded default access-token secret is shipped in the core configuration file and is never overridden in the production environment profile. An attacker who extracts that secret from the publicly available source can then sign their own tokens and reach protected backend APIs with full administrative privileges, giving high confidentiality, integrity and availability impact (CVSS 9.8; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and EPSS is low at 0.24% (15th percentile); the real limiter is deployment hygiene, since any operator who rotates or overrides the token secret removes the flaw entirely.
Authentication bypass in Siam Ordering (siam-server) 1.0.0 lets remote attackers log in as any user, merchant, or administrator by supplying a hardcoded master verification code that ships with the server. The flaw is rooted in a hardcoded credential (CWE-259) rather than a memory-safety or logic error, so every deployment of version 1.0.0 that exposes the verification endpoint is potentially affected, with full confidentiality, integrity, and availability impact once a session is obtained. No public exploit code has been identified and the EPSS score is low (0.24%, 16th percentile), but the issue is trivially severe if the code value is known or recoverable, and no vendor-released patch was identified in the available data.
Token replay vulnerability in macropay-solutions/maravel-framework prior to version 10.74.0 enables attackers holding invalidated JWT tokens to bypass authentication and regain unauthorized API access after a predictable 2-hour window. The root cause is a lifecycle collision: the framework's O(1) Atomic Lazy Eviction model silently caps all tagged cache entries at 7,200 seconds, truncating the tymon/jwt-auth blacklist's intended 14-day retention and leaving revoked tokens cryptographically valid but logistically unblocked. No public exploit code has been identified and the CVE is not in CISA KEV, though the attack mechanism is deterministic and requires no specialized tooling.
Local privilege escalation in Waves Central for macOS (versions up to 16.6.2) allows any authenticated local user to gain root code execution by abusing a flawed XPC client authorization scheme in the product's privileged helper service. The helper validates connecting XPC clients by performing a certificate-chain equality comparison against itself rather than enforcing a pinned code requirement (application identifier and Apple Team ID), meaning any process carrying the Waves signing certificate can impersonate a legitimate client and instruct the helper to run arbitrary scripts as root. No public exploit has been identified at time of analysis; a vendor-released fix is available in version 17.0.
Administrative takeover of the Eclipse aeriOS Identity Manager (IdM) is possible because the current development-version deployment exposes its Keycloak server and PostgreSQL backing database to the network (Kubernetes NodePort services, and PostgreSQL bound to all interfaces under Docker Compose) while shipping fixed, publicly documented default credentials for the Keycloak admin and the PostgreSQL user. An attacker who can reach these services logs in with the published defaults to read or modify identity data - users, roles, client credentials, sessions, and cryptographic material - and can mint privileged identities or tokens trusted by other aeriOS components. No official release exists yet; there is no CISA KEV listing and no public exploit identified at time of analysis, though the credentials are effectively public in the source repository.
Privilege escalation to arbitrary code execution in Adobe Experience Manager (AEM 6.5 through 6.5.24, AEM as a Cloud Service through 2026.7.0, and AEM 6.5 LTS through SP2) lets a low-privileged authenticated attacker abuse an incorrect-authorization flaw to execute code and take over a victim's account or session without any user interaction. Because the CVSS scope is changed, the impact extends beyond the vulnerable component. Adobe (PSIRT) rated it 9.9 critical and shipped a fix in APSB26-98; no public exploit is identified at time of analysis.
Roo-Code's auto-approve shell execution mechanism through version 3.54.0 can be bypassed by exploiting a word-boundary mismatch between the approval gate's shell tokenizer and bash, allowing commands explicitly denied in the user's allowlist to execute silently on the developer's machine. An attacker who can influence the command string reaching the auto-execute pipeline - most plausibly via prompt injection through malicious repository content or crafted AI interactions - prefixes a denied command with an allowlisted token followed by a hash character and separator; the approval gate passes the token as safe while bash interprets the hash as a comment delimiter and executes the trailing denied payload with the agent's full privileges. No public exploit has been confirmed as actively exploited (not in CISA KEV), though a detailed technical writeup is publicly available on GitHub, lowering the barrier for exploitation.
Command allowlist bypass in Roo-Code through version 3.54.0 enables execution of shell commands that users explicitly denied from auto-approval. The vulnerability stems from the shell command parser's failure to recognize the bash pipe operator `|&` as a command separator - a crafted pipeline prefixed with an allowlisted command followed by the stderr-redirecting pipe and a denied command passes parser validation while bash executes the entire pipeline, including the denied component, with full agent privileges on the developer's workstation. A public proof-of-concept writeup exists on GitHub; no active exploitation has been confirmed by CISA KEV.
Incorrect Authorization (CWE-863) in Adobe Commerce allows unauthenticated remote attackers to bypass security controls and gain unauthorized read access across a changed security scope boundary. Affected products span Adobe Commerce 2.4.4-2.4.9, Adobe Commerce B2B 1.3.3-1.5.3, and Magento Open Source 2.4.6-2.4.9, all prior to the August 2026 security patches released under APSB26-138. No public exploit code has been identified and no active exploitation is confirmed in CISA KEV, but SSVC rates the vulnerability as automatable, making mass scanning a realistic near-term threat once technical details become more widely known.
Incorrect Authorization (CWE-863) in Adobe Commerce and Magento Open Source allows a high-privileged attacker to bypass access control boundaries and perform unauthorized writes to resources outside their intended scope, with the scope change (S:C) amplifying impact to components beyond the directly vulnerable module. All supported branches of Adobe Commerce (2.4.4-2.4.9), Magento Open Source (2.4.6-2.4.9), and Commerce B2B (1.3.3-1.5.3) prior to the August 2026 security patch cycle are affected. No public exploit or CISA KEV listing is identified at time of analysis; exploitation requires an already-authenticated admin-level session.
Incorrect Authorization (CWE-863) in Adobe Commerce and Magento Open Source allows unauthenticated remote attackers to escalate privileges and gain write access to restricted platform resources without user interaction. Scope change is confirmed: successful exploitation crosses privilege boundaries within the Commerce platform, granting access to administrative or otherwise protected functionality. SSVC classifies technical impact as total and the attack as automatable, elevating operational priority despite no active exploitation currently recorded in CISA KEV.
Incorrect Authorization in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B allows remote unauthenticated attackers to bypass access controls and read sensitive platform data, achieving a privilege-escalation effect without any user interaction. The flaw stems from CWE-863 (Incorrect Authorization), where authorization checks fail to enforce the correct permission boundaries, letting an unauthenticated network request access resources restricted to higher-privilege roles. No public exploit code has been identified at time of analysis, but the combination of PR:N and C:H on a major e-commerce platform makes this a meaningful exposure for confidential business and customer data.
Incorrect Authorization in Adobe Commerce allows remote unauthenticated attackers to escalate privileges and access sensitive information without any user interaction. The vulnerability, rooted in CWE-863, affects Adobe Commerce 2.4.4 through 2.4.9, Magento Open Source 2.4.6 through 2.4.9, and Adobe Commerce B2B 1.3.3 through 1.5.3, covering a broad range of production deployments. No public exploit code has been confirmed and CISA KEV does not list active exploitation, but SSVC flags the flaw as automatable, raising concern for mass-scanning campaigns against exposed storefronts.
Skype for Business Server's failure to properly verify cryptographic signatures (CWE-347) enables unauthenticated attackers on the same network segment to spoof identities or server endpoints, achieving high confidentiality and integrity impact across three distinct server release lines. All on-premises deployments of SfB Server 2015 CU13, 2019 CU8, and Subscription Edition CU1 below specific cumulative-update thresholds are confirmed affected, with patched releases available from Microsoft. The JWT Attack tag combined with CWE-347 indicates the flaw resides in token signature validation, where the server may accept cryptographically forged or unsigned tokens as legitimate - enabling impersonation without valid credentials. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local privilege escalation in Android's biometrics settings framework (BiometricsSettingsBase.java) allows a low-privileged app to achieve full device compromise without user interaction. The confused deputy flaw (CWE-441) in the component's onAttach lifecycle method enables a malicious app to cause the biometrics settings service - which operates with elevated system privileges - to perform privileged operations on the attacker's behalf, bypassing authentication controls. Affects Android 14, 15, 16, 16-qpr2, and 17; no public exploit or CISA KEV listing identified at time of analysis.
Remote privilege escalation in the Android Bluetooth stack (AdapterService.java) allows an attacker to bypass device pairing entirely. A logic error in handleBondStateChanged lets a bond be treated as established without the normal pairing/consent flow, granting the attacker elevated privileges on Android 15, 16, 16-qpr2, and 17 with no user interaction. Google rates it CVSS 9.8; no public exploit is identified and CISA's SSVC framework records exploitation status as none, and EPSS is very low (0.16%).
Authentication bypass via capture-replay in Microsoft Authentication Library (MSAL) for Node.js versions 1.0.0 through 5.5.x allows an unauthenticated network-adjacent attacker to spoof authenticated identity by replaying captured tokens. The CWE-294 root cause means a previously captured authentication artifact can be reused to impersonate a legitimate user, yielding high confidentiality and integrity impact consistent with the CVSS C:H/I:H scores. No public exploit or active exploitation is known at time of analysis, but Microsoft has released a patch at version 5.6.0.
Missing authorization in Microsoft Entra ID allows an attacker who already holds a valid low-privilege identity - a compromised user account, guest account, or service principal - to elevate privileges over the network without any user interaction, giving high impact to confidentiality, integrity, and availability (CVSS 8.8, AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H). Microsoft has published an advisory through MSRC (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83941), but no public exploit code has been identified at time of analysis and the issue is not in CISA KEV; EPSS is only 0.73% (52nd percentile), so this is a genuine priority-worthy finding rather than an emergency. Because Entra ID is a Microsoft-operated multi-tenant cloud service, the affected code is centrally managed and the exact tenant configuration or feature exposing the missing check is not detailed in the advisory.
Security feature bypass in Visual Studio Code before 1.136.2 allows a remote, unauthenticated attacker to circumvent a protection mechanism via a failing-open (CWE-636) code path, resulting in high confidentiality impact and limited integrity impact across a changed scope. The vulnerability is reachable over the network with low complexity but requires user interaction, suggesting an attacker must induce the victim to open a crafted workspace, file, or URI. No public exploit code and no CISA KEV listing have been identified at time of analysis, though Microsoft has released a patch.
Security feature bypass in Visual Studio Code (versions 1.0.0 through below 1.136.2) allows a remote unauthenticated attacker to circumvent a protective security control via an interpretation conflict in the editor's processing pipeline. The vulnerability requires user interaction (UI:R) - a victim must open or interact with attacker-influenced content - after which the scope change (S:C) and high confidentiality impact suggest sensitive host data or credentials may be exfiltrated beyond the process boundary. No public exploit or CISA KEV listing has been identified at time of analysis.
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a protection mechanism when a user is lured into interacting with malicious content (UI:R). Rooted in an incomplete comparison that omits required factors (CWE-693), the flaw carries a scope-changed CVSS 9.6 with full confidentiality, integrity, and availability impact, consistent with a trust/security-control bypass that can extend beyond the editor's initial boundary. A vendor patch exists; no public exploit is identified at time of analysis.
HTTP request smuggling in Visual Studio Code (versions 1.0.0 through 1.136.2) enables unauthenticated network attackers to bypass security controls through inconsistent interpretation of HTTP request boundaries. The CVSS scope change (S:C) signals that impact extends beyond the editor itself - smuggled requests can affect back-end services or proxies that VS Code communicates with, resulting in high confidentiality exposure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible, unauthenticated nature of the attack surface warrants prompt patching.
Local privilege escalation in Microsoft Authenticator for Android (versions 6.0.0 through below 16.3.0) allows a local attacker without any prior privileges to bypass the app's authentication controls and elevate privileges on the device. The scope-changed CVSS vector (S:C) reflects that a successful bypass extends impact beyond the Authenticator app itself - potentially compromising MFA-protected accounts and downstream Microsoft or enterprise services. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the wide affected version range (spanning a very broad Android release history) increases exposure surface considerably.
Privilege escalation in Microsoft SQL Server (2017 through 2025) allows a low-privileged authenticated network attacker to gain full administrative control via improper access control enforcement. The vulnerability spans four major SQL Server release trains - 2017, 2019, 2022, and 2025 - including both Cumulative Update (CU) and General Distribution Release (GDR) servicing branches. No public exploit code has been identified at time of analysis, but the low attack complexity and broad affected surface across enterprise SQL Server deployments make this a meaningful priority for patching.
Security feature bypass in Microsoft Windows iSCSI (Initiator/Target service) lets a remote, unauthenticated attacker defeat the protocol's weak authentication over the network, per Microsoft's advisory carrying a 9.8 CVSS with full confidentiality, integrity, and availability impact. The flaw spans essentially the entire supported Windows Server line (2012 through 2025) plus Windows 10 (1607/1809), and a vendor patch is available. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) enables a network-authenticated attacker to execute arbitrary code with full system impact across a broad range of Microsoft Windows releases. The vulnerability (CWE-122) affects Windows 10, Windows 11, and Windows Server 2012 through 2025, with vendor-released patches available via MSRC. No public exploit code and no CISA KEV listing are identified at time of analysis, but the low authentication bar (PR:L) and wide platform coverage make this a high-priority patch for any organization operating RRAS-enabled servers.
Use-After-Free (CWE-416) in the Windows Routing and Remote Access Service enables an unauthenticated attacker positioned on an adjacent network to execute arbitrary code on affected Windows systems. The vulnerability spans a wide range of Microsoft platforms from Windows Server 2012 through Windows Server 2025 and Windows 10/11 client versions, making the exposure surface substantial in enterprise environments where RRAS is deployed as a VPN or routing endpoint. Microsoft has released patches addressing this issue; no public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS C:H/I:H/A:H impact and adjacent-network unauthenticated attack path make it a high-priority patching target for organizations running RRAS-enabled servers.
Privilege elevation in Spring Cloud Azure (versions 1.0.0 up to but not including 7.4.0) lets a network-based, unauthenticated attacker bypass improper authentication logic (CWE-287) to gain elevated privileges. Reported by Microsoft (MSRC) with a vendor patch available; no public exploit identified at time of analysis and neither KEV nor EPSS/POC signals are present in the provided data.
Security feature bypass in the Windows TCP/IP stack allows unauthenticated remote attackers to circumvent network-level security controls across a broad range of Windows client and server versions, from Windows Server 2012 through Windows 11 25H2 and Windows Server 2025. Exploitation leverages CWE-1288 (improper consistency validation within input), meaning crafted packets with internally contradictory fields can slip past enforcement mechanisms - resulting in high integrity impact with no confidentiality or availability effect. No public exploit code has been identified at time of analysis, and Microsoft has released patches across all affected version families.
DNS response spoofing in Windows DNS Server allows unauthenticated network attackers to inject forged DNS responses by exploiting an origin validation error (CWE-346), poisoning the server's cache and redirecting downstream client resolution to attacker-controlled endpoints. All supported Windows Server releases from 2012 through 2025, plus Windows 10 versions 1607 and 1809, are confirmed affected across both full and Server Core installations. Successful cache poisoning yields full confidentiality, integrity, and availability impact - enabling credential interception, traffic redirection, and service disruption for any client relying on the compromised resolver. No public exploit identified at time of analysis, and the vulnerability is not currently listed in the CISA KEV catalog.
Capture-replay exploitation of Windows Kerberos authentication enables an attacker with network access and initial credentials to bypass authentication controls and achieve remote code execution. Affected products span virtually every supported Windows client and server release from Windows Server 2012 to Windows 11 26H1 and Windows Server 2025. No public exploit or CISA KEV listing has been identified at time of analysis, but the breadth of affected platforms and Microsoft's direct disclosure make this a high-priority patching target.
Network-based privilege escalation in Microsoft Exchange Server lets an already-authenticated attacker gain higher privileges by exploiting a missing authorization check (CWE-862). Affected on-premises builds include Exchange 2016 CU23, Exchange 2019 CU14/CU15, and the Subscription Edition; Microsoft has released fixed cumulative-update builds via MSRC. No public exploit identified at time of analysis and the flaw is not on CISA KEV, but its 9.1 CVSS with scope change and full CIA impact makes it a high-priority patch for internet-facing mail infrastructure.
Privilege escalation in Windows Shell affects Windows 11 (versions 23H2 through 26H1) and Windows Server 2025, enabling a locally authenticated low-privileged attacker to achieve full system compromise with no user interaction required. The root cause is CWE-306 - a critical internal Shell function that lacks an authentication or authorization gate, allowing a standard user account to invoke privileged operations and elevate to SYSTEM. No public exploit code or CISA KEV listing exists at time of analysis; Microsoft has issued patches via Windows Update.
Remote code execution in Microsoft SharePoint Server Subscription Edition allows an authenticated low-privileged attacker to execute arbitrary code over the network by exploiting an improper access control flaw (CWE-284). The vulnerability affects build versions from 16.0.0 up to but not including 16.0.20326.20090, which Microsoft has patched. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog at time of analysis.
Authentication bypass by spoofing in the Windows Netlogon (MS-NRPC) protocol allows an unauthenticated adjacent-network attacker to impersonate domain authentication, yielding full confidentiality, integrity, and availability compromise of the targeted system. The flaw spans Windows 10, Windows 11, and Windows Server 2012 through Server 2025, making it a broad-surface Active Directory infrastructure risk. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; however, the high CIA impact warrants prompt patching in domain-connected environments.
Authentication bypass in DeepSeek Harness before 0.1.2-alpha.1 lets attackers seize full control of the local agent by spoofing the HTTP Host header, because the control-plane API trusts the client-supplied Host value instead of the actual TCP connection origin. An unauthenticated attacker who lures an operator's browser to a malicious page (via DNS rebinding or a cross-site 'simple' POST) can invoke privileged methods such as commands/execute with danger-full-access, escalate approval policies to unconfined execution, and exfiltrate all stored conversations. No public exploit is identified at time of analysis, though the fixing commit and a VulnCheck advisory document the exploitation mechanics in detail.
Unauthenticated remote access control bypass in Fortinet FortiSandbox 4.2.x through 5.0.x - and its Cloud and PaaS variants - allows network-reachable attackers to retrieve sensitive information and disrupt availability by sending crafted HTTP requests, with no credentials or user interaction required. Fortinet's confirmed CVSS temporal metrics include E:P (proof-of-concept exploit code exists) alongside RL:O (official remediation available) and RC:C (confirmed), establishing this as an actively documented, patchable risk against sandboxing infrastructure that processes enterprise malware submissions. The scope-changed vector (S:C) combined with high availability impact (A:H) indicates the access control failure cascades beyond the directly targeted HTTP endpoint to other components within the FortiSandbox platform.
UEFI Secure Boot bypass in Cisco UCS Servers and UCS-based appliances allows authenticated users with 'user' or 'admin' role credentials - or unauthenticated attackers with physical device access - to disable Secure Boot protections and execute unauthorized software at boot time. The flaw stems from UEFI Shell memory-write commands remaining accessible while Secure Boot is active, enabling direct manipulation of Secure Boot validation variables in UEFI memory. A successful exploit undermines firmware integrity controls, potentially allowing persistent pre-OS implants or untrusted bootloaders on enterprise server infrastructure. No public exploit code or CISA KEV entry has been identified at time of analysis.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 lets an unauthenticated attacker run arbitrary code and read or tamper with other users' chat sessions by reaching publicly shared MCP (Model Context Protocol) project endpoints. The flaw stems from Langflow failing to enforce its public-flow security restrictions and session-isolation controls, so exposure exists once a project is shared publicly via an MCP endpoint. No public exploit is identified in the provided data, and the item is not listed in CISA KEV.
Sensitive health-data exposure in the Lenovo Health Android application (distributed exclusively in the Chinese market) stems from hardcoded credentials (CWE-798) that let an attacker access users' health-related information without legitimate authentication. Reported by Lenovo PSIRT and tracked under a single Lenovo advisory, it carries a CVSS 4.0 base of 9.3 driven by high confidentiality impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Local privilege escalation in Lenovo Rescue and Smart Assistant (LMSA) enables a local authenticated user to execute arbitrary code with elevated privileges by exploiting a capture-and-replay authentication bypass (CWE-290) in the application's privileged service layer. The vulnerability is strictly local in scope per the CVSS 4.0 vector (AV:L/PR:L), limiting the threat to attackers who already hold a standard user account on an affected Lenovo device. Lenovo has published advisory LEN-217409 with remediation guidance; no public exploit has been identified at time of analysis.
IBM WebSphere Application Server 8.5 and 9.0 contain improper authentication controls that allow an attacker who already holds a local, low-privileged foothold on the server to bypass security checks and escalate privileges. Successful exploitation yields high confidentiality and integrity impact — protected resources and configuration can be read and modified — though availability is unaffected per the CVSS vector. No public exploit code has been identified, EPSS is very low at 0.12% (3rd percentile), the issue is not in CISA KEV, and a vendor patch is available from IBM.
Authentication/authorization bypass in rclone's dynamic serve interface (versions 1.70.0 through 1.75.0) lets remote attackers reach a fixed filesystem instead of the per-request backend the operator intended. When an FTP or S3 server is spun up via the serve/start RC (remote control) API with a per-server proxyOpt.AuthProxy, the FTP and S3 constructors mistakenly consult the empty process-global proxy.Opt.AuthProxy, so the request-local auth proxy is silently ignored: FTP accepts anonymous logins with any password against the fixed VFS, and S3 with AuthKey serves the fixed RC fs rather than the proxy-selected backend. There is no public exploit identified at time of analysis, and this is not in CISA KEV. Fixed in 1.75.1.
Authentication bypass in rclone's S3 server mode (rclone serve s3) allows any unauthenticated network attacker to impersonate arbitrary S3 access keys. When rclone serve s3 is started with --auth-proxy but without --auth-key, authPairMiddleware registers whatever accessKeyID the client chooses against an empty s3Secret, and gofakes3 then validates the request's SigV4 signature against that same empty secret - so an attacker can pick any access key, sign with an empty secret, and reach whatever backend the auth-proxy script resolves for that identity. Fixed in rclone 1.75.1; no public exploit identified at time of analysis, though the vendor security advisory (GHSA-xwwr-4h3p-r22c) and fix commit are public.
Arbitrary code execution in Dell ThinOS 10 (all builds prior to 2605_10.2616) allows a remote, unauthenticated attacker to run code within the application context of the affected thin client, per Dell advisory DSA-2026-389. The root cause is a protection mechanism failure (CWE-284) that bypasses an intended security control rather than exploiting a memory-corruption bug directly. No public exploit is identified at time of analysis and the CVE is not in CISA KEV, but the network-reachable, no-authentication attack profile makes it high priority.
HTTP/1 request-target parsing in Traefik prior to 2.11.57 and 3.7.13 allows unauthenticated remote attackers to send a rootless URL target (e.g., `http:example.com/admin`) that Go's HTTP library stores in URL.Opaque rather than URL.Path, leaving URL.Path empty. Traefik's routing engine, forwardAuth middleware, and access logger all evaluate against the normalized empty path (treated as `/`), while URL.RequestURI() gives URL.Opaque precedence when forwarding — meaning the backend receives the original opaque target verbatim. The practical consequence is cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion, all requiring no authentication or special client configuration. No public exploit has been identified at time of analysis, though the patch PR includes test cases demonstrating the attack technique in full detail.
Backend connection hijacking in Traefik reverse proxy (2.11.0 through 2.11.56 and 3.0.0 through 3.7.12) lets an unauthenticated remote client impersonate another user over HTTP/3. Because the HTTP/3 entrypoint never calls service.AddTransportOnContext, the kerberosRoundTripper falls back to a shared backend transport instead of one bound to each frontend connection, so when a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can reuse a backend connection already authenticated for a victim, read the victim's data, and act as the victim without ever obtaining their credentials. No public exploit is identified at time of analysis, though the fix PR ships a regression test that effectively demonstrates the flaw.
Traefik's header-security defenses (aliasHeadersStrategy, underscoreHeadersStrategy, forwardedHeaders) inspect req.Header but not req.Trailer, allowing unauthenticated clients on versions 3.2.0 through 3.7.12 to smuggle security-sensitive header values through HTTP/1.1 chunked trailers or HTTP/2 trailers. When retry or buffering middleware is active in the routing chain, attacker-controlled trailer values become accessible before the request is cloned for the backend; backends that merge trailers into their header namespace then receive the spoofed values, bypassing Traefik's documented delete or reject behavior. No public exploit code has been identified and this CVE is not in CISA KEV, but the impact on identity and routing integrity at the backend is classified high by the CVSS 4.0 subsequent-system metrics.
CyberPanel before 3.0.5 allows attackers who have obtained an administrator's password to bypass two-factor authentication entirely on API endpoints by deriving valid API tokens from the password alone, without satisfying the TOTP requirement. This reduces 2FA-protected admin accounts to effective single-factor authentication at the API layer, enabling full administrative operations or session creation. The fix is available in version 3.0.5 per the GitHub security advisory; no public exploit or active exploitation has been identified at time of analysis.
Authentication bypass in Traefik v3.7.0 through v3.7.11 lets remote unauthenticated attackers reach protected Kubernetes backends when an Ingress uses the ingress-nginx compatibility provider with both an authentication annotation and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation. The provider generates a host-only 'sibling' router carrying only a non-terminal RedirectRegex middleware that still routes to the protected backend, so a crafted request evades the redirect and is proxied without any annotation-derived middleware. Reported by VulnCheck with a published advisory; no public exploit is identified at time of analysis, though the technique is fully documented and trivially reproducible.
Improper access control in Capgo (capgo.app) lets any holder of an ordinary full API key forge a trusted SSO provider by writing directly to the public.sso_providers table exposed via Supabase PostgREST, setting status='active' and enforce_sso=true without passing the backend provisioning route. This sidesteps the Enterprise-plan gate, Supabase Management API provider creation, DNS TXT domain-ownership verification, and the pending_verification→verified→active workflow, so an attacker can assert SSO enforcement for arbitrary unverified domains and disrupt normal login. All versions are affected, no patch was available at advisory time, and there is no public exploit identified at time of analysis beyond the VulnCheck write-up.
Capgo's MFA enforcement is defeated by an authentication assurance level (AAL) mismatch across two distinct code paths: the Edge JWT middleware (foundJWT() in supabase/functions/_backend/utils/hono_middleware.ts) accepts Supabase JWTs without inspecting the aal claim, and the direct RBAC path (checkPermissionPg() calling public.rbac_check_permission_direct() in rbac.ts) authorizes operations by user ID alone, bypassing the assurance-level check that public.verify_mfa() correctly enforces. An attacker holding only the victim's account password can authenticate, receive an aal1 JWT, exercise privileged RBAC operations without triggering any MFA challenge, mint a persistent app_admin API key, and modify production OTA channel configurations - all of which survive logout of the original aal1 session. No patched version has been released; all versions of capgo.app are affected, and the advisory includes a validated proof-of-concept demonstrating bundle swap on a production channel.
Improper authorization in Hikvision HikCentral Access Control V2.5.0 and below allows authenticated low-privilege users to invoke API endpoints restricted to higher-privileged roles, resulting in unauthorized access to sensitive data and limited system modification. The CVSS vector (PR:L, C:H, I:L) confirms the attacker requires only a valid low-privilege account but can achieve high confidentiality impact and limited integrity compromise across the network. No public exploit code or CISA KEV listing has been identified at time of analysis, though the straightforward nature of the authorization flaw (unenforced role checks on API routes) makes it readily exploitable by any insider or attacker who obtains basic credentials.
Unauthenticated remote control of GeoVision GV-LPC2211 license-plate-capture cameras (firmware V1.13) is possible because the PTZ control service is exposed on the network with no authentication (CWE-306). Any remote client that can reach the service can query PTZ state and, more critically, issue PTZ movement or raw serial commands to the device and its attached serial peripherals. CVSS is 9.4 and no public exploit has been identified at time of analysis, but the trivial network-reachable, unauthenticated nature makes exploitation straightforward.
Unauthenticated arbitrary WordPress option deletion in the zipMoney (Zip Co) Payments Plugin for WooCommerce before 2.4.0 lets remote attackers destroy site configuration and take the site offline. One front-end request handler performs no authorization checks and does not restrict which option name the caller supplies, so any unauthenticated visitor can delete critical wp_options entries. Publicly available exploit code exists and a vendor patch (2.4.0) is available; no active exploitation has been confirmed (not in CISA KEV).
Two-factor authentication bypass in the miniOrange 2FA WordPress plugin allows an attacker who has already obtained a victim's password to defeat the second factor through unlimited OTP brute-forcing. The plugin keys its attempt-rate limit to a client-controlled identifier rather than the target account, enabling an adversary to rotate that identifier and circumvent lockout entirely; a separate validation endpoint applies no rate limit at all. A publicly available exploit (WPScan) confirms practical exploitability against plugin versions below 6.3.1 and 19.3.
Unauthenticated arbitrary site-option deletion in the miniOrange 2FA WordPress plugin (versions 5.3.24 through before 6.3.1, and 18.0 through before 19.3) lets any visitor delete arbitrary wp_options entries because option names are taken directly from request input without validating a legitimate transaction. Deleting the right options can lock every administrator out of the WordPress dashboard or fully deactivate the two-factor plugin, stripping the site of its 2FA protection. Publicly available exploit code exists (WPScan) and a vendor patch is available; the flaw is rated CVSS 10.0.
Privilege escalation in the Bulk Password Reset WordPress plugin (all versions ≤1.3.3) allows any authenticated subscriber-level user to perform a full administrative account takeover. The plugin fails to validate the requesting user's identity before permitting bulk password changes and email-address updates, meaning an attacker can redirect an administrator's email to an attacker-controlled address, then invoke the standard WordPress password-reset flow to obtain reset credentials for that admin account. No public exploit code has been identified at time of analysis, but source code references from WordPress Plugin Trac directly expose the vulnerable functions at lines 44, 594, 659, and 679 of bulk_password_reset.php.
Pre-authentication queue deletion in Apache Artemis and Apache ActiveMQ Artemis allows unauthenticated remote attackers to destroy message queues by sending a crafted Openwire RemoveSubscriptionInfo command before or after the broker's authentication stage completes. The flaw affects every Apache ActiveMQ Artemis release from 1.0.0 through 2.44.0, and the rebranded Apache Artemis releases from 2.50.0 through 2.56.0, making it an extremely wide-scope exposure for the legacy version range. No public exploit code or CISA KEV listing has been identified at time of analysis, but the pre-authentication nature and low exploitation complexity make this a credible denial-of-service and data-loss vector in any internet- or intranet-exposed Artemis deployment.
Session hijacking in Apache ActiveMQ Artemis and Apache Artemis allows unauthenticated remote attackers to steal authenticated messaging sessions by sending a crafted CORE protocol SESSION_REATTACH packet, granting full control of an existing authenticated session without any credentials. The CORE protocol's session reattachment mechanism - designed for fault-tolerant HA reconnection - performs no identity verification, enabling any network-accessible attacker to impersonate legitimate connected clients. No public exploit or CISA KEV listing is identified at time of analysis, but the vulnerability spans the entire release history of Apache ActiveMQ Artemis (1.0.0 through 2.44.0), meaning essentially all historical deployments are affected.
Cluster credential exposure in Apache ActiveMQ Artemis and Apache Artemis allows a network-adjacent unauthenticated attacker to passively capture cluster administrative credentials during the initial peer-discovery handshake. Both the legacy Apache ActiveMQ Artemis lineage (versions 1.0.0 through 2.44.0) and the newer Apache Artemis distribution (versions 2.50.0 through 2.56.0) are affected, covering effectively the entire supported history of the project. An attacker positioned on the same network segment as a clustering deployment can intercept these credentials without any prior authentication, then use them to authenticate as a cluster administrator and gain full control over the message broker cluster. No public exploit code has been identified at the time of analysis.
Pre-authentication information disclosure in Apache ActiveMQ Artemis and Apache Artemis exposes cluster topology details to any unauthenticated remote attacker. The CORE protocol's SUBSCRIBE_TOPOLOGY request can be submitted before the broker enforces authentication, leaking cluster node configuration including internal broker addresses and cluster membership data. No public exploit code has been identified and it is not listed in CISA KEV, but the zero-prerequisite network vector makes automated scanning trivially feasible at scale.
Unauthenticated remote attackers can create arbitrary durable queues on Apache Artemis and Apache ActiveMQ Artemis brokers via the native CORE protocol due to missing authentication enforcement in the protocol handler. The vulnerability spans the entire Apache ActiveMQ Artemis release history (1.0.0 through 2.44.0) and the recently rebranded Apache Artemis fork (2.50.0 through 2.56.0), making the unpatched population potentially very large. Exploitation enables persistent unauthorized broker state manipulation and denial-of-service through storage and memory exhaustion, with no credentials or user interaction required; no public exploit code has been identified at time of analysis.
Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.
Unauthenticated remote task execution in @yeger/turbo-graph ≤ 2.8.8 allows any adjacent-network attacker to invoke arbitrary Turborepo tasks with the victim developer's OS-level privileges. Two independent implementation flaws combine: the embedded Next.js server omits the hostname argument to Node.js `.listen()`, causing the process to bind on all interfaces (`0.0.0.0`/`::`), while the `/api/run` HTTP endpoint reads task names from an attacker-controlled query string and passes them directly to `spawn()` with no authentication, CSRF protection, or allowlist check. No public exploit database entry or CISA KEV listing was identified, but a fully functional PoC with containerized end-to-end reproduction is included in the GitHub Security Advisory GHSA-2r5q-h53f-9rp3, significantly lowering the bar to exploitation.
OAuth and SCIM identity confusion in Open WebUI 0.6.41-0.10.x (SQLite-backed deployments only) allows unauthenticated remote attackers to hijack arbitrary stored user accounts, including administrator accounts, by presenting an OAuth subject claim containing SQL LIKE wildcard characters. SQLAlchemy's `JSON.contains()` on SQLite compiles to a substring LIKE match rather than an exact equality check, so a crafted `sub` claim such as `%admin%` can resolve to a different stored identity and cause the server to issue the attacker a valid session token for that identity. Vendor-released patch is available in version 0.11.1; no active exploitation has been confirmed.
Authentication bypass in MaxSite CMS versions 0.78 through 109.6 lets unauthenticated remote attackers forge valid administrator session cookies because the framework ships with a hardcoded session encryption key in application/config/config.php that installers never rotate. Using the publicly known key, an attacker computes a valid HMAC-SHA1 over a crafted ci_session cookie to impersonate an admin, defeating the is_login() and mso_check_allow() authorization checks. Publicly available exploit code exists (published by VulnCheck / EviL0rd); there is no evidence of active exploitation in CISA KEV at time of analysis.
Authentication bypass in SSSD's OIDC/IdP provider allows an authenticated IdP user whose subject identifier is a strict lexical prefix of a target user's identifier to impersonate that target user on SSSD-protected Linux systems. The root cause is `eval_access_token_buf()` passing the attacker-controlled identifier's length to `strncmp()`, reducing an identity equality check to a prefix test. All Red Hat Enterprise Linux releases (6-10) and OpenShift Container Platform 4 are affected when SSSD is configured to use an OIDC-based identity provider; no public exploit has been identified at time of analysis.
Unauthenticated firmware injection in Softish EarVision Android Application 1.3.1 paired with the C6 Ear Camera 1.3.1_Code 132 allows an adjacent attacker to deliver arbitrary, unsigned firmware to the physical ear camera device. By spoofing the C6 Ear Camera's wireless identity and eliciting a single user confirmation, the attacker triggers the application to transmit firmware over an update channel that performs neither endpoint authentication nor cryptographic signature verification (CWE-306). No public exploit code has been identified and the vulnerability is absent from the CISA KEV catalog; however, the adjacent-network vector and minimal social engineering threshold make exploitation realistic in clinical or close-proximity consumer settings.
Hardcoded or algorithmically derivable Wi-Fi credentials in the Softish C6 Ear Camera (firmware 1.3.1_Code 132) and companion EarVision Android application (1.3.1) allow an adjacent-network attacker to reconstruct the device's access-point password without authentication. Once the attacker connects to the camera's private Wi-Fi network, the live video stream, device management interfaces, status pages, and the firmware-update endpoint become fully accessible. The vulnerability was disclosed via CISA ICS-CERT advisory VA-26-251-01 and carries a CVSS 4.0 score of 8.7 reflecting high impact across confidentiality, integrity, and availability within the vulnerable system.
Device impersonation via unauthenticated camera spoofing in Softish's EarVision ecosystem exposes Android app users to man-in-the-middle attacks on adjacent networks. The C6 Ear Camera and its companion EarVision Android app (both at version 1.3.1) lack proper device authentication, allowing an adjacent network attacker to emulate the camera, intercept and manipulate device status responses, observe application traffic, and potentially trigger firmware-update behavior on the camera. Reported by CISA ICS-CERT; no public exploit code or KEV listing identified at time of analysis.
Hard-coded credentials in Dell Secure Connect Gateway (SCG) 5.0 expose both the Appliance and Application deployments to unauthenticated remote information disclosure. Any attacker who discovers or reverse-engineers the embedded static credentials - which cannot be changed by administrators - can authenticate to the gateway without valid user accounts and access sensitive information. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no privileges or user interaction; no public exploit or CISA KEV listing is recorded at time of analysis.
Account takeover in Snipe-IT before 8.7.0 allows low-privileged identity-provider users to hijack arbitrary Snipe-IT accounts by registering IdP usernames that are case or Unicode accent variants of existing victim usernames. The vulnerability exploits MySQL's default utf8mb4_unicode_ci collation, which conflates these variants during database lookups, enabling an attacker to be matched to a different user's record across all federated authentication paths - SAML, LDAP, and OAuth. Vendor-released patch 8.7.0 resolves the issue; no public exploit code or active exploitation has been identified at time of analysis.
Snipe-IT before 8.7.0 fails to apply the CheckUserIsActivated middleware to the API middleware group, allowing deactivated accounts to retain full REST API access through their existing Laravel Passport personal access tokens. Any deactivated user whose token has not been explicitly revoked can continue reading and writing assets, users, and licenses at their prior permission level, bypassing the offboarding control that correctly blocks web sessions. The most critical escalation path lets a deactivated account previously holding users.edit permission PATCH its own activation flag via /api/v1/users/{id} to permanently re-enable itself. No public exploit has been identified at time of analysis; a vendor-released patch is available in version 8.7.0.
Hard-coded credentials embedded in Dell Secure Connect Gateway 5.0 allow a remote, unauthenticated attacker to authenticate to the service using the static credentials and access sensitive information. Both the Appliance variant (all versions prior to 5.36.00.16) and the Application variant (all versions prior to 5.36.00.00) are affected, as confirmed by Dell advisory DSA-2026-382. No public exploit code or active exploitation has been identified, but CWE-798 credentials are static across all unpatched installations worldwide, meaning any party with knowledge of them can exploit any exposed instance without further effort.
Hard-coded credentials in Dell Secure Connect Gateway (SCG) 5.0 expose sensitive information to unauthenticated remote attackers across both the Appliance and Application deployment variants. The vulnerability (CWE-798) allows an attacker who discovers or possesses the embedded credentials to authenticate without authorization and access confidential data. Dell has released patched versions under advisory DSA-2026-382, and no public exploits or CISA KEV listing have been identified at time of analysis.
Unauthorized ADMIN access in Dell Secure Connect Gateway (SCG) 5.0 allows a remote unauthenticated attacker to replay a previously captured request indefinitely, forging ADMIN-level access and refresh tokens. Because the token-issuing flow performs no nonce validation and enforces no request expiry, a single intercepted request grants durable administrative control of the gateway. The Appliance edition is affected before 5.36.00.16 and the Application edition before 5.36.00.00; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Remote unauthenticated retrieval of expired one-time secrets in PasswordPusher before 2.11.1 is enabled by a TOCTOU race condition in the expire_after_views view-limit enforcement logic. By issuing multiple simultaneous HTTP requests to the show endpoint, an attacker can read a secret that was configured to self-destruct after a single view, defeating the core confidentiality guarantee the tool is designed to provide. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified, though the technique requires only basic HTTP concurrency tooling.
Authentication bypass in Parse Server's built-in LDAP authentication adapter (versions <= 8.6.87 and 9.0.0 through 9.10.1-alpha.6) lets an unauthenticated attacker who knows a valid directory username obtain a session token for that account, resulting in full account takeover. The adapter forwarded a client-supplied empty password to the directory and treated any non-error bind response as successful authentication, so a zero-length credential triggers an RFC 4513 unauthenticated-simple-bind that directories like Active Directory answer with success. No public exploit identified at time of analysis, but the flaw is trivial to trigger against affected LDAP-backed deployments.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application allows a network-positioned unauthenticated attacker to conduct man-in-the-middle attacks, intercepting and potentially modifying encrypted communications between the SCG and Dell's remote support infrastructure. Affected versions are SCG 5.0 Appliance prior to 5.36.00.16 and SCG 5.0 Application prior to 5.36.00.00, as confirmed by Dell advisory DSA-2026-382. No public exploit code or CISA KEV listing exists at time of analysis, but successful exploitation yields high confidentiality and integrity impact on all intercepted support traffic.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows an unauthenticated network-positioned attacker to conduct man-in-the-middle attacks against both the Appliance (prior to 5.36.00.16) and Application (prior to 5.36.00.00) deployment forms, intercepting and potentially tampering with encrypted remote-support communications to achieve unauthorized access. Dell confirmed the vulnerability under advisory DSA-2026-382 with a CVSS 7.7 (High) rating; the AC:H metric reflects the MITM positioning prerequisite, which is the primary exploitation barrier. No public exploit code has been identified at time of analysis.
Authentication bypass in the shared wp-module-data module (bundled across four Newfold WordPress plugins) allows unauthenticated remote attackers to gain full administrator-level access to any affected WordPress site that lacks a stored Hiive connection token. The defect degenerates the HMAC-style Bearer token verification into a trivially forgeable computation: when the stored connection token is absent, PHP coerces `strrev(false)` to `strrev('')`, reducing the secret salt to the publicly known SHA-256 empty-string hash `e3b0c44...`, while all remaining inputs (HTTP method, URL, body, and the attacker-supplied X-Timestamp header) are fully attacker-controlled, enabling offline token pre-computation. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV at time of analysis, but full technical details including source code references are publicly disclosed by Wordfence, substantially lowering the barrier to exploitation.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows remote unauthenticated attackers to exploit TLS/certificate handling weaknesses, leading to unauthorized access and high-availability impact. Both the Appliance (Virtual Edition) builds prior to 5.36.00.16 and Application builds prior to 5.36.00.00 are affected. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated network vector and CVSS 8.2 score make this a priority patching item for environments running Dell infrastructure monitoring.
Improper certificate validation in Dell Secure Connect Gateway 5.0 exposes both Appliance and Application deployments to unauthenticated remote exploitation, enabling MITM-style attacks that bypass TLS trust enforcement and grant unauthorized access to communications relayed through the gateway. The Appliance variant is affected below version 5.36.00.16 and the Application variant below 5.36.00.00. No active exploitation has been confirmed by CISA KEV and no public exploit code is referenced, but the zero-authentication network vector makes patching urgent for any internet-reachable SCG deployment.
Certificate hostname validation failure in Dell Secure Connect Gateway (SCG) 5.0 enables an unauthenticated remote attacker positioned as a network man-in-the-middle to present a valid TLS certificate for a different host, defeating the connection's trust model and gaining unauthorized access to intercepted communications. Both the Appliance variant (prior to 5.36.00.16) and Application variant (prior to 5.36.00.00) are confirmed affected per Dell DSA-2026-382. No public exploit or CISA KEV listing has been identified at time of analysis; the AC:H CVSS metric reflects the non-trivial network positioning prerequisite.
Improper certificate validation in Dell Secure Connect Gateway 5.0 (both Appliance and Application variants) enables an unauthenticated remote attacker with a man-in-the-middle network position to intercept and modify encrypted communications between the SCG platform and Dell's support infrastructure. Rated CVSS 7.4 (CWE-295) with high confidentiality and integrity impact, this flaw is particularly sensitive given that SCG routinely carries privileged support telemetry and credentials. No public exploit code and no CISA KEV listing have been identified at time of analysis; Dell has released patches in advisory DSA-2026-382.
Authentication bypass in the Next-Cart Store to WooCommerce Migration WordPress plugin (all versions ≤ 3.9.8) allows unauthenticated remote attackers to reach privileged migration endpoints and achieve full site takeover via arbitrary SQL execution and arbitrary file deletion. The root cause is a double design flaw: the `/wp-json/next_cart/v1/migration` REST route is registered with `permission_callback` set to `__return_true` (granting unrestricted access to all callers), and the token check falls back to the hardcoded literal `__token__` via `get_option('nextcart_token', '__token__')` whenever the database option has never been written. Once past the token check, attackers pass attacker-controlled SQL directly to `$wpdb->query()` and `$wpdb->get_results()` - enabling administrator account creation - and pass an attacker-controlled path to `unlink()`, enabling arbitrary file deletion. No public exploit or CISA KEV listing has been identified at time of analysis, though source code confirming the flaw is publicly visible in the WordPress plugin SVN repository.
Secure Boot bypass in InsydeH2O UEFI firmware allows a locally-privileged attacker to leverage the embedded UEFI Shell to execute shell commands or startup scripts that circumvent Secure Boot integrity enforcement, enabling pre-OS code execution outside the chain of trust. The vulnerability affects InsydeH2O across all tracked versions per the CPE wildcard, with remediation details deferred to OEM-specific advisories referenced in Insyde SA-2026004. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope change to C:H/I:H/A:H reflects the catastrophic trust boundary violation once exploited.
Improper access controls (CWE-862 Missing Authorization) in Tanium Comply expose compliance and vulnerability assessment data to authenticated users who lack sufficient privileges to access it. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) scores this at 7.1, with high confidentiality impact and limited integrity risk, exploitable over the network by any low-privileged Tanium account holder with no user interaction required. No public exploit code or active exploitation has been identified at time of analysis.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Authentication bypass in s-pms SPMS-Server (through v1.0) allows remote, unauthenticated attackers to forge valid administrative session tokens because a hardcoded default access-token secret is shipped in the core configuration file and is never overridden in the production environment profile. An attacker who extracts that secret from the publicly available source can then sign their own tokens and reach protected backend APIs with full administrative privileges, giving high confidentiality, integrity and availability impact (CVSS 9.8; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and EPSS is low at 0.24% (15th percentile); the real limiter is deployment hygiene, since any operator who rotates or overrides the token secret removes the flaw entirely.
Authentication bypass in Siam Ordering (siam-server) 1.0.0 lets remote attackers log in as any user, merchant, or administrator by supplying a hardcoded master verification code that ships with the server. The flaw is rooted in a hardcoded credential (CWE-259) rather than a memory-safety or logic error, so every deployment of version 1.0.0 that exposes the verification endpoint is potentially affected, with full confidentiality, integrity, and availability impact once a session is obtained. No public exploit code has been identified and the EPSS score is low (0.24%, 16th percentile), but the issue is trivially severe if the code value is known or recoverable, and no vendor-released patch was identified in the available data.
Token replay vulnerability in macropay-solutions/maravel-framework prior to version 10.74.0 enables attackers holding invalidated JWT tokens to bypass authentication and regain unauthorized API access after a predictable 2-hour window. The root cause is a lifecycle collision: the framework's O(1) Atomic Lazy Eviction model silently caps all tagged cache entries at 7,200 seconds, truncating the tymon/jwt-auth blacklist's intended 14-day retention and leaving revoked tokens cryptographically valid but logistically unblocked. No public exploit code has been identified and the CVE is not in CISA KEV, though the attack mechanism is deterministic and requires no specialized tooling.
Local privilege escalation in Waves Central for macOS (versions up to 16.6.2) allows any authenticated local user to gain root code execution by abusing a flawed XPC client authorization scheme in the product's privileged helper service. The helper validates connecting XPC clients by performing a certificate-chain equality comparison against itself rather than enforcing a pinned code requirement (application identifier and Apple Team ID), meaning any process carrying the Waves signing certificate can impersonate a legitimate client and instruct the helper to run arbitrary scripts as root. No public exploit has been identified at time of analysis; a vendor-released fix is available in version 17.0.
Administrative takeover of the Eclipse aeriOS Identity Manager (IdM) is possible because the current development-version deployment exposes its Keycloak server and PostgreSQL backing database to the network (Kubernetes NodePort services, and PostgreSQL bound to all interfaces under Docker Compose) while shipping fixed, publicly documented default credentials for the Keycloak admin and the PostgreSQL user. An attacker who can reach these services logs in with the published defaults to read or modify identity data - users, roles, client credentials, sessions, and cryptographic material - and can mint privileged identities or tokens trusted by other aeriOS components. No official release exists yet; there is no CISA KEV listing and no public exploit identified at time of analysis, though the credentials are effectively public in the source repository.
Privilege escalation to arbitrary code execution in Adobe Experience Manager (AEM 6.5 through 6.5.24, AEM as a Cloud Service through 2026.7.0, and AEM 6.5 LTS through SP2) lets a low-privileged authenticated attacker abuse an incorrect-authorization flaw to execute code and take over a victim's account or session without any user interaction. Because the CVSS scope is changed, the impact extends beyond the vulnerable component. Adobe (PSIRT) rated it 9.9 critical and shipped a fix in APSB26-98; no public exploit is identified at time of analysis.
Roo-Code's auto-approve shell execution mechanism through version 3.54.0 can be bypassed by exploiting a word-boundary mismatch between the approval gate's shell tokenizer and bash, allowing commands explicitly denied in the user's allowlist to execute silently on the developer's machine. An attacker who can influence the command string reaching the auto-execute pipeline - most plausibly via prompt injection through malicious repository content or crafted AI interactions - prefixes a denied command with an allowlisted token followed by a hash character and separator; the approval gate passes the token as safe while bash interprets the hash as a comment delimiter and executes the trailing denied payload with the agent's full privileges. No public exploit has been confirmed as actively exploited (not in CISA KEV), though a detailed technical writeup is publicly available on GitHub, lowering the barrier for exploitation.
Command allowlist bypass in Roo-Code through version 3.54.0 enables execution of shell commands that users explicitly denied from auto-approval. The vulnerability stems from the shell command parser's failure to recognize the bash pipe operator `|&` as a command separator - a crafted pipeline prefixed with an allowlisted command followed by the stderr-redirecting pipe and a denied command passes parser validation while bash executes the entire pipeline, including the denied component, with full agent privileges on the developer's workstation. A public proof-of-concept writeup exists on GitHub; no active exploitation has been confirmed by CISA KEV.
Incorrect Authorization (CWE-863) in Adobe Commerce allows unauthenticated remote attackers to bypass security controls and gain unauthorized read access across a changed security scope boundary. Affected products span Adobe Commerce 2.4.4-2.4.9, Adobe Commerce B2B 1.3.3-1.5.3, and Magento Open Source 2.4.6-2.4.9, all prior to the August 2026 security patches released under APSB26-138. No public exploit code has been identified and no active exploitation is confirmed in CISA KEV, but SSVC rates the vulnerability as automatable, making mass scanning a realistic near-term threat once technical details become more widely known.
Incorrect Authorization (CWE-863) in Adobe Commerce and Magento Open Source allows a high-privileged attacker to bypass access control boundaries and perform unauthorized writes to resources outside their intended scope, with the scope change (S:C) amplifying impact to components beyond the directly vulnerable module. All supported branches of Adobe Commerce (2.4.4-2.4.9), Magento Open Source (2.4.6-2.4.9), and Commerce B2B (1.3.3-1.5.3) prior to the August 2026 security patch cycle are affected. No public exploit or CISA KEV listing is identified at time of analysis; exploitation requires an already-authenticated admin-level session.
Incorrect Authorization (CWE-863) in Adobe Commerce and Magento Open Source allows unauthenticated remote attackers to escalate privileges and gain write access to restricted platform resources without user interaction. Scope change is confirmed: successful exploitation crosses privilege boundaries within the Commerce platform, granting access to administrative or otherwise protected functionality. SSVC classifies technical impact as total and the attack as automatable, elevating operational priority despite no active exploitation currently recorded in CISA KEV.
Incorrect Authorization in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B allows remote unauthenticated attackers to bypass access controls and read sensitive platform data, achieving a privilege-escalation effect without any user interaction. The flaw stems from CWE-863 (Incorrect Authorization), where authorization checks fail to enforce the correct permission boundaries, letting an unauthenticated network request access resources restricted to higher-privilege roles. No public exploit code has been identified at time of analysis, but the combination of PR:N and C:H on a major e-commerce platform makes this a meaningful exposure for confidential business and customer data.
Incorrect Authorization in Adobe Commerce allows remote unauthenticated attackers to escalate privileges and access sensitive information without any user interaction. The vulnerability, rooted in CWE-863, affects Adobe Commerce 2.4.4 through 2.4.9, Magento Open Source 2.4.6 through 2.4.9, and Adobe Commerce B2B 1.3.3 through 1.5.3, covering a broad range of production deployments. No public exploit code has been confirmed and CISA KEV does not list active exploitation, but SSVC flags the flaw as automatable, raising concern for mass-scanning campaigns against exposed storefronts.
Skype for Business Server's failure to properly verify cryptographic signatures (CWE-347) enables unauthenticated attackers on the same network segment to spoof identities or server endpoints, achieving high confidentiality and integrity impact across three distinct server release lines. All on-premises deployments of SfB Server 2015 CU13, 2019 CU8, and Subscription Edition CU1 below specific cumulative-update thresholds are confirmed affected, with patched releases available from Microsoft. The JWT Attack tag combined with CWE-347 indicates the flaw resides in token signature validation, where the server may accept cryptographically forged or unsigned tokens as legitimate - enabling impersonation without valid credentials. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local privilege escalation in Android's biometrics settings framework (BiometricsSettingsBase.java) allows a low-privileged app to achieve full device compromise without user interaction. The confused deputy flaw (CWE-441) in the component's onAttach lifecycle method enables a malicious app to cause the biometrics settings service - which operates with elevated system privileges - to perform privileged operations on the attacker's behalf, bypassing authentication controls. Affects Android 14, 15, 16, 16-qpr2, and 17; no public exploit or CISA KEV listing identified at time of analysis.
Remote privilege escalation in the Android Bluetooth stack (AdapterService.java) allows an attacker to bypass device pairing entirely. A logic error in handleBondStateChanged lets a bond be treated as established without the normal pairing/consent flow, granting the attacker elevated privileges on Android 15, 16, 16-qpr2, and 17 with no user interaction. Google rates it CVSS 9.8; no public exploit is identified and CISA's SSVC framework records exploitation status as none, and EPSS is very low (0.16%).
Authentication bypass via capture-replay in Microsoft Authentication Library (MSAL) for Node.js versions 1.0.0 through 5.5.x allows an unauthenticated network-adjacent attacker to spoof authenticated identity by replaying captured tokens. The CWE-294 root cause means a previously captured authentication artifact can be reused to impersonate a legitimate user, yielding high confidentiality and integrity impact consistent with the CVSS C:H/I:H scores. No public exploit or active exploitation is known at time of analysis, but Microsoft has released a patch at version 5.6.0.
Missing authorization in Microsoft Entra ID allows an attacker who already holds a valid low-privilege identity - a compromised user account, guest account, or service principal - to elevate privileges over the network without any user interaction, giving high impact to confidentiality, integrity, and availability (CVSS 8.8, AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H). Microsoft has published an advisory through MSRC (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83941), but no public exploit code has been identified at time of analysis and the issue is not in CISA KEV; EPSS is only 0.73% (52nd percentile), so this is a genuine priority-worthy finding rather than an emergency. Because Entra ID is a Microsoft-operated multi-tenant cloud service, the affected code is centrally managed and the exact tenant configuration or feature exposing the missing check is not detailed in the advisory.
Security feature bypass in Visual Studio Code before 1.136.2 allows a remote, unauthenticated attacker to circumvent a protection mechanism via a failing-open (CWE-636) code path, resulting in high confidentiality impact and limited integrity impact across a changed scope. The vulnerability is reachable over the network with low complexity but requires user interaction, suggesting an attacker must induce the victim to open a crafted workspace, file, or URI. No public exploit code and no CISA KEV listing have been identified at time of analysis, though Microsoft has released a patch.
Security feature bypass in Visual Studio Code (versions 1.0.0 through below 1.136.2) allows a remote unauthenticated attacker to circumvent a protective security control via an interpretation conflict in the editor's processing pipeline. The vulnerability requires user interaction (UI:R) - a victim must open or interact with attacker-influenced content - after which the scope change (S:C) and high confidentiality impact suggest sensitive host data or credentials may be exfiltrated beyond the process boundary. No public exploit or CISA KEV listing has been identified at time of analysis.
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a protection mechanism when a user is lured into interacting with malicious content (UI:R). Rooted in an incomplete comparison that omits required factors (CWE-693), the flaw carries a scope-changed CVSS 9.6 with full confidentiality, integrity, and availability impact, consistent with a trust/security-control bypass that can extend beyond the editor's initial boundary. A vendor patch exists; no public exploit is identified at time of analysis.
HTTP request smuggling in Visual Studio Code (versions 1.0.0 through 1.136.2) enables unauthenticated network attackers to bypass security controls through inconsistent interpretation of HTTP request boundaries. The CVSS scope change (S:C) signals that impact extends beyond the editor itself - smuggled requests can affect back-end services or proxies that VS Code communicates with, resulting in high confidentiality exposure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible, unauthenticated nature of the attack surface warrants prompt patching.
Local privilege escalation in Microsoft Authenticator for Android (versions 6.0.0 through below 16.3.0) allows a local attacker without any prior privileges to bypass the app's authentication controls and elevate privileges on the device. The scope-changed CVSS vector (S:C) reflects that a successful bypass extends impact beyond the Authenticator app itself - potentially compromising MFA-protected accounts and downstream Microsoft or enterprise services. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the wide affected version range (spanning a very broad Android release history) increases exposure surface considerably.
Privilege escalation in Microsoft SQL Server (2017 through 2025) allows a low-privileged authenticated network attacker to gain full administrative control via improper access control enforcement. The vulnerability spans four major SQL Server release trains - 2017, 2019, 2022, and 2025 - including both Cumulative Update (CU) and General Distribution Release (GDR) servicing branches. No public exploit code has been identified at time of analysis, but the low attack complexity and broad affected surface across enterprise SQL Server deployments make this a meaningful priority for patching.
Security feature bypass in Microsoft Windows iSCSI (Initiator/Target service) lets a remote, unauthenticated attacker defeat the protocol's weak authentication over the network, per Microsoft's advisory carrying a 9.8 CVSS with full confidentiality, integrity, and availability impact. The flaw spans essentially the entire supported Windows Server line (2012 through 2025) plus Windows 10 (1607/1809), and a vendor patch is available. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) enables a network-authenticated attacker to execute arbitrary code with full system impact across a broad range of Microsoft Windows releases. The vulnerability (CWE-122) affects Windows 10, Windows 11, and Windows Server 2012 through 2025, with vendor-released patches available via MSRC. No public exploit code and no CISA KEV listing are identified at time of analysis, but the low authentication bar (PR:L) and wide platform coverage make this a high-priority patch for any organization operating RRAS-enabled servers.
Use-After-Free (CWE-416) in the Windows Routing and Remote Access Service enables an unauthenticated attacker positioned on an adjacent network to execute arbitrary code on affected Windows systems. The vulnerability spans a wide range of Microsoft platforms from Windows Server 2012 through Windows Server 2025 and Windows 10/11 client versions, making the exposure surface substantial in enterprise environments where RRAS is deployed as a VPN or routing endpoint. Microsoft has released patches addressing this issue; no public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS C:H/I:H/A:H impact and adjacent-network unauthenticated attack path make it a high-priority patching target for organizations running RRAS-enabled servers.
Privilege elevation in Spring Cloud Azure (versions 1.0.0 up to but not including 7.4.0) lets a network-based, unauthenticated attacker bypass improper authentication logic (CWE-287) to gain elevated privileges. Reported by Microsoft (MSRC) with a vendor patch available; no public exploit identified at time of analysis and neither KEV nor EPSS/POC signals are present in the provided data.
Security feature bypass in the Windows TCP/IP stack allows unauthenticated remote attackers to circumvent network-level security controls across a broad range of Windows client and server versions, from Windows Server 2012 through Windows 11 25H2 and Windows Server 2025. Exploitation leverages CWE-1288 (improper consistency validation within input), meaning crafted packets with internally contradictory fields can slip past enforcement mechanisms - resulting in high integrity impact with no confidentiality or availability effect. No public exploit code has been identified at time of analysis, and Microsoft has released patches across all affected version families.
DNS response spoofing in Windows DNS Server allows unauthenticated network attackers to inject forged DNS responses by exploiting an origin validation error (CWE-346), poisoning the server's cache and redirecting downstream client resolution to attacker-controlled endpoints. All supported Windows Server releases from 2012 through 2025, plus Windows 10 versions 1607 and 1809, are confirmed affected across both full and Server Core installations. Successful cache poisoning yields full confidentiality, integrity, and availability impact - enabling credential interception, traffic redirection, and service disruption for any client relying on the compromised resolver. No public exploit identified at time of analysis, and the vulnerability is not currently listed in the CISA KEV catalog.
Capture-replay exploitation of Windows Kerberos authentication enables an attacker with network access and initial credentials to bypass authentication controls and achieve remote code execution. Affected products span virtually every supported Windows client and server release from Windows Server 2012 to Windows 11 26H1 and Windows Server 2025. No public exploit or CISA KEV listing has been identified at time of analysis, but the breadth of affected platforms and Microsoft's direct disclosure make this a high-priority patching target.
Network-based privilege escalation in Microsoft Exchange Server lets an already-authenticated attacker gain higher privileges by exploiting a missing authorization check (CWE-862). Affected on-premises builds include Exchange 2016 CU23, Exchange 2019 CU14/CU15, and the Subscription Edition; Microsoft has released fixed cumulative-update builds via MSRC. No public exploit identified at time of analysis and the flaw is not on CISA KEV, but its 9.1 CVSS with scope change and full CIA impact makes it a high-priority patch for internet-facing mail infrastructure.
Privilege escalation in Windows Shell affects Windows 11 (versions 23H2 through 26H1) and Windows Server 2025, enabling a locally authenticated low-privileged attacker to achieve full system compromise with no user interaction required. The root cause is CWE-306 - a critical internal Shell function that lacks an authentication or authorization gate, allowing a standard user account to invoke privileged operations and elevate to SYSTEM. No public exploit code or CISA KEV listing exists at time of analysis; Microsoft has issued patches via Windows Update.
Remote code execution in Microsoft SharePoint Server Subscription Edition allows an authenticated low-privileged attacker to execute arbitrary code over the network by exploiting an improper access control flaw (CWE-284). The vulnerability affects build versions from 16.0.0 up to but not including 16.0.20326.20090, which Microsoft has patched. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog at time of analysis.
Authentication bypass by spoofing in the Windows Netlogon (MS-NRPC) protocol allows an unauthenticated adjacent-network attacker to impersonate domain authentication, yielding full confidentiality, integrity, and availability compromise of the targeted system. The flaw spans Windows 10, Windows 11, and Windows Server 2012 through Server 2025, making it a broad-surface Active Directory infrastructure risk. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; however, the high CIA impact warrants prompt patching in domain-connected environments.
Authentication bypass in DeepSeek Harness before 0.1.2-alpha.1 lets attackers seize full control of the local agent by spoofing the HTTP Host header, because the control-plane API trusts the client-supplied Host value instead of the actual TCP connection origin. An unauthenticated attacker who lures an operator's browser to a malicious page (via DNS rebinding or a cross-site 'simple' POST) can invoke privileged methods such as commands/execute with danger-full-access, escalate approval policies to unconfined execution, and exfiltrate all stored conversations. No public exploit is identified at time of analysis, though the fixing commit and a VulnCheck advisory document the exploitation mechanics in detail.
Unauthenticated remote access control bypass in Fortinet FortiSandbox 4.2.x through 5.0.x - and its Cloud and PaaS variants - allows network-reachable attackers to retrieve sensitive information and disrupt availability by sending crafted HTTP requests, with no credentials or user interaction required. Fortinet's confirmed CVSS temporal metrics include E:P (proof-of-concept exploit code exists) alongside RL:O (official remediation available) and RC:C (confirmed), establishing this as an actively documented, patchable risk against sandboxing infrastructure that processes enterprise malware submissions. The scope-changed vector (S:C) combined with high availability impact (A:H) indicates the access control failure cascades beyond the directly targeted HTTP endpoint to other components within the FortiSandbox platform.
UEFI Secure Boot bypass in Cisco UCS Servers and UCS-based appliances allows authenticated users with 'user' or 'admin' role credentials - or unauthenticated attackers with physical device access - to disable Secure Boot protections and execute unauthorized software at boot time. The flaw stems from UEFI Shell memory-write commands remaining accessible while Secure Boot is active, enabling direct manipulation of Secure Boot validation variables in UEFI memory. A successful exploit undermines firmware integrity controls, potentially allowing persistent pre-OS implants or untrusted bootloaders on enterprise server infrastructure. No public exploit code or CISA KEV entry has been identified at time of analysis.