Authentication Bypass
Monthly
Unauthenticated remote write to any contact record is possible in OpenSignLabs OpenSign through version 2.37.0 via the updatecontacttour Parse cloud function, which performs no authentication or authorization checks before accepting and applying updates to arbitrary contact records. Any internet-reachable deployment is vulnerable to data corruption or overwrite of contact records for all users system-wide without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability's zero-prerequisites nature and straightforward exploitation model make it a realistic target for automated abuse.
Unauthenticated contact record enumeration in OpenSignLabs OpenSign through 2.37.0 exposes all stored personally identifiable information to remote attackers without credentials. The `getcontact` Parse cloud function executes with `useMasterKey`, which bypasses Parse Server's native access control layers (ACLs and Class-Level Permissions), and contains no compensating authentication or authorization logic. Any network-reachable attacker can call this function, supply arbitrary object IDs, and retrieve full contact records including PII at scale. No public exploit has been identified at time of analysis, and no KEV listing exists.
Unauthenticated remote attackers can invoke the stripeCreateIntent GraphQL mutation in Chaskiq (through commit 46dfdd1) without any session or credential, enabling manipulation of Stripe payment intents for any tenant on the platform. The root cause is CWE-306 (Missing Authentication for Critical Function): the mutation bypasses all authentication and authorization checks, exposing a financial operation to the open internet. No public exploit or CISA KEV active exploitation has been identified at time of analysis, but the trivially low attack complexity (AV:N/AC:L/PR:N/UI:N) means any internet-reachable instance with Stripe configured is structurally exploitable.
Unauthenticated remote access to Stripe Billing Portal sessions in Chaskiq through commit 46dfdd1 allows any attacker to mint valid customer portal sessions for arbitrary tenants by invoking the `stripeCustomerPortal` GraphQL mutation without credentials. The mutation performs zero authentication or tenant-ownership checks before calling the Stripe API, enabling cross-tenant subscription manipulation - including plan changes and cancellations - against any Chaskiq-hosted tenant with Stripe Billing configured. No public exploit code has been identified at time of analysis, though the attack surface requires only network access and knowledge of a target tenant identifier.
Portainer CE through 2.44.0 exposes root-level Docker host access to any authenticated low-privileged user via a URL path normalization flaw in the Docker proxy endpoint. The authorization middleware evaluates a non-canonical request path (e.g., percent-encoded slashes, double slashes, or traversal sequences) differently from the proxy layer that ultimately forwards it to the Docker daemon - allowing crafted requests to bypass all access controls while executing with full Docker API privileges. No active exploitation has been confirmed (no CISA KEV listing) and no public exploit code has been identified at time of analysis; EPSS data was not provided in the source intelligence.
Authorization bypass in Commvault CommServe allows remote attackers to invoke a limited set of command-execution operations without passing the intended authorization checks, per Commvault security advisory CV_2026_07_9. The flaw carries a CVSS 4.0 base score of 9.2 with high impact to confidentiality, integrity, and availability, and affects Commvault Cloud deployments across the CommServe, Web Server, Command Center, MediaAgents, Clients, and HyperScale X components. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authorization bypass in Commvault CommServe permits attackers to circumvent the command-execution allowlist, gaining unsanctioned command execution across the backup-management control plane. Because CommServe orchestrates the entire Commvault environment, a successful bypass can cascade to Webservers, Command Center, Media Agents, Clients and HyperScale X, threatening confidentiality, integrity and availability of protected data. Rated CVSS 4.0 9.2 (critical) by Commvault; no public exploit identified at time of analysis and it is not listed in CISA KEV.
IIOP NameService in Red Hat JBoss Enterprise Application Platform (EAP) accepts bind operations without authentication, allowing unauthenticated network attackers to register malicious CORBA object references under arbitrary JNDI names. When legitimate clients subsequently perform JNDI lookups, they resolve the attacker's malicious Object Request Broker (ORB), enabling man-in-the-middle interception of CORBA/RMI-IIOP invocations or denial-of-service on dependent application flows. EPSS data was not provided; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.
Undertow's AJP listener unconditionally trusts the ssl_cert and is_ssl AJP request attributes without requiring a shared-secret, allowing an unauthenticated remote attacker with direct TCP access to port 8009 to impersonate any X.509 client certificate identity and bypass CLIENT-CERT mutual TLS authentication entirely. Deployments where Undertow acts as a back-end behind a reverse proxy - with CLIENT-CERT authentication enforced at the proxy layer but the AJP port exposed on an internal network - are directly at risk of identity spoofing and authorization bypass. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog; however, the bypass primitive is architecturally simple for any attacker who has obtained internal network access to the AJP port.
Privilege escalation in the `openvt -u` utility allows a local low-privileged attacker to obtain passwordless root login on Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. The flaw lies in `authenticate_user()`, which resolves VT ownership via `stat("/proc/<pid>/fd/0")` - a call that follows the symlink to the underlying TTY device node rather than inspecting the owning process, causing the check to read the device node's UID rather than the process owner's UID. When a privileged user logs out and TTY device node ownership reverts to root or the getty owner while an attacker's process still holds fd 0 on that TTY, the check incorrectly authorizes a passwordless `login -f root` execution. No public exploit is identified at time of analysis and there is no CISA KEV listing, but the root-level impact makes this a high priority for environments using the affected `kbrequest`/init deployment pattern.
Privilege escalation in MRTG (Multi Router Traffic Grapher) allows a local low-privileged attacker to gain elevated file ownership on the host system. When the MRTG daemon is launched as root and then drops privileges, a CWE-59 symlink-following flaw in PID file handling lets an attacker pre-place or manipulate a symlink at the expected PID file path, causing the root process to change ownership of an arbitrary existing file to the daemon user. Affected platforms include Red Hat Enterprise Linux 6 through 10; no public exploit code or CISA KEV listing has been identified at time of analysis.
Insecure Direct Object Reference in Chiline Cloud (Inventec Appliances) versions up to and including 4.5.9 exposes sensitive user data to unauthenticated remote attackers. By manipulating a specific request parameter - likely a user identifier or resource key - an attacker can bypass authorization checks and read account data belonging to arbitrary other users. Reported by TWCERT and catalogued under EUVD-2026-55925, no public exploit code or active exploitation has been confirmed at time of analysis, though the trivial exploitation conditions (network-accessible, no authentication, no user interaction) make this a high-priority disclosure risk.
Missing authorization checks in SAP ABAP Developer Tools (the Eclipse-based IDE for ABAP development) allow any low-privileged SAP user to execute unauthorized database operations against SAP NetWeaver AS ABAP backends. The flaw spans a wide range of SAP_BASIS releases (750 through 920) and yields full confidentiality, integrity, and availability compromise of the ABAP application layer - including the ability to read sensitive business data, modify application records, and disrupt legitimate user access. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and broad version coverage elevate real-world risk considerably for enterprises running ADT-connected NetWeaver systems.
Unauthenticated remote access to SAP Manufacturing Integration and Intelligence (MII) scheduling functions is possible due to a missing authorization check on scheduling-related API endpoints. Any network-reachable attacker without credentials can retrieve, create, modify, or delete scheduling data managed by the application, impacting confidentiality, integrity, and availability at a low severity level each. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the trivial exploitation conditions - no authentication, no user interaction, low complexity - lower the barrier to opportunistic abuse significantly.
Missing authorization on the Cost Servlet in SAP Manufacturing Integration and Intelligence (SAP MII) exposes backend operations to unauthenticated remote attackers via crafted HTTP requests with specific parameter values. Successful exploitation grants read, create, modify, and delete access to application-managed business data, producing a limited but tripartite impact across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at this time, though the zero-privilege network vector lowers the bar for opportunistic probing.
SSO-based account takeover in usememos Memos v0.27.1 lets a remote, unauthenticated attacker impersonate any user by exploiting the ssoCredentials path of the SignIn handler (server/router/api/v1/auth_service.go), which matches a federated identity solely on an attacker-controllable identifier (e.g. email or username) instead of the identity provider's stable subject claim. Any deployment that has an OIDC/OAuth SSO provider enabled is affected, and a successful attack yields full control of the targeted account, including potentially administrative accounts. The flaw carries CVSS 9.8 and CWE-287; there is no public exploit identified as weaponized at time of analysis, though a referenced GitHub gist appears to be a researcher write-up, and EPSS is low at 0.22%.
Broken access control in ERPNext's accounts module permits authenticated low-privilege users to invoke privileged write operations across five functions - merge_account, pause_job_for_doc, trigger_job_for_doc, change_release_date, and update_cost_center - without any server-side permission enforcement. All v15 releases prior to 15.112.0 and all v16 releases prior to 16.22.0 are affected. An attacker with any valid ERPNext session can directly call these whitelisted API endpoints to corrupt financial accounts, payment reconciliation jobs, purchase invoices, and cost centers beyond their assigned role, with no public exploit identified at time of analysis.
Broken access control in ERPNext's Accounts Receivable and Payable report engine allows any authenticated user to read cross-company financial data they are not authorized to view. The `ReceivablePayableReport.prepare_conditions()` method fails to enforce Customer and Supplier user permissions against the Payment Ledger Entry dynamic-link party field, meaning permission boundaries set via Frappe's user permission system are silently bypassed for this report path. Fixed in versions 15.112.0 and 16.23.0; no public exploit identified at time of analysis.
Privilege escalation in Red Hat OpenShift AI's Data Science Pipelines component allows authenticated tenants to bypass authorization controls in the setDefaultServiceAccount function by submitting a crafted CreateRun request that references a more privileged ServiceAccount than they are entitled to use. Successful exploitation enables the tenant's pipeline containers to run with elevated Kubernetes RBAC permissions, resulting in cross-namespace secret disclosure and the ability to execute commands inside other tenants' pods. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Credential derivation in Red Hat OpenShift AI's Data Science Pipelines Operator allows unauthenticated remote attackers to predict MariaDB root/user passwords and MinIO access/secret keys by exploiting a cryptographically weak PRNG (CWE-338). Any attacker who can reach the MinIO Route or MariaDB Service over the network can compute valid credentials without prior authentication, then access all pipeline artifacts and metadata stored in the system. No active exploitation is confirmed and no public exploit code has been identified at time of analysis, but the CVSS 7.5 High rating with AV:N and PR:N reflects a no-authentication-barrier condition against exposed services.
Privilege escalation in Red Hat OpenShift AI (RHOAI) training operator overlay allows any namespace editor to manage TrainJob resources beyond their intended authorization scope. The RHOAI overlay incorrectly injects trainjobs CRUD permissions into the native Kubernetes edit ClusterRole, violating the principle of least privilege. When chained with a companion flaw (TRN-01) that permits arbitrary pod configuration within TrainJobs, a remote attacker holding namespace editor credentials could escalate to arbitrary code execution - no public exploit is identified at time of analysis, and KEV listing has not been confirmed.
Authorization bypass in Feast's materialization API endpoints within Red Hat OpenShift AI (RHOAI) permits full re-materialization of all feature views by sending a crafted request that omits the feature_views field, circumventing permission checks. The consequence is a multi-tenant Denial of Service through data corruption and significant resource exhaustion, impacting all tenants sharing the deployment. No public exploit code has been identified at time of analysis, but the bypass mechanism is straightforward - a structural omission in the request body - making independent rediscovery likely for any attacker with API access.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
Authentication bypass in TrustyAI Service (TAS) within Red Hat OpenShift AI (RHOAI) exposes the backend API to any pod on the cluster network without requiring valid credentials. The CVSS vector (AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that an attacker with a pod on the cluster-such as through a compromised workload or a malicious tenant pod in a multi-tenant deployment-can read, modify, delete, or poison AI model monitoring data and configurations with no additional barriers. No public exploit code or CISA KEV listing has been identified at time of analysis, but the root cause (CWE-306: Missing Authentication for Critical Function) means exploitation is trivially simple once cluster network adjacency is established.
Authentication bypass in the Models-as-a-Service (MaaS) API component of Red Hat OpenShift AI (RHOAI) lets any pod already running in the cluster impersonate arbitrary users by forging the X-MaaS-Username and X-MaaS-Group HTTP headers, which the service trusts without independent verification. Because the MaaS API performs no first-party authentication and defers entirely to a Kuadrant AuthPolicy gateway that can be circumvented, a low-privileged workload can mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and exfiltrate model-access configuration - a full cross-tenant privilege escalation. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the 9.9 CVSS reflects near-total impact.
The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.
Cross-channel message deletion in Spacebar Server (all commits before 8d126f4) permits authenticated users holding MANAGE_MESSAGES permission in any channel to delete messages residing in channels they do not control. Both the single-delete and bulk-delete API handlers failed to scope their database queries to the channel_id present in the request path, allowing attacker-supplied message IDs from foreign channels to be processed and destroyed. A publicly available exploit exists, with the root cause and fix confirmed by the upstream security advisory GHSA-62g6-28hv-h6hc; no CISA KEV listing has been issued at time of analysis.
Incomplete authorization in Dokploy's WebSocket handlers prior to v0.29.13 allows any authenticated organization member to obtain root terminal access to servers and read logs or statistics for services they were explicitly denied access to. The four affected handlers (terminal.ts, docker-container-terminal.ts, docker-container-logs.ts, docker-stats.ts) verify organization membership but never call checkServiceAccess, getAccessibleServerIds, or accessedServices, nullifying all fine-grained role-based access controls. No public exploit or CISA KEV listing exists; however, the attack requires only a valid low-privilege organization account, making this a meaningful privilege escalation risk in any multi-tenant Dokploy deployment.
Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.
GitHub App provider injection in Dokploy PaaS (prior to v0.29.13) allows unauthenticated remote attackers to insert attacker-controlled GitHub App credentials - including client_secret, webhook_secret, and PEM private key material - into any target organization's configuration by forging the state parameter in the GitHub OAuth callback route. The route /api/providers/github/setup performed no session authentication (CWE-306), blindly trusting organizationId and userId values supplied by the caller in the state query parameter. No public exploit identified at time of analysis; a vendor-released patch is confirmed available as v0.29.13.
Interactive host-shell access in Dokploy prior to 0.29.13 is obtainable by any authenticated platform user due to a missing authorization check in the WebSocket terminal handler. The handler at apps/dokploy/server/wss/terminal.ts validates the session token but never checks whether the user holds an organization role or server-access grant before spawning a terminal for serverId=local, yielding full interactive shell access on the Dokploy host. No confirmed active exploitation or public exploit code has been identified at time of analysis, but the public security advisory and fix diff make reconstruction trivial for any authenticated user.
Privilege escalation via missing authorization in Dokploy, a self-hostable Platform-as-a-Service, lets any authenticated organization member open a root shell inside arbitrary containers on a self-hosted instance. The /docker-container-terminal WebSocket handler authenticated the caller but never checked the attacker-supplied containerId against the caller's role, organization, or service scope before invoking docker exec. Fixed in 0.29.13; no public exploit identified at time of analysis, though the upstream fix commit is public.
Unauthenticated file exfiltration in Flowise 2.2.4-3.1.4 is possible because the POST /api/v1/openai-assistants-file/download endpoint was incorrectly added to the application's global authentication whitelist, causing all session and API key verification to be skipped unconditionally. Any remote, unauthenticated attacker who can supply valid chatflowId, chatId, and fileName identifiers can retrieve private files from any chatflow on the instance, including those belonging to other workspaces or organizations in a multi-tenant deployment. A public proof-of-concept exploit is available via GitHub, and no KEV listing has been confirmed at time of analysis.
Full application database read in Metabase is achievable by any authenticated low-privileged user due to a missing authorization check (CWE-862). Any user with a valid account - regardless of their assigned role or permissions - can issue requests that return the entire contents of the Metabase backend database, potentially exposing database connection credentials, API keys, user account data, and sensitive query results. No public exploit has been identified at time of analysis, but the low exploitation complexity and broad attacker pool (any registered user) make this a high-priority remediation item.
Cross-tenant authorization bypass in Dokploy 0.29.8 and earlier lets an authenticated organization member with backup permissions reach another organization's S3 backup destinations by supplying a client-controlled destinationId that is never checked against their active organization. Because the referenced destination's S3 accessKey and secretAccessKey are materialized on the attacker's service host, the attacker can read a victim tenant's backup objects and redirect or poison backups across tenant boundaries. No public exploit identified at time of analysis, but the flaw is trivially reachable and breaks the core multi-tenant isolation of the platform (CVSS 9.6, scope-changed).
Cryptographic signature validation failure in Pega Platform (Pega Infinity) versions 8.5.0 through 25.1.2 enables low-privileged network attackers to forge or manipulate JWT tokens, bypassing authentication and authorization controls. The vulnerability maps to CWE-347 and is tagged as a JWT attack vector capable of authentication bypass, with high confidentiality and integrity impact confirmed in the vendor's own CVSS 4.0 assessment. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and network accessibility make this a meaningful risk for any organization running affected Pega Infinity deployments.
Cross-organization server deletion and SSH key disclosure in Dokploy affects all instances running versions 0.28.7 through 0.29.12. The server.remove tRPC mutation accepts a caller-supplied serverId without verifying organizational ownership, allowing an authenticated owner or administrator in one organization to delete server registrations and all associated deployment records belonging to a completely separate organization - and to receive that organization's plaintext SSH private key as a side effect. No public exploit code has been identified at time of analysis, but the fix is available in version 0.29.13 and the GitHub advisory (GHSA-3rpx-c3j9-q99x) and patch PR are public.
Cross-tenant IDOR in Prospero Flow CRM before 5.4.8 allows any authenticated user to blindly overwrite contact records belonging to other companies and exfiltrate their personal data as vCard files, simply by supplying an arbitrary numeric contact ID. The contact save and vCard export endpoints performed no company-scoping on their database queries, so a user authenticated to Company A could tamper with or harvest contacts owned by Company B without any special knowledge beyond a valid integer identifier. No public exploit or CISA KEV listing has been identified at time of analysis, but the vulnerability is trivially exploitable in any multi-tenant deployment and the full fix has been released as v5.4.8 (and later v5.5.3).
Hard-coded credentials embedded in the Zyxel WAH7601 mobile Wi-Fi hotspot firmware expose sensitive constants within the device executable, enabling adjacent-network attackers without any prior privileges to bypass authentication and achieve high-impact confidentiality and integrity compromise. All WAH7601 firmware versions through 20.07.2026 are confirmed affected per TR-CERT advisory TR-26-0799 and NVD. No public exploit code or active exploitation has been identified at time of analysis, but the low attack complexity characteristic of CWE-798 makes this a credible near-term risk in environments where adjacent access is not tightly controlled.
Privilege escalation in Roskus Prospero Flow CRM before version 5.2.1 permits any authenticated user - regardless of assigned role - to grant any application role the complete set of system permissions by sending a crafted POST request to the permission save endpoint. The vulnerable `PermissionSaveController` accepted a user-supplied `roles` array and invoked Spatie Permission's `syncPermissions()` with no prior authorization check, making low-trust authenticated accounts a direct path to full administrative control. No public exploit or CISA KEV listing has been identified at time of analysis, but the publicly accessible commit diff documents the exact endpoint and flaw mechanism, substantially lowering the exploitation barrier for any attacker holding CRM credentials.
Missing authorization in OpenSignLabs opensignserver through 2.37.0 lets unauthenticated remote attackers irreversibly decline any in-flight signing document and forge the decline attribution to an arbitrary user. The vulnerable declinedoc Parse cloud function writes the IsDeclined flag, DeclineReason text, and a caller-supplied DeclineBy pointer to the document record without verifying the caller's identity, enabling both workflow termination and evidentiary record falsification. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.
Authentication bypass in opensignserver through 2.37.0 exposes all stored files to unauthenticated remote attackers by allowing them to mint MASTER_KEY-signed file access tokens via the getsignedurl Parse cloud function. The bypass requires no credentials and no prior knowledge of valid document records - supplying any arbitrary string as the docId parameter causes the function to skip its isAuthenticated check entirely and issue a fully trusted signed token. No public exploit code or CISA KEV listing exists at time of analysis, but the bypass condition is trivially reproducible from the CVE description alone, making this a realistic and immediate threat to any internet-exposed instance storing sensitive signed documents.
Cross-tenant authorization bypass in Attendize through commit 9289acb permits an authenticated organizer to inject persistent, mandatory survey questions into a different organizer's events by supplying an arbitrary event_id to the POST /event/{event_id}/question/create endpoint. The postCreateEventQuestion method resolves the target event without applying tenant-isolation scoping, so the write succeeds across tenant boundaries; the injected question is then irremovable by the victim because the victim's account-scoped delete path cannot resolve a record owned by another tenant. No public exploit has been identified at time of analysis, and the vulnerability has not been listed in the CISA KEV catalog.
Broken object-level authorization in OpenSignLabs OpenSignServer through 2.37.0 exposes complete contract records - including sender and signer PII and pre-signed document download URLs - to unauthenticated remote attackers via the getDocument Parse cloud function. The function internally calls useMasterKey, bypassing Parse's ACL enforcement, and returns full records whenever the document's IsEnableOTP flag is false, which is the default configuration across all deployments. No public exploit has been identified at time of analysis, but the network-accessible, zero-authentication attack path against default configurations makes this a high-priority data protection issue, particularly for organizations subject to GDPR or similar data regulation.
Unauthenticated remote access to all stored contract documents is possible in OpenSignLabs opensignserver through version 2.37.0 due to a missing authentication check in the fileupload Parse cloud function. Any unauthenticated attacker who can reach the endpoint can supply an arbitrary URL and receive a MASTER_KEY-signed file access token, completely defeating the only access control layer protecting stored documents. No public exploit has been identified at time of analysis, but the zero-privilege, low-complexity attack vector makes this highly accessible to unsophisticated threat actors.
Use-after-free in the Linux kernel's TIPC (Transparent Inter-Process Communication) subsystem lets a local actor trigger a write to freed slab memory via the accept() error path of tipc_sk_create(). When socket insertion into the per-netns rhashtable fails, sock->sk is left dangling instead of NULLed, so tipc_release() bypasses its own NULL guard and calls lock_sock() on the freed sk. It affects kernels using the AF_TIPC protocol across many stable branches (fixes backported to 5.4.x through 6.18.x and mainline 7.x); there is no public exploit identified at time of analysis and it is not in CISA KEV, with a low EPSS of 0.18%.
Recursive locking deadlock in the Linux kernel audit subsystem causes a complete, unrecoverable kernel hang when a file matching an executable audit rule is renamed. Affected kernels from 4.3 through stable branches prior to 6.6.148, 6.12.101, 6.18.42, 7.1.6, and 7.2-rc1 are vulnerable. Any local user able to rename a file that matches an active exe= audit rule can trigger the deadlock, forcing a hard reboot; no public exploit exists and EPSS is 0.18%, consistent with the specific preconditions required.
Missing authentication in dulldusk/phpFM through version 1.8.0 exposes the complete file manager to unauthenticated remote attackers because the default configuration ships with an empty auth_pass value. The flawed check in index.php (line 637, 'if ($auth_pass == '' || $loggedon==$auth_pass)') short-circuits to true whenever the password is unset, granting anyone full read, write, delete, and upload access to the server filesystem. CVSS 9.8 (CWE-306); no public exploit identified at time of analysis, though the vulnerable logic is directly visible in the referenced public source and is trivially reproducible.
Unauthenticated access to complete historical sensor data is possible in FUXA through version 1.3.3 because the DAQ_QUERY Socket.IO event handler in server/runtime/index.js omits the isSocketAdminAuthorized() check that guards every other sensitive Socket.IO event. Remote attackers can exfiltrate all sensor history without credentials even on deployments where secureEnabled=true is configured, silently undermining an operator's assumption that authentication is fully enforced. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS AV:N/AC:L/PR:N vector confirms this is trivially exploitable by any network-reachable party.
Remote unauthenticated account takeover in fastschema through v0.15.1 is enabled by a TOCTOU race condition in the OTP-based account recovery flow. The verifyOTPSession function in pkg/auth/local.go reads and increments the attempt counter in separate non-atomic operations, allowing concurrent HTTP requests to race past the attempt limit before any counter update is committed. With no effective limit enforced on a 6-digit OTP (1,000,000 possible values), an attacker can brute-force valid codes; no public exploit is identified at time of analysis and this CVE is not in CISA KEV.
Remote code execution in NASA fprime-gds through version 3.4.3 lets an unauthenticated remote attacker fully compromise the ground data system and inject arbitrary commands to any connected spacecraft. The Flask ground station exposes every endpoint without authentication (CWE-306), while a path traversal in the upload/download handler permits reading and writing arbitrary files, and a hardcoded Flask secret key (CWE-321) enables session forgery; chained, they yield code execution on the ground station host. No public exploit is identified at time of analysis, but the CVSS 9.8 rating and unauthenticated network vector make this a high-priority, real-world risk for anyone running F Prime ground software.
Improper authorization in Daptin through v0.12.34 lets unauthenticated remote guests perform full CRUD (read, create, update, delete) on all usergroup records, effectively bypassing access control on the platform's group and permission objects. The flaw arises because permission checks treat a null/zero UserId as a valid ownership match, so a guest whose session UserId is null is granted owner-level rights over ownerless usergroup rows. No public exploit identified at time of analysis, but the CVSS of 9.1 (network, no auth, no interaction) reflects that manipulating usergroups can be leveraged to escalate privileges and corrupt the platform's authorization model.
Cross-tenant authorization bypass in fosrl Pangolin through v1.20.0 lets an authenticated user reuse an access token minted for one resource to authenticate against any other resource in any organization. Because the authWithAccessToken.ts handler validates the token without binding it to the requested resourceId, a token scoped to resource X in organization A is accepted for resource Y in organization B, collapsing multi-tenant isolation. Rated CVSS 9.6 (CWE-639); no public exploit identified at time of analysis, though the vulnerable code path is disclosed in the referenced source file.
Unauthenticated access to Apache Ranger Download APIs on versions 2.8.0 and earlier exposes sensitive authorization policy data to any remote attacker with network connectivity. The missing authentication check (CWE-306) means no credentials or privileges are required to invoke these endpoints and retrieve their output. No public exploit code has been identified at time of analysis, but the low complexity and zero-authentication nature of the CVSS vector (AV:N/AC:L/PR:N/UI:N) makes this trivially exploitable by any attacker who can reach the Ranger Admin interface.
Improper access control in the Weaver component of Samsung Mobile devices allows a local attacker without elevated privileges to render the device inoperable, achieving high integrity and availability impact. All Samsung Mobile devices running Weaver prior to the SMR Aug-2026 Release 1 security update are affected. No public exploit code or active exploitation has been confirmed at time of analysis, but the low attack complexity and absence of privilege requirements lower the bar for abuse by a local threat actor.
Privilege escalation via REST API authentication bypass in the CheckView WordPress plugin before 2.3.2 allows an unauthenticated attacker to perform any REST action available to a logged-in administrator - including creating a new administrator account - by tricking an admin into opening a crafted link. The plugin's authentication filter is applied globally to all REST routes rather than only to CheckView's own endpoints, and it unconditionally discards authentication errors for any request whose URI merely contains a CheckView-specific string, bypassing WordPress's nonce enforcement entirely. A publicly available exploit from WPScan demonstrates this path; no confirmed active exploitation (CISA KEV) has been recorded at time of analysis.
Authentication bypass in the AutoNetTV Relay WordPress plugin (all versions before 3.0.14) allows unauthenticated remote attackers to obtain a WordPress administrator session cookie by triggering the plugin's scheduled content-synchronization task under a specific server configuration. The plugin issues an admin authentication cookie during the sync task without performing any capability or authorization check, and on servers where the scheduled task completes before the HTTP response is committed, the cookie is returned to the triggering request. A public proof-of-concept exploit exists, reported by WPScan; no KEV listing has been identified at time of analysis.
Account takeover via broken password-reset rate limiting in the Login & Register Forms WordPress plugin (versions before 4.0.2) allows unauthenticated remote attackers to brute-force verification codes and seize any account, including administrator accounts. Both the verification code and the per-source attempt counter are keyed on client-controlled data, meaning an attacker can reset the rate limit at will by manipulating that value - rendering the lockout mechanism entirely ineffective. Exploitation requires the 'verification-code reset mode' to be enabled; a publicly available proof-of-concept from WPScan demonstrates the technique, though EPSS sits at only 0.15% (4th percentile), indicating limited observed exploitation activity to date.
Account takeover in the Login & Register Forms WordPress plugin (before 4.0.2) is enabled by a fundamentally broken password reset verification design: the plugin keys the 'verification completed' state to a client-controlled value rather than binding it server-side to the account under reset or to the authenticated session of the party completing verification. An unauthenticated attacker who can observe or manipulate this state during or after a legitimate reset flow can claim ownership of that completed verification and set a new password for any targeted account, including administrator accounts. A publicly available exploit has been published by WPScan, and no public exploit identified at time of analysis translates to KEV, though POC availability materially lowers the exploitation threshold.
Password reset abuse in the Single Sign On For TNG WordPress plugin (versions before 2.2.0) allows unauthenticated attackers to reset the password of any account, including administrators, resulting in full site takeover. The flaw stems from improper validation of the password reset request, and publicly available exploit code exists, though EPSS scores the exploitation probability at a low 0.15% (4th percentile). It is not listed in CISA KEV, so exploitation is currently proof-of-concept rather than confirmed active in-the-wild use.
Unauthenticated content injection in Arvow AI SEO Writer WordPress plugin (before 1.5.4) allows remote attackers to create arbitrary posts and pages and extract author account and taxonomy information by exploiting a PHP type juggling flaw in a REST endpoint. The bypass is effective exclusively when the plugin has not been configured post-installation, making freshly deployed or abandoned instances the primary target. A public proof-of-concept is available via WPScan; despite this, EPSS sits at 0.15% (5th percentile) and no CISA KEV listing exists, indicating no public exploit has driven mass exploitation at time of analysis.
Account takeover in the BricksForge WordPress plugin (versions before 3.1.8.8) is enabled by a missing server-side identity check during password change form submissions, allowing unauthenticated remote attackers to set arbitrary passwords for any WordPress user, including site administrators. The vulnerable state is effectively the default configuration for any site that has deployed BricksForge's password update form action, since current-password verification is disabled by default in that action. A publicly available exploit exists; active exploitation has not been confirmed by CISA KEV, but the direct path to admin-level account takeover makes this a critical remediation priority for affected deployments.
Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user - including low-privilege subscribers - to read and delete arbitrary files under the WordPress installation directory. The weakness exposes sensitive configuration secrets such as database credentials stored in wp-config.php, and enables deliberate denial of service through file deletion. A publicly available exploit exists per WPScan reporting, though EPSS remains very low (0.14%, 4th percentile), suggesting targeted rather than broadly automated exploitation at time of analysis.
Full network takeover via authentication bypass in the InfiniteWP Client WordPress plugin before 1.13.6 affects WordPress Multisite installations, where the plugin fails to validate the site-connection state and the authenticity of requests to its remote-management endpoint. Unauthenticated remote attackers can bind their own management key, hijack an administrator session, and gain control of every site in the network, culminating in remote code execution. No public exploit identified at time of analysis; EPSS is low at 0.19% (9th percentile) despite the maximal 9.8 CVSS, and a vendor patch is available.
Privilege escalation in the Solace Extra WordPress plugin (versions before 1.6.1) allows any authenticated user with Subscriber-level access to modify site-wide presentation settings and permanently delete imported site-builder content by exploiting missing capability checks across multiple AJAX endpoints. The plugin incorrectly exposes nonce values on admin-accessible pages that low-privileged users can reach, collapsing the intended authorization boundary between Subscriber and Administrator roles. A publicly available proof-of-concept exists via WPScan; no public exploit identified at time of analysis has been confirmed by CISA KEV, and the EPSS score of 0.13% (3rd percentile) reflects low observed exploitation probability to date.
The Home Assistant iOS Companion app silently executes tag-triggered automations when any co-installed untrusted app forwards a crafted tag event via iOS universal links, bypassing physical scan validation entirely. Affected versions are all iOS Companion app releases prior to 2026.5.0; the underlying Home Assistant core CPE (cpe:2.3:a:home-assistant:core:*:*:*:*:*:*:*:*) is also cited. Because automations can control physical devices such as smart locks and alarms, the I:H CVSS metric reflects real-world consequences beyond software state. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Silent automation execution in the Home Assistant Android Companion App prior to 2026.8.1 allows any co-installed app on the device to trigger arbitrary HA automations by forwarding a crafted tag URL to an exported Activity without user confirmation. The flaw exists because TagReaderActivity accepted both physical NFC intents and OS-routed deep links identically, with no caller validation or approval prompt before dispatching the tag scan to the Home Assistant server. No public exploit has been identified at time of analysis, but the attack is unattended and can control physical actuators such as locks or alarms.
The `$import-pnp` operation in Pathling Server allows low-privileged callers to supply an arbitrary `exportUrl`, causing the server to forward its configured PNP credentials to an attacker-controlled FHIR endpoint and stage the returned files as trusted local sources - effectively bypassing the `allowableSources` allowlist that guards the standard `$import` operation. All Pathling Server deployments prior to version 2.0.0 with PNP credentials configured are affected, with high confidentiality and integrity impact (credential theft and unauthorized data import). No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack requires only low-privilege API access and is low-complexity.
Pathling Server before version 2.0.0 permits authenticated callers holding only coarse operation-level authorities (e.g., `pathling:search`) to act on arbitrary FHIR resource families - including resource types they are not explicitly authorized to read or write - because typed search, update, and batch handlers enforce the operation-level authority check but skip the documented per-resource authority check (e.g., `pathling:read:Patient`). The flaw breaks the two-factor authorization model the product documents, exposing potentially all FHIR resource families to any valid operation-authority holder. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis; the vulnerability is fixed in Pathling Server 2.0.0.
Missing authentication in the LightRAG API server (HKUDS/LightRAG) through version 1.5.4 exposes every management endpoint to unauthenticated network attackers, because the server binds to 0.0.0.0 by default while authentication is off unless explicitly configured. Any attacker with network reach can read indexed document content, upload or delete documents, rewrite the knowledge graph, cancel ingestion pipelines, clear caches, and consume LLM/API credits. No public exploit identified at time of analysis, but exploitation is trivial via a single unauthenticated HTTP request, and the fix in 1.5.5rc1 is largely a hardening/warning change rather than an enforced secure default, so operator action is still required.
Insecure direct object reference in TestLink 1.9.20 and earlier allows any authenticated user - including low-privilege guest accounts - to retrieve arbitrary file attachments from projects they have no membership in, by supplying sequential integer IDs to the attachmentdownload.php endpoint. The handler performs no project membership or role authorization check, enabling bulk enumeration of all attachments across the entire installation. No public exploit has been confirmed at time of analysis, though a researcher writeup exists; the attack is trivially automatable due to the sequential integer ID scheme.
Incorrect authorization in the Nexus Repository 3 CE/Pro repository-creation UI allows an authenticated user with a format-scoped delegated repository-admin privilege to create repositories in unauthorized formats - bypassing the intended scope boundary. Affected are all releases from 3.0.0 through 3.94.x; version 3.95.0 resolves the flaw. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, but the integrity impact is high given that unauthorized repository types could be introduced into a managed artifact store, potentially tainting software supply chain pipelines.
Insufficient session expiration in Sonatype Nexus Repository 3 allows a previously-authenticated user to retain full repository access after their account is deleted, deactivated, or their password is changed. Any user holding an active session at the moment of an administrative revocation event can continue reading, modifying, or deleting repository content until that session naturally times out - bypassing the intended access control action. No public exploit has been identified and this is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 reflects the high-impact triad of confidentiality, integrity, and availability against network-accessible repositories once the prerequisite session exists.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated low-privileged user - who holds the 'update privilege definitions' permission - to silently elevate themselves to full administrative access by editing wildcard privilege definitions already scoped to their own role. No additional authorization check, role reassignment, or administrator approval is required for this escalation. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.9 and the complete confidentiality, integrity, and availability impact - including lateral impact on downstream systems - indicate high real-world risk for any organization using Nexus Repository 3 as a software supply chain hub.
Improper authentication in Dell OpenManage Server Administrator (OMSA) Managed Node before version 11.1.0.2 allows a remote, unauthenticated attacker to bypass authentication controls and gain unauthorized access to the systems management interface across Windows, RHEL 8.10/9.4, and SLES 15 deployments. The CVSS 3.1 base score is 9.8 (network vector, no privileges, no user interaction) with total confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and CISA SSVC lists exploitation as none, but the trivial attack path makes prompt patching important.
Persistent denial of service in Tobit Laboratories AG's TeamDavid (David/Webbox groupware) allows any remote, unauthenticated attacker to shut down the server by requesting the exposed /internalRestart endpoint, which fully halts the service rather than restarting it. All releases through Rollout 524 are affected, and recovery requires manual administrator intervention to bring the server back online. No public exploit identified at time of analysis, though the trigger is trivial (a single HTTP request to a known path).
Hardcoded plaintext credentials embedded in ZTE device firmware expose the web management interface to unauthorized access. The initial login credentials for the device's web interface are stored unencrypted within the firmware image, allowing any party who obtains the firmware to authenticate to any affected device. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the trivial nature of credential extraction from downloadable firmware files significantly elevates practical risk beyond what EPSS alone may reflect.
Integrity bypass in MStore API WordPress plugin (versions before 4.21.0) enables unauthenticated remote attackers to create fraudulent WooCommerce product reviews with arbitrary reviewer names, email addresses, and star ratings, completely circumventing the store's verified-purchase-only review restriction. The plugin's REST API review creation route applies neither authorization nor purchase-ownership validation, rendering the WooCommerce protection setting ineffective when the plugin is active. A publicly available proof-of-concept exists and SSVC confirms the attack is automatable, though the EPSS exploitation probability sits at just 0.14% (3rd percentile), suggesting limited real-world exploitation activity despite ease of execution.
Authentication bypass in the MStore API WordPress plugin before 4.21.0 lets an unauthenticated remote attacker mark any order as fully paid without processing a real payment, because several payment-completion endpoints trust the client-supplied completion signal instead of verifying it against the payment gateway. Any store using this plugin can be defrauded of goods, services, or digital downloads. A public exploit exists (WPScan) and a vendor patch is available, though EPSS remains low at 0.14%.
Account takeover in MStore API WordPress plugin before 4.21.0 is achievable by unauthenticated remote attackers who know a target's registered phone number, by forging a cryptographically invalid login token that the plugin fails to properly verify. This yields full control over the targeted account, including administrator-level WordPress accounts. A publicly available proof-of-concept exists; however, no CISA KEV listing is present and EPSS at 0.14% (3rd percentile) indicates low observed exploitation to date, likely constrained by the phone-number reconnaissance prerequisite.
Payment bypass in the WP Events Manager WordPress plugin before 2.2.5 lets any authenticated user register for a paid event and receive a fully completed booking without paying, because the plugin trusts an attacker-controlled quantity value and derives the charge from it. WPScan reports publicly available exploit code exists, though there is no evidence of active exploitation and the EPSS score is very low (0.13%, 3rd percentile). The flaw is a business-logic/authorization defect rather than a memory-safety issue, so impact is financial fraud against event organizers rather than server compromise.
Improper access control in V-Secure Jingyun Antivirus 2.4.2.39 allows a local low-privileged user to interact with the ZyArk.sys kernel driver in ways that bypass intended access restrictions, yielding high-impact compromise of confidentiality, integrity, and availability on the affected host. A publicly available proof-of-concept exploit (E:P per the CVSS 4.0 vector) lowers the bar for exploitation, though the local-only attack vector limits the exposure to already-authenticated users or post-initial-access scenarios. The vendor was contacted prior to disclosure but did not respond, meaning no official patch exists at time of analysis.
Unauthenticated account takeover in the TrueBooker Appointment Booking and Scheduler System plugin for WordPress (all versions through 1.2.3) allows remote attackers to reset the password of any account, including administrators, because a password-change action fails to verify the requester's authorization. Successful exploitation yields full admin login and therefore complete control of the WordPress site. No public exploit identified at time of analysis; the flaw was reported by Wordfence and an upstream fix is present in the plugin repository.
Local privilege escalation in Jiangmin Antivirus 21 exploits improper access controls in the kernel-mode driver kvcore.sys, specifically within the MessageNotifyCallback function of the Minifilter Port component. A low-privileged local attacker can send crafted messages to this communication port to bypass access enforcement, achieving high impact across confidentiality, integrity, and availability on the affected system. No public exploit identified at time of analysis is incorrect here - a publicly available exploit exists on GitHub, and the vendor did not respond to responsible disclosure, leaving no patch available.
DeepCool DisplayService 1.2.12 on Windows exposes an unauthenticated LocalSystem-level named pipe control channel that any low-privileged local user can connect to and manipulate, enabling full privilege escalation to SYSTEM. The root cause is CWE-284 (Improper Access Control) - the service's IPC channel enforces no caller authentication or ACL verification. A public proof-of-concept is available per VulDB and a researcher's writeup; the vulnerability is not currently listed in CISA KEV, indicating no confirmed mass exploitation, though the low attack complexity and available POC materially elevate near-term risk.
Privilege escalation in Microsoft Purview eDiscovery enables an authenticated low-privileged attacker to gain elevated access over the network, with full confidentiality, integrity, and availability impact once exploited. The vulnerability stems from improper access control (CWE-284), meaning the service fails to enforce authorization boundaries between privilege levels for eDiscovery operations such as case management, legal holds, and content searches. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, though the low attack complexity and network accessibility make this a credible threat in Microsoft 365 enterprise environments.
Privilege elevation in Microsoft Teams lets a remote, unauthenticated attacker gain unauthorized access across a network due to a missing authorization check (CWE-862). The maximum 10.0 CVSS rating stems from a changed scope with high confidentiality and integrity impact, meaning the flaw reaches resources beyond the initially vulnerable component. No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the perfect-score, no-precondition profile makes it a top-tier patch priority.
Privilege elevation in Microsoft Planetary Computer Pro allows a remote, unauthenticated attacker to gain elevated privileges over the network by invoking a critical function that lacks an authentication check (CWE-306). Scored CVSS 10.0 with a scope change, the flaw exposes confidential data and permits unauthorized modification against the affected Azure geospatial platform. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but the maximal score reflects trivial exploitability against exposed instances.
Cryptographic signature spoofing in Microsoft Teams exposes enterprise collaboration environments to unauthenticated identity impersonation over the network. The flaw, tagged as a JWT attack enabling authentication bypass, allows a remote attacker with no prior credentials to forge or tamper with token-based identity claims that Teams fails to properly verify. No active exploitation has been confirmed by CISA KEV, and no public proof-of-concept has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates a low-barrier, remotely exploitable path with high integrity impact.
Privilege elevation in Microsoft Teams allows an authenticated attacker with low-level access to bypass authentication controls and gain higher privileges across a network boundary. The CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H) shows the flaw is remotely reachable, requires only low existing privileges, needs no user interaction, and crosses a security scope to compromise confidentiality and integrity of resources beyond the initially authorized context. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the 9.6 base score reflects the low barrier to abuse once an attacker holds any authenticated Teams foothold.
Unauthenticated remote write to any contact record is possible in OpenSignLabs OpenSign through version 2.37.0 via the updatecontacttour Parse cloud function, which performs no authentication or authorization checks before accepting and applying updates to arbitrary contact records. Any internet-reachable deployment is vulnerable to data corruption or overwrite of contact records for all users system-wide without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability's zero-prerequisites nature and straightforward exploitation model make it a realistic target for automated abuse.
Unauthenticated contact record enumeration in OpenSignLabs OpenSign through 2.37.0 exposes all stored personally identifiable information to remote attackers without credentials. The `getcontact` Parse cloud function executes with `useMasterKey`, which bypasses Parse Server's native access control layers (ACLs and Class-Level Permissions), and contains no compensating authentication or authorization logic. Any network-reachable attacker can call this function, supply arbitrary object IDs, and retrieve full contact records including PII at scale. No public exploit has been identified at time of analysis, and no KEV listing exists.
Unauthenticated remote attackers can invoke the stripeCreateIntent GraphQL mutation in Chaskiq (through commit 46dfdd1) without any session or credential, enabling manipulation of Stripe payment intents for any tenant on the platform. The root cause is CWE-306 (Missing Authentication for Critical Function): the mutation bypasses all authentication and authorization checks, exposing a financial operation to the open internet. No public exploit or CISA KEV active exploitation has been identified at time of analysis, but the trivially low attack complexity (AV:N/AC:L/PR:N/UI:N) means any internet-reachable instance with Stripe configured is structurally exploitable.
Unauthenticated remote access to Stripe Billing Portal sessions in Chaskiq through commit 46dfdd1 allows any attacker to mint valid customer portal sessions for arbitrary tenants by invoking the `stripeCustomerPortal` GraphQL mutation without credentials. The mutation performs zero authentication or tenant-ownership checks before calling the Stripe API, enabling cross-tenant subscription manipulation - including plan changes and cancellations - against any Chaskiq-hosted tenant with Stripe Billing configured. No public exploit code has been identified at time of analysis, though the attack surface requires only network access and knowledge of a target tenant identifier.
Portainer CE through 2.44.0 exposes root-level Docker host access to any authenticated low-privileged user via a URL path normalization flaw in the Docker proxy endpoint. The authorization middleware evaluates a non-canonical request path (e.g., percent-encoded slashes, double slashes, or traversal sequences) differently from the proxy layer that ultimately forwards it to the Docker daemon - allowing crafted requests to bypass all access controls while executing with full Docker API privileges. No active exploitation has been confirmed (no CISA KEV listing) and no public exploit code has been identified at time of analysis; EPSS data was not provided in the source intelligence.
Authorization bypass in Commvault CommServe allows remote attackers to invoke a limited set of command-execution operations without passing the intended authorization checks, per Commvault security advisory CV_2026_07_9. The flaw carries a CVSS 4.0 base score of 9.2 with high impact to confidentiality, integrity, and availability, and affects Commvault Cloud deployments across the CommServe, Web Server, Command Center, MediaAgents, Clients, and HyperScale X components. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authorization bypass in Commvault CommServe permits attackers to circumvent the command-execution allowlist, gaining unsanctioned command execution across the backup-management control plane. Because CommServe orchestrates the entire Commvault environment, a successful bypass can cascade to Webservers, Command Center, Media Agents, Clients and HyperScale X, threatening confidentiality, integrity and availability of protected data. Rated CVSS 4.0 9.2 (critical) by Commvault; no public exploit identified at time of analysis and it is not listed in CISA KEV.
IIOP NameService in Red Hat JBoss Enterprise Application Platform (EAP) accepts bind operations without authentication, allowing unauthenticated network attackers to register malicious CORBA object references under arbitrary JNDI names. When legitimate clients subsequently perform JNDI lookups, they resolve the attacker's malicious Object Request Broker (ORB), enabling man-in-the-middle interception of CORBA/RMI-IIOP invocations or denial-of-service on dependent application flows. EPSS data was not provided; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.
Undertow's AJP listener unconditionally trusts the ssl_cert and is_ssl AJP request attributes without requiring a shared-secret, allowing an unauthenticated remote attacker with direct TCP access to port 8009 to impersonate any X.509 client certificate identity and bypass CLIENT-CERT mutual TLS authentication entirely. Deployments where Undertow acts as a back-end behind a reverse proxy - with CLIENT-CERT authentication enforced at the proxy layer but the AJP port exposed on an internal network - are directly at risk of identity spoofing and authorization bypass. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog; however, the bypass primitive is architecturally simple for any attacker who has obtained internal network access to the AJP port.
Privilege escalation in the `openvt -u` utility allows a local low-privileged attacker to obtain passwordless root login on Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. The flaw lies in `authenticate_user()`, which resolves VT ownership via `stat("/proc/<pid>/fd/0")` - a call that follows the symlink to the underlying TTY device node rather than inspecting the owning process, causing the check to read the device node's UID rather than the process owner's UID. When a privileged user logs out and TTY device node ownership reverts to root or the getty owner while an attacker's process still holds fd 0 on that TTY, the check incorrectly authorizes a passwordless `login -f root` execution. No public exploit is identified at time of analysis and there is no CISA KEV listing, but the root-level impact makes this a high priority for environments using the affected `kbrequest`/init deployment pattern.
Privilege escalation in MRTG (Multi Router Traffic Grapher) allows a local low-privileged attacker to gain elevated file ownership on the host system. When the MRTG daemon is launched as root and then drops privileges, a CWE-59 symlink-following flaw in PID file handling lets an attacker pre-place or manipulate a symlink at the expected PID file path, causing the root process to change ownership of an arbitrary existing file to the daemon user. Affected platforms include Red Hat Enterprise Linux 6 through 10; no public exploit code or CISA KEV listing has been identified at time of analysis.
Insecure Direct Object Reference in Chiline Cloud (Inventec Appliances) versions up to and including 4.5.9 exposes sensitive user data to unauthenticated remote attackers. By manipulating a specific request parameter - likely a user identifier or resource key - an attacker can bypass authorization checks and read account data belonging to arbitrary other users. Reported by TWCERT and catalogued under EUVD-2026-55925, no public exploit code or active exploitation has been confirmed at time of analysis, though the trivial exploitation conditions (network-accessible, no authentication, no user interaction) make this a high-priority disclosure risk.
Missing authorization checks in SAP ABAP Developer Tools (the Eclipse-based IDE for ABAP development) allow any low-privileged SAP user to execute unauthorized database operations against SAP NetWeaver AS ABAP backends. The flaw spans a wide range of SAP_BASIS releases (750 through 920) and yields full confidentiality, integrity, and availability compromise of the ABAP application layer - including the ability to read sensitive business data, modify application records, and disrupt legitimate user access. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and broad version coverage elevate real-world risk considerably for enterprises running ADT-connected NetWeaver systems.
Unauthenticated remote access to SAP Manufacturing Integration and Intelligence (MII) scheduling functions is possible due to a missing authorization check on scheduling-related API endpoints. Any network-reachable attacker without credentials can retrieve, create, modify, or delete scheduling data managed by the application, impacting confidentiality, integrity, and availability at a low severity level each. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the trivial exploitation conditions - no authentication, no user interaction, low complexity - lower the barrier to opportunistic abuse significantly.
Missing authorization on the Cost Servlet in SAP Manufacturing Integration and Intelligence (SAP MII) exposes backend operations to unauthenticated remote attackers via crafted HTTP requests with specific parameter values. Successful exploitation grants read, create, modify, and delete access to application-managed business data, producing a limited but tripartite impact across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at this time, though the zero-privilege network vector lowers the bar for opportunistic probing.
SSO-based account takeover in usememos Memos v0.27.1 lets a remote, unauthenticated attacker impersonate any user by exploiting the ssoCredentials path of the SignIn handler (server/router/api/v1/auth_service.go), which matches a federated identity solely on an attacker-controllable identifier (e.g. email or username) instead of the identity provider's stable subject claim. Any deployment that has an OIDC/OAuth SSO provider enabled is affected, and a successful attack yields full control of the targeted account, including potentially administrative accounts. The flaw carries CVSS 9.8 and CWE-287; there is no public exploit identified as weaponized at time of analysis, though a referenced GitHub gist appears to be a researcher write-up, and EPSS is low at 0.22%.
Broken access control in ERPNext's accounts module permits authenticated low-privilege users to invoke privileged write operations across five functions - merge_account, pause_job_for_doc, trigger_job_for_doc, change_release_date, and update_cost_center - without any server-side permission enforcement. All v15 releases prior to 15.112.0 and all v16 releases prior to 16.22.0 are affected. An attacker with any valid ERPNext session can directly call these whitelisted API endpoints to corrupt financial accounts, payment reconciliation jobs, purchase invoices, and cost centers beyond their assigned role, with no public exploit identified at time of analysis.
Broken access control in ERPNext's Accounts Receivable and Payable report engine allows any authenticated user to read cross-company financial data they are not authorized to view. The `ReceivablePayableReport.prepare_conditions()` method fails to enforce Customer and Supplier user permissions against the Payment Ledger Entry dynamic-link party field, meaning permission boundaries set via Frappe's user permission system are silently bypassed for this report path. Fixed in versions 15.112.0 and 16.23.0; no public exploit identified at time of analysis.
Privilege escalation in Red Hat OpenShift AI's Data Science Pipelines component allows authenticated tenants to bypass authorization controls in the setDefaultServiceAccount function by submitting a crafted CreateRun request that references a more privileged ServiceAccount than they are entitled to use. Successful exploitation enables the tenant's pipeline containers to run with elevated Kubernetes RBAC permissions, resulting in cross-namespace secret disclosure and the ability to execute commands inside other tenants' pods. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Credential derivation in Red Hat OpenShift AI's Data Science Pipelines Operator allows unauthenticated remote attackers to predict MariaDB root/user passwords and MinIO access/secret keys by exploiting a cryptographically weak PRNG (CWE-338). Any attacker who can reach the MinIO Route or MariaDB Service over the network can compute valid credentials without prior authentication, then access all pipeline artifacts and metadata stored in the system. No active exploitation is confirmed and no public exploit code has been identified at time of analysis, but the CVSS 7.5 High rating with AV:N and PR:N reflects a no-authentication-barrier condition against exposed services.
Privilege escalation in Red Hat OpenShift AI (RHOAI) training operator overlay allows any namespace editor to manage TrainJob resources beyond their intended authorization scope. The RHOAI overlay incorrectly injects trainjobs CRUD permissions into the native Kubernetes edit ClusterRole, violating the principle of least privilege. When chained with a companion flaw (TRN-01) that permits arbitrary pod configuration within TrainJobs, a remote attacker holding namespace editor credentials could escalate to arbitrary code execution - no public exploit is identified at time of analysis, and KEV listing has not been confirmed.
Authorization bypass in Feast's materialization API endpoints within Red Hat OpenShift AI (RHOAI) permits full re-materialization of all feature views by sending a crafted request that omits the feature_views field, circumventing permission checks. The consequence is a multi-tenant Denial of Service through data corruption and significant resource exhaustion, impacting all tenants sharing the deployment. No public exploit code has been identified at time of analysis, but the bypass mechanism is straightforward - a structural omission in the request body - making independent rediscovery likely for any attacker with API access.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
Authentication bypass in TrustyAI Service (TAS) within Red Hat OpenShift AI (RHOAI) exposes the backend API to any pod on the cluster network without requiring valid credentials. The CVSS vector (AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that an attacker with a pod on the cluster-such as through a compromised workload or a malicious tenant pod in a multi-tenant deployment-can read, modify, delete, or poison AI model monitoring data and configurations with no additional barriers. No public exploit code or CISA KEV listing has been identified at time of analysis, but the root cause (CWE-306: Missing Authentication for Critical Function) means exploitation is trivially simple once cluster network adjacency is established.
Authentication bypass in the Models-as-a-Service (MaaS) API component of Red Hat OpenShift AI (RHOAI) lets any pod already running in the cluster impersonate arbitrary users by forging the X-MaaS-Username and X-MaaS-Group HTTP headers, which the service trusts without independent verification. Because the MaaS API performs no first-party authentication and defers entirely to a Kuadrant AuthPolicy gateway that can be circumvented, a low-privileged workload can mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and exfiltrate model-access configuration - a full cross-tenant privilege escalation. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the 9.9 CVSS reflects near-total impact.
The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.
Cross-channel message deletion in Spacebar Server (all commits before 8d126f4) permits authenticated users holding MANAGE_MESSAGES permission in any channel to delete messages residing in channels they do not control. Both the single-delete and bulk-delete API handlers failed to scope their database queries to the channel_id present in the request path, allowing attacker-supplied message IDs from foreign channels to be processed and destroyed. A publicly available exploit exists, with the root cause and fix confirmed by the upstream security advisory GHSA-62g6-28hv-h6hc; no CISA KEV listing has been issued at time of analysis.
Incomplete authorization in Dokploy's WebSocket handlers prior to v0.29.13 allows any authenticated organization member to obtain root terminal access to servers and read logs or statistics for services they were explicitly denied access to. The four affected handlers (terminal.ts, docker-container-terminal.ts, docker-container-logs.ts, docker-stats.ts) verify organization membership but never call checkServiceAccess, getAccessibleServerIds, or accessedServices, nullifying all fine-grained role-based access controls. No public exploit or CISA KEV listing exists; however, the attack requires only a valid low-privilege organization account, making this a meaningful privilege escalation risk in any multi-tenant Dokploy deployment.
Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.
GitHub App provider injection in Dokploy PaaS (prior to v0.29.13) allows unauthenticated remote attackers to insert attacker-controlled GitHub App credentials - including client_secret, webhook_secret, and PEM private key material - into any target organization's configuration by forging the state parameter in the GitHub OAuth callback route. The route /api/providers/github/setup performed no session authentication (CWE-306), blindly trusting organizationId and userId values supplied by the caller in the state query parameter. No public exploit identified at time of analysis; a vendor-released patch is confirmed available as v0.29.13.
Interactive host-shell access in Dokploy prior to 0.29.13 is obtainable by any authenticated platform user due to a missing authorization check in the WebSocket terminal handler. The handler at apps/dokploy/server/wss/terminal.ts validates the session token but never checks whether the user holds an organization role or server-access grant before spawning a terminal for serverId=local, yielding full interactive shell access on the Dokploy host. No confirmed active exploitation or public exploit code has been identified at time of analysis, but the public security advisory and fix diff make reconstruction trivial for any authenticated user.
Privilege escalation via missing authorization in Dokploy, a self-hostable Platform-as-a-Service, lets any authenticated organization member open a root shell inside arbitrary containers on a self-hosted instance. The /docker-container-terminal WebSocket handler authenticated the caller but never checked the attacker-supplied containerId against the caller's role, organization, or service scope before invoking docker exec. Fixed in 0.29.13; no public exploit identified at time of analysis, though the upstream fix commit is public.
Unauthenticated file exfiltration in Flowise 2.2.4-3.1.4 is possible because the POST /api/v1/openai-assistants-file/download endpoint was incorrectly added to the application's global authentication whitelist, causing all session and API key verification to be skipped unconditionally. Any remote, unauthenticated attacker who can supply valid chatflowId, chatId, and fileName identifiers can retrieve private files from any chatflow on the instance, including those belonging to other workspaces or organizations in a multi-tenant deployment. A public proof-of-concept exploit is available via GitHub, and no KEV listing has been confirmed at time of analysis.
Full application database read in Metabase is achievable by any authenticated low-privileged user due to a missing authorization check (CWE-862). Any user with a valid account - regardless of their assigned role or permissions - can issue requests that return the entire contents of the Metabase backend database, potentially exposing database connection credentials, API keys, user account data, and sensitive query results. No public exploit has been identified at time of analysis, but the low exploitation complexity and broad attacker pool (any registered user) make this a high-priority remediation item.
Cross-tenant authorization bypass in Dokploy 0.29.8 and earlier lets an authenticated organization member with backup permissions reach another organization's S3 backup destinations by supplying a client-controlled destinationId that is never checked against their active organization. Because the referenced destination's S3 accessKey and secretAccessKey are materialized on the attacker's service host, the attacker can read a victim tenant's backup objects and redirect or poison backups across tenant boundaries. No public exploit identified at time of analysis, but the flaw is trivially reachable and breaks the core multi-tenant isolation of the platform (CVSS 9.6, scope-changed).
Cryptographic signature validation failure in Pega Platform (Pega Infinity) versions 8.5.0 through 25.1.2 enables low-privileged network attackers to forge or manipulate JWT tokens, bypassing authentication and authorization controls. The vulnerability maps to CWE-347 and is tagged as a JWT attack vector capable of authentication bypass, with high confidentiality and integrity impact confirmed in the vendor's own CVSS 4.0 assessment. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and network accessibility make this a meaningful risk for any organization running affected Pega Infinity deployments.
Cross-organization server deletion and SSH key disclosure in Dokploy affects all instances running versions 0.28.7 through 0.29.12. The server.remove tRPC mutation accepts a caller-supplied serverId without verifying organizational ownership, allowing an authenticated owner or administrator in one organization to delete server registrations and all associated deployment records belonging to a completely separate organization - and to receive that organization's plaintext SSH private key as a side effect. No public exploit code has been identified at time of analysis, but the fix is available in version 0.29.13 and the GitHub advisory (GHSA-3rpx-c3j9-q99x) and patch PR are public.
Cross-tenant IDOR in Prospero Flow CRM before 5.4.8 allows any authenticated user to blindly overwrite contact records belonging to other companies and exfiltrate their personal data as vCard files, simply by supplying an arbitrary numeric contact ID. The contact save and vCard export endpoints performed no company-scoping on their database queries, so a user authenticated to Company A could tamper with or harvest contacts owned by Company B without any special knowledge beyond a valid integer identifier. No public exploit or CISA KEV listing has been identified at time of analysis, but the vulnerability is trivially exploitable in any multi-tenant deployment and the full fix has been released as v5.4.8 (and later v5.5.3).
Hard-coded credentials embedded in the Zyxel WAH7601 mobile Wi-Fi hotspot firmware expose sensitive constants within the device executable, enabling adjacent-network attackers without any prior privileges to bypass authentication and achieve high-impact confidentiality and integrity compromise. All WAH7601 firmware versions through 20.07.2026 are confirmed affected per TR-CERT advisory TR-26-0799 and NVD. No public exploit code or active exploitation has been identified at time of analysis, but the low attack complexity characteristic of CWE-798 makes this a credible near-term risk in environments where adjacent access is not tightly controlled.
Privilege escalation in Roskus Prospero Flow CRM before version 5.2.1 permits any authenticated user - regardless of assigned role - to grant any application role the complete set of system permissions by sending a crafted POST request to the permission save endpoint. The vulnerable `PermissionSaveController` accepted a user-supplied `roles` array and invoked Spatie Permission's `syncPermissions()` with no prior authorization check, making low-trust authenticated accounts a direct path to full administrative control. No public exploit or CISA KEV listing has been identified at time of analysis, but the publicly accessible commit diff documents the exact endpoint and flaw mechanism, substantially lowering the exploitation barrier for any attacker holding CRM credentials.
Missing authorization in OpenSignLabs opensignserver through 2.37.0 lets unauthenticated remote attackers irreversibly decline any in-flight signing document and forge the decline attribution to an arbitrary user. The vulnerable declinedoc Parse cloud function writes the IsDeclined flag, DeclineReason text, and a caller-supplied DeclineBy pointer to the document record without verifying the caller's identity, enabling both workflow termination and evidentiary record falsification. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.
Authentication bypass in opensignserver through 2.37.0 exposes all stored files to unauthenticated remote attackers by allowing them to mint MASTER_KEY-signed file access tokens via the getsignedurl Parse cloud function. The bypass requires no credentials and no prior knowledge of valid document records - supplying any arbitrary string as the docId parameter causes the function to skip its isAuthenticated check entirely and issue a fully trusted signed token. No public exploit code or CISA KEV listing exists at time of analysis, but the bypass condition is trivially reproducible from the CVE description alone, making this a realistic and immediate threat to any internet-exposed instance storing sensitive signed documents.
Cross-tenant authorization bypass in Attendize through commit 9289acb permits an authenticated organizer to inject persistent, mandatory survey questions into a different organizer's events by supplying an arbitrary event_id to the POST /event/{event_id}/question/create endpoint. The postCreateEventQuestion method resolves the target event without applying tenant-isolation scoping, so the write succeeds across tenant boundaries; the injected question is then irremovable by the victim because the victim's account-scoped delete path cannot resolve a record owned by another tenant. No public exploit has been identified at time of analysis, and the vulnerability has not been listed in the CISA KEV catalog.
Broken object-level authorization in OpenSignLabs OpenSignServer through 2.37.0 exposes complete contract records - including sender and signer PII and pre-signed document download URLs - to unauthenticated remote attackers via the getDocument Parse cloud function. The function internally calls useMasterKey, bypassing Parse's ACL enforcement, and returns full records whenever the document's IsEnableOTP flag is false, which is the default configuration across all deployments. No public exploit has been identified at time of analysis, but the network-accessible, zero-authentication attack path against default configurations makes this a high-priority data protection issue, particularly for organizations subject to GDPR or similar data regulation.
Unauthenticated remote access to all stored contract documents is possible in OpenSignLabs opensignserver through version 2.37.0 due to a missing authentication check in the fileupload Parse cloud function. Any unauthenticated attacker who can reach the endpoint can supply an arbitrary URL and receive a MASTER_KEY-signed file access token, completely defeating the only access control layer protecting stored documents. No public exploit has been identified at time of analysis, but the zero-privilege, low-complexity attack vector makes this highly accessible to unsophisticated threat actors.
Use-after-free in the Linux kernel's TIPC (Transparent Inter-Process Communication) subsystem lets a local actor trigger a write to freed slab memory via the accept() error path of tipc_sk_create(). When socket insertion into the per-netns rhashtable fails, sock->sk is left dangling instead of NULLed, so tipc_release() bypasses its own NULL guard and calls lock_sock() on the freed sk. It affects kernels using the AF_TIPC protocol across many stable branches (fixes backported to 5.4.x through 6.18.x and mainline 7.x); there is no public exploit identified at time of analysis and it is not in CISA KEV, with a low EPSS of 0.18%.
Recursive locking deadlock in the Linux kernel audit subsystem causes a complete, unrecoverable kernel hang when a file matching an executable audit rule is renamed. Affected kernels from 4.3 through stable branches prior to 6.6.148, 6.12.101, 6.18.42, 7.1.6, and 7.2-rc1 are vulnerable. Any local user able to rename a file that matches an active exe= audit rule can trigger the deadlock, forcing a hard reboot; no public exploit exists and EPSS is 0.18%, consistent with the specific preconditions required.
Missing authentication in dulldusk/phpFM through version 1.8.0 exposes the complete file manager to unauthenticated remote attackers because the default configuration ships with an empty auth_pass value. The flawed check in index.php (line 637, 'if ($auth_pass == '' || $loggedon==$auth_pass)') short-circuits to true whenever the password is unset, granting anyone full read, write, delete, and upload access to the server filesystem. CVSS 9.8 (CWE-306); no public exploit identified at time of analysis, though the vulnerable logic is directly visible in the referenced public source and is trivially reproducible.
Unauthenticated access to complete historical sensor data is possible in FUXA through version 1.3.3 because the DAQ_QUERY Socket.IO event handler in server/runtime/index.js omits the isSocketAdminAuthorized() check that guards every other sensitive Socket.IO event. Remote attackers can exfiltrate all sensor history without credentials even on deployments where secureEnabled=true is configured, silently undermining an operator's assumption that authentication is fully enforced. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS AV:N/AC:L/PR:N vector confirms this is trivially exploitable by any network-reachable party.
Remote unauthenticated account takeover in fastschema through v0.15.1 is enabled by a TOCTOU race condition in the OTP-based account recovery flow. The verifyOTPSession function in pkg/auth/local.go reads and increments the attempt counter in separate non-atomic operations, allowing concurrent HTTP requests to race past the attempt limit before any counter update is committed. With no effective limit enforced on a 6-digit OTP (1,000,000 possible values), an attacker can brute-force valid codes; no public exploit is identified at time of analysis and this CVE is not in CISA KEV.
Remote code execution in NASA fprime-gds through version 3.4.3 lets an unauthenticated remote attacker fully compromise the ground data system and inject arbitrary commands to any connected spacecraft. The Flask ground station exposes every endpoint without authentication (CWE-306), while a path traversal in the upload/download handler permits reading and writing arbitrary files, and a hardcoded Flask secret key (CWE-321) enables session forgery; chained, they yield code execution on the ground station host. No public exploit is identified at time of analysis, but the CVSS 9.8 rating and unauthenticated network vector make this a high-priority, real-world risk for anyone running F Prime ground software.
Improper authorization in Daptin through v0.12.34 lets unauthenticated remote guests perform full CRUD (read, create, update, delete) on all usergroup records, effectively bypassing access control on the platform's group and permission objects. The flaw arises because permission checks treat a null/zero UserId as a valid ownership match, so a guest whose session UserId is null is granted owner-level rights over ownerless usergroup rows. No public exploit identified at time of analysis, but the CVSS of 9.1 (network, no auth, no interaction) reflects that manipulating usergroups can be leveraged to escalate privileges and corrupt the platform's authorization model.
Cross-tenant authorization bypass in fosrl Pangolin through v1.20.0 lets an authenticated user reuse an access token minted for one resource to authenticate against any other resource in any organization. Because the authWithAccessToken.ts handler validates the token without binding it to the requested resourceId, a token scoped to resource X in organization A is accepted for resource Y in organization B, collapsing multi-tenant isolation. Rated CVSS 9.6 (CWE-639); no public exploit identified at time of analysis, though the vulnerable code path is disclosed in the referenced source file.
Unauthenticated access to Apache Ranger Download APIs on versions 2.8.0 and earlier exposes sensitive authorization policy data to any remote attacker with network connectivity. The missing authentication check (CWE-306) means no credentials or privileges are required to invoke these endpoints and retrieve their output. No public exploit code has been identified at time of analysis, but the low complexity and zero-authentication nature of the CVSS vector (AV:N/AC:L/PR:N/UI:N) makes this trivially exploitable by any attacker who can reach the Ranger Admin interface.
Improper access control in the Weaver component of Samsung Mobile devices allows a local attacker without elevated privileges to render the device inoperable, achieving high integrity and availability impact. All Samsung Mobile devices running Weaver prior to the SMR Aug-2026 Release 1 security update are affected. No public exploit code or active exploitation has been confirmed at time of analysis, but the low attack complexity and absence of privilege requirements lower the bar for abuse by a local threat actor.
Privilege escalation via REST API authentication bypass in the CheckView WordPress plugin before 2.3.2 allows an unauthenticated attacker to perform any REST action available to a logged-in administrator - including creating a new administrator account - by tricking an admin into opening a crafted link. The plugin's authentication filter is applied globally to all REST routes rather than only to CheckView's own endpoints, and it unconditionally discards authentication errors for any request whose URI merely contains a CheckView-specific string, bypassing WordPress's nonce enforcement entirely. A publicly available exploit from WPScan demonstrates this path; no confirmed active exploitation (CISA KEV) has been recorded at time of analysis.
Authentication bypass in the AutoNetTV Relay WordPress plugin (all versions before 3.0.14) allows unauthenticated remote attackers to obtain a WordPress administrator session cookie by triggering the plugin's scheduled content-synchronization task under a specific server configuration. The plugin issues an admin authentication cookie during the sync task without performing any capability or authorization check, and on servers where the scheduled task completes before the HTTP response is committed, the cookie is returned to the triggering request. A public proof-of-concept exploit exists, reported by WPScan; no KEV listing has been identified at time of analysis.
Account takeover via broken password-reset rate limiting in the Login & Register Forms WordPress plugin (versions before 4.0.2) allows unauthenticated remote attackers to brute-force verification codes and seize any account, including administrator accounts. Both the verification code and the per-source attempt counter are keyed on client-controlled data, meaning an attacker can reset the rate limit at will by manipulating that value - rendering the lockout mechanism entirely ineffective. Exploitation requires the 'verification-code reset mode' to be enabled; a publicly available proof-of-concept from WPScan demonstrates the technique, though EPSS sits at only 0.15% (4th percentile), indicating limited observed exploitation activity to date.
Account takeover in the Login & Register Forms WordPress plugin (before 4.0.2) is enabled by a fundamentally broken password reset verification design: the plugin keys the 'verification completed' state to a client-controlled value rather than binding it server-side to the account under reset or to the authenticated session of the party completing verification. An unauthenticated attacker who can observe or manipulate this state during or after a legitimate reset flow can claim ownership of that completed verification and set a new password for any targeted account, including administrator accounts. A publicly available exploit has been published by WPScan, and no public exploit identified at time of analysis translates to KEV, though POC availability materially lowers the exploitation threshold.
Password reset abuse in the Single Sign On For TNG WordPress plugin (versions before 2.2.0) allows unauthenticated attackers to reset the password of any account, including administrators, resulting in full site takeover. The flaw stems from improper validation of the password reset request, and publicly available exploit code exists, though EPSS scores the exploitation probability at a low 0.15% (4th percentile). It is not listed in CISA KEV, so exploitation is currently proof-of-concept rather than confirmed active in-the-wild use.
Unauthenticated content injection in Arvow AI SEO Writer WordPress plugin (before 1.5.4) allows remote attackers to create arbitrary posts and pages and extract author account and taxonomy information by exploiting a PHP type juggling flaw in a REST endpoint. The bypass is effective exclusively when the plugin has not been configured post-installation, making freshly deployed or abandoned instances the primary target. A public proof-of-concept is available via WPScan; despite this, EPSS sits at 0.15% (5th percentile) and no CISA KEV listing exists, indicating no public exploit has driven mass exploitation at time of analysis.
Account takeover in the BricksForge WordPress plugin (versions before 3.1.8.8) is enabled by a missing server-side identity check during password change form submissions, allowing unauthenticated remote attackers to set arbitrary passwords for any WordPress user, including site administrators. The vulnerable state is effectively the default configuration for any site that has deployed BricksForge's password update form action, since current-password verification is disabled by default in that action. A publicly available exploit exists; active exploitation has not been confirmed by CISA KEV, but the direct path to admin-level account takeover makes this a critical remediation priority for affected deployments.
Missing authorization controls in the File Manager WordPress plugin before version 6.9.1 allow any authenticated user - including low-privilege subscribers - to read and delete arbitrary files under the WordPress installation directory. The weakness exposes sensitive configuration secrets such as database credentials stored in wp-config.php, and enables deliberate denial of service through file deletion. A publicly available exploit exists per WPScan reporting, though EPSS remains very low (0.14%, 4th percentile), suggesting targeted rather than broadly automated exploitation at time of analysis.
Full network takeover via authentication bypass in the InfiniteWP Client WordPress plugin before 1.13.6 affects WordPress Multisite installations, where the plugin fails to validate the site-connection state and the authenticity of requests to its remote-management endpoint. Unauthenticated remote attackers can bind their own management key, hijack an administrator session, and gain control of every site in the network, culminating in remote code execution. No public exploit identified at time of analysis; EPSS is low at 0.19% (9th percentile) despite the maximal 9.8 CVSS, and a vendor patch is available.
Privilege escalation in the Solace Extra WordPress plugin (versions before 1.6.1) allows any authenticated user with Subscriber-level access to modify site-wide presentation settings and permanently delete imported site-builder content by exploiting missing capability checks across multiple AJAX endpoints. The plugin incorrectly exposes nonce values on admin-accessible pages that low-privileged users can reach, collapsing the intended authorization boundary between Subscriber and Administrator roles. A publicly available proof-of-concept exists via WPScan; no public exploit identified at time of analysis has been confirmed by CISA KEV, and the EPSS score of 0.13% (3rd percentile) reflects low observed exploitation probability to date.
The Home Assistant iOS Companion app silently executes tag-triggered automations when any co-installed untrusted app forwards a crafted tag event via iOS universal links, bypassing physical scan validation entirely. Affected versions are all iOS Companion app releases prior to 2026.5.0; the underlying Home Assistant core CPE (cpe:2.3:a:home-assistant:core:*:*:*:*:*:*:*:*) is also cited. Because automations can control physical devices such as smart locks and alarms, the I:H CVSS metric reflects real-world consequences beyond software state. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Silent automation execution in the Home Assistant Android Companion App prior to 2026.8.1 allows any co-installed app on the device to trigger arbitrary HA automations by forwarding a crafted tag URL to an exported Activity without user confirmation. The flaw exists because TagReaderActivity accepted both physical NFC intents and OS-routed deep links identically, with no caller validation or approval prompt before dispatching the tag scan to the Home Assistant server. No public exploit has been identified at time of analysis, but the attack is unattended and can control physical actuators such as locks or alarms.
The `$import-pnp` operation in Pathling Server allows low-privileged callers to supply an arbitrary `exportUrl`, causing the server to forward its configured PNP credentials to an attacker-controlled FHIR endpoint and stage the returned files as trusted local sources - effectively bypassing the `allowableSources` allowlist that guards the standard `$import` operation. All Pathling Server deployments prior to version 2.0.0 with PNP credentials configured are affected, with high confidentiality and integrity impact (credential theft and unauthorized data import). No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack requires only low-privilege API access and is low-complexity.
Pathling Server before version 2.0.0 permits authenticated callers holding only coarse operation-level authorities (e.g., `pathling:search`) to act on arbitrary FHIR resource families - including resource types they are not explicitly authorized to read or write - because typed search, update, and batch handlers enforce the operation-level authority check but skip the documented per-resource authority check (e.g., `pathling:read:Patient`). The flaw breaks the two-factor authorization model the product documents, exposing potentially all FHIR resource families to any valid operation-authority holder. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis; the vulnerability is fixed in Pathling Server 2.0.0.
Missing authentication in the LightRAG API server (HKUDS/LightRAG) through version 1.5.4 exposes every management endpoint to unauthenticated network attackers, because the server binds to 0.0.0.0 by default while authentication is off unless explicitly configured. Any attacker with network reach can read indexed document content, upload or delete documents, rewrite the knowledge graph, cancel ingestion pipelines, clear caches, and consume LLM/API credits. No public exploit identified at time of analysis, but exploitation is trivial via a single unauthenticated HTTP request, and the fix in 1.5.5rc1 is largely a hardening/warning change rather than an enforced secure default, so operator action is still required.
Insecure direct object reference in TestLink 1.9.20 and earlier allows any authenticated user - including low-privilege guest accounts - to retrieve arbitrary file attachments from projects they have no membership in, by supplying sequential integer IDs to the attachmentdownload.php endpoint. The handler performs no project membership or role authorization check, enabling bulk enumeration of all attachments across the entire installation. No public exploit has been confirmed at time of analysis, though a researcher writeup exists; the attack is trivially automatable due to the sequential integer ID scheme.
Incorrect authorization in the Nexus Repository 3 CE/Pro repository-creation UI allows an authenticated user with a format-scoped delegated repository-admin privilege to create repositories in unauthorized formats - bypassing the intended scope boundary. Affected are all releases from 3.0.0 through 3.94.x; version 3.95.0 resolves the flaw. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, but the integrity impact is high given that unauthorized repository types could be introduced into a managed artifact store, potentially tainting software supply chain pipelines.
Insufficient session expiration in Sonatype Nexus Repository 3 allows a previously-authenticated user to retain full repository access after their account is deleted, deactivated, or their password is changed. Any user holding an active session at the moment of an administrative revocation event can continue reading, modifying, or deleting repository content until that session naturally times out - bypassing the intended access control action. No public exploit has been identified and this is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 reflects the high-impact triad of confidentiality, integrity, and availability against network-accessible repositories once the prerequisite session exists.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated low-privileged user - who holds the 'update privilege definitions' permission - to silently elevate themselves to full administrative access by editing wildcard privilege definitions already scoped to their own role. No additional authorization check, role reassignment, or administrator approval is required for this escalation. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.9 and the complete confidentiality, integrity, and availability impact - including lateral impact on downstream systems - indicate high real-world risk for any organization using Nexus Repository 3 as a software supply chain hub.
Improper authentication in Dell OpenManage Server Administrator (OMSA) Managed Node before version 11.1.0.2 allows a remote, unauthenticated attacker to bypass authentication controls and gain unauthorized access to the systems management interface across Windows, RHEL 8.10/9.4, and SLES 15 deployments. The CVSS 3.1 base score is 9.8 (network vector, no privileges, no user interaction) with total confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and CISA SSVC lists exploitation as none, but the trivial attack path makes prompt patching important.
Persistent denial of service in Tobit Laboratories AG's TeamDavid (David/Webbox groupware) allows any remote, unauthenticated attacker to shut down the server by requesting the exposed /internalRestart endpoint, which fully halts the service rather than restarting it. All releases through Rollout 524 are affected, and recovery requires manual administrator intervention to bring the server back online. No public exploit identified at time of analysis, though the trigger is trivial (a single HTTP request to a known path).
Hardcoded plaintext credentials embedded in ZTE device firmware expose the web management interface to unauthorized access. The initial login credentials for the device's web interface are stored unencrypted within the firmware image, allowing any party who obtains the firmware to authenticate to any affected device. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the trivial nature of credential extraction from downloadable firmware files significantly elevates practical risk beyond what EPSS alone may reflect.
Integrity bypass in MStore API WordPress plugin (versions before 4.21.0) enables unauthenticated remote attackers to create fraudulent WooCommerce product reviews with arbitrary reviewer names, email addresses, and star ratings, completely circumventing the store's verified-purchase-only review restriction. The plugin's REST API review creation route applies neither authorization nor purchase-ownership validation, rendering the WooCommerce protection setting ineffective when the plugin is active. A publicly available proof-of-concept exists and SSVC confirms the attack is automatable, though the EPSS exploitation probability sits at just 0.14% (3rd percentile), suggesting limited real-world exploitation activity despite ease of execution.
Authentication bypass in the MStore API WordPress plugin before 4.21.0 lets an unauthenticated remote attacker mark any order as fully paid without processing a real payment, because several payment-completion endpoints trust the client-supplied completion signal instead of verifying it against the payment gateway. Any store using this plugin can be defrauded of goods, services, or digital downloads. A public exploit exists (WPScan) and a vendor patch is available, though EPSS remains low at 0.14%.
Account takeover in MStore API WordPress plugin before 4.21.0 is achievable by unauthenticated remote attackers who know a target's registered phone number, by forging a cryptographically invalid login token that the plugin fails to properly verify. This yields full control over the targeted account, including administrator-level WordPress accounts. A publicly available proof-of-concept exists; however, no CISA KEV listing is present and EPSS at 0.14% (3rd percentile) indicates low observed exploitation to date, likely constrained by the phone-number reconnaissance prerequisite.
Payment bypass in the WP Events Manager WordPress plugin before 2.2.5 lets any authenticated user register for a paid event and receive a fully completed booking without paying, because the plugin trusts an attacker-controlled quantity value and derives the charge from it. WPScan reports publicly available exploit code exists, though there is no evidence of active exploitation and the EPSS score is very low (0.13%, 3rd percentile). The flaw is a business-logic/authorization defect rather than a memory-safety issue, so impact is financial fraud against event organizers rather than server compromise.
Improper access control in V-Secure Jingyun Antivirus 2.4.2.39 allows a local low-privileged user to interact with the ZyArk.sys kernel driver in ways that bypass intended access restrictions, yielding high-impact compromise of confidentiality, integrity, and availability on the affected host. A publicly available proof-of-concept exploit (E:P per the CVSS 4.0 vector) lowers the bar for exploitation, though the local-only attack vector limits the exposure to already-authenticated users or post-initial-access scenarios. The vendor was contacted prior to disclosure but did not respond, meaning no official patch exists at time of analysis.
Unauthenticated account takeover in the TrueBooker Appointment Booking and Scheduler System plugin for WordPress (all versions through 1.2.3) allows remote attackers to reset the password of any account, including administrators, because a password-change action fails to verify the requester's authorization. Successful exploitation yields full admin login and therefore complete control of the WordPress site. No public exploit identified at time of analysis; the flaw was reported by Wordfence and an upstream fix is present in the plugin repository.
Local privilege escalation in Jiangmin Antivirus 21 exploits improper access controls in the kernel-mode driver kvcore.sys, specifically within the MessageNotifyCallback function of the Minifilter Port component. A low-privileged local attacker can send crafted messages to this communication port to bypass access enforcement, achieving high impact across confidentiality, integrity, and availability on the affected system. No public exploit identified at time of analysis is incorrect here - a publicly available exploit exists on GitHub, and the vendor did not respond to responsible disclosure, leaving no patch available.
DeepCool DisplayService 1.2.12 on Windows exposes an unauthenticated LocalSystem-level named pipe control channel that any low-privileged local user can connect to and manipulate, enabling full privilege escalation to SYSTEM. The root cause is CWE-284 (Improper Access Control) - the service's IPC channel enforces no caller authentication or ACL verification. A public proof-of-concept is available per VulDB and a researcher's writeup; the vulnerability is not currently listed in CISA KEV, indicating no confirmed mass exploitation, though the low attack complexity and available POC materially elevate near-term risk.
Privilege escalation in Microsoft Purview eDiscovery enables an authenticated low-privileged attacker to gain elevated access over the network, with full confidentiality, integrity, and availability impact once exploited. The vulnerability stems from improper access control (CWE-284), meaning the service fails to enforce authorization boundaries between privilege levels for eDiscovery operations such as case management, legal holds, and content searches. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, though the low attack complexity and network accessibility make this a credible threat in Microsoft 365 enterprise environments.
Privilege elevation in Microsoft Teams lets a remote, unauthenticated attacker gain unauthorized access across a network due to a missing authorization check (CWE-862). The maximum 10.0 CVSS rating stems from a changed scope with high confidentiality and integrity impact, meaning the flaw reaches resources beyond the initially vulnerable component. No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the perfect-score, no-precondition profile makes it a top-tier patch priority.
Privilege elevation in Microsoft Planetary Computer Pro allows a remote, unauthenticated attacker to gain elevated privileges over the network by invoking a critical function that lacks an authentication check (CWE-306). Scored CVSS 10.0 with a scope change, the flaw exposes confidential data and permits unauthorized modification against the affected Azure geospatial platform. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but the maximal score reflects trivial exploitability against exposed instances.
Cryptographic signature spoofing in Microsoft Teams exposes enterprise collaboration environments to unauthenticated identity impersonation over the network. The flaw, tagged as a JWT attack enabling authentication bypass, allows a remote attacker with no prior credentials to forge or tamper with token-based identity claims that Teams fails to properly verify. No active exploitation has been confirmed by CISA KEV, and no public proof-of-concept has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates a low-barrier, remotely exploitable path with high integrity impact.
Privilege elevation in Microsoft Teams allows an authenticated attacker with low-level access to bypass authentication controls and gain higher privileges across a network boundary. The CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H) shows the flaw is remotely reachable, requires only low existing privileges, needs no user interaction, and crosses a security scope to compromise confidentiality and integrity of resources beyond the initially authorized context. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the 9.6 base score reflects the low barrier to abuse once an attacker holds any authenticated Teams foothold.