Authentication Bypass
Monthly
Authentication bypass in Ubiquiti UniFi OS lets a network-adjacent attacker circumvent login on affected devices by injecting CRLF sequences, granting full control over the appliance under certain conditions. It affects a broad range of UniFi OS platforms including Cloud Gateways, Dream Machines/Routers, Cloud Keys, and Enterprise NVR/NAS hardware. Reported by Ubiquiti with a CVSS of 9.0; there is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the high scope-changing impact makes it a priority to patch.
Broken authorization in the Grav API plugin (getgrav/grav-plugin-api) before 1.0.18 lets a holder of a scoped API key view - and potentially edit - a page's security/permission blueprint section beyond the scope their key was granted. The flaw lives in injectSecurityTab() of BlueprintController, which decides editability using raw isSuperAdmin()/hasPermission() checks and never calls scopeAllows(), so the per-key scope cap is silently bypassed. There is no public exploit identified at time of analysis and no KEV listing; the reporter (VulnCheck) explicitly could not confirm the end-to-end write-time impact, so confirmed effect is at least unauthorized disclosure of permission fields.
Broken authorization in getgrav/grav-plugin-api before 1.0.18 lets a scoped API key that belongs to a super-admin account perform privileged user-management actions it was never scoped for. Across seven sensitive endpoints the requireNotSuperTarget() guard in UsersController.php checks isSuperAdmin() on the underlying account instead of whether the presented key carries super authority (isSuperWithinScope()), so a deliberately down-scoped key can act against other super-admin accounts-disabling their 2FA, deleting avatars, and minting or deleting their API keys. Reported by VulnCheck; no public exploit identified at time of analysis, and it is not on CISA KEV.
Complete authentication bypass in TarsWeb (the web console for the TARS microservice framework) through 3.0.14 lets a remote unauthenticated attacker act as any account, including an administrator, by sending a forged X-Forwarded-For header naming the loopback address together with a uid query parameter. Because app.js trusts Koa's proxy option blindly and the SSO middleware treats the loopback allowlist match as authorization to adopt the caller-supplied uid, no ticket, cookie, or password is ever checked. No public exploit is identified at the time of analysis, but the technique is trivial and the CVSS 4.0 base score is 9.3 (Critical).
Missing authorization checks across four methods in TarsWeb's PatchController allow any authenticated account - regardless of its assigned application scope - to deploy arbitrary packages to any server managed by the console, retrieve or delete packages belonging to other applications, and alter default deployment configurations system-wide. Affected versions span TarsWeb through at least v3.0.16 as confirmed by the vulnerable source reference at that tag. No public exploit code has been identified at time of analysis, but the vulnerability is straightforwardly exploitable by any user with a valid TarsWeb account, making it a high-priority internal threat in multi-tenant or shared TarsWeb installations.
Missing authorization on DROP MATERIALIZED VIEW in StarRocks allows any authenticated account to permanently delete legacy synchronous materialized views across all databases, regardless of grants. The flaw exists because `AuthorizerStmtVisitor.visitDropMaterializedViewStatement` exits early without invoking the Authorizer; the authorization branch executes only when the resolved object is a modern `MaterializedView`, not when it is a legacy synchronous view stored as a rollup index on an `OlapTable`. Versions through 4.0.13 are affected per the VulnCheck advisory, and no public exploit has been identified at time of analysis.
Privilege escalation in Ubiquiti's UniFi Network Application allows an already-authenticated, high-privileged user with network access to gain elevated rights within the application through an improper access control (CWE-284) flaw. Ubiquiti self-reported the issue in Security Advisory Bulletin 067 and tags it as an authentication bypass; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. The vendor rates it CVSS 9.1, driven largely by an assumed scope change, though the practical bar is raised by the requirement for pre-existing high privileges.
Privilege escalation in Ubiquiti's UniFi Connect Application allows network-accessible unauthenticated attackers to elevate their access level within the application via an Improper Access Control flaw. The vulnerability, tagged as an authentication bypass, exposes access control management infrastructure to unauthorized privilege acquisition with no user interaction or prior credentials required. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity network attack vector and PR:N classification make this a straightforward target for opportunistic exploitation.
Privilege escalation in Ubiquiti UniFi OS lets a low-privileged actor with network access to an affected device elevate their rights to full administrative control, per Ubiquiti Security Advisory Bulletin 067 (CVE-2026-77536). The flaw stems from improper access control (CWE-284) and carries a near-maximum CVSS 9.9 due to a scope-changing impact across confidentiality, integrity, and availability. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Privilege escalation in Ubiquiti UniFi OS devices allows a network-adjacent attacker holding a low-privileged account to elevate to higher privileges on the affected device or instance due to an improper access control flaw. The issue spans Ubiquiti's core managed platforms - UniFi OS Server, Cloud Keys, Dream Machines/Routers, Cloud Gateways, NVR/Enterprise NVR, Enterprise NAS, and Enterprise Firewall/Fortress Gateway - and carries a critical CVSS 9.9 with a changed scope. No public exploit has been identified at time of analysis, but the low attack complexity and low privilege requirement make it high priority.
NSD's proxy protocol port fails to re-evaluate BLOCKED access control list entries on the second DNS query sent over a kept-open TCP or TLS connection, allowing a remote unauthenticated attacker to bypass ACL denials that should have blocked the request. NLnet Labs reported this against all NSD versions (CPE wildcard scope), classifying it under CWE-290 as an authentication bypass by spoofing. No public exploit code has been identified at time of analysis, but the bypass mechanic - sending a query twice on the same persistent connection - is mechanically trivial once the proxy protocol port is reachable.
IP range-based access control in NLnet Labs NSD is silently broken on little-endian systems due to an endianness mismatch in the range comparison logic. Both IPv4 and IPv6 addresses are compared as unsigned 32-bit integers using host byte order, while the actual stored values are in network byte order (big-endian), causing comparisons to produce incorrect results on the dominant x86/x86-64/ARM-LE server platforms. The practical consequence is a bidirectional access control bypass: operators relying on hyphen-range ACL syntax may inadvertently permit unauthorized IP addresses to access restricted DNS operations (such as zone transfers) while simultaneously denying legitimate clients. No public exploit has been identified at time of analysis, but the flaw is fully deterministic and requires no special attacker capability beyond network reachability.
Privilege escalation in Admin By Request (ABR) for macOS allows a low-privileged local user to obtain full administrator rights by exploiting a predictable PIN derivation mechanism via Apple's Cross-Process Communication (XPC) framework. The attacker masquerades as an Apple-signed process during XPC communication, bypassing ABR's authentication logic entirely. Covered by a vendor security advisory and a CSA alert, the flaw carries a CVSS 8.8 with a scope change; no public exploit or CISA KEV listing has been identified at time of analysis.
Unauthenticated arbitrary file write in the Avada WordPress theme (versions up to and including 7.16) combined with the Fusion Builder plugin (up to and including 3.16) lets remote attackers plant attacker-controlled files - including executable PHP - leading to remote code execution and full site takeover. The flaw is a cross-component chain of broken authorization and weak input validation (CWE-862) reported by Wordfence, and requires both components active plus specific administrator-authored content to be present. No public exploit is identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated account creation in the Project Manager WordPress plugin before version 4.0.7 allows any remote attacker to register WordPress user accounts regardless of the site's registration settings. The import routes in the plugin carry no authorization checks whatsoever (CWE-862), enabling an attacker who already knows the password they will submit to establish a persistent, valid WordPress account on the target site. A publicly available proof-of-concept exploit exists; however, EPSS is currently 0.18% (7th percentile), indicating low observed exploitation volume at the time of analysis.
Remote unauthenticated administrative compromise is possible across three WordPress plugins - BlogVault Backup & Staging, MalCare WordPress Security Plugin, and WP Remote WordPress Plugin - in versions 5.16 through 6.64, due to the combination of a weak pseudo-random number generator used to create site-binding secrets and unauthenticated endpoints leaking data derived from those secrets. An attacker who can observe the leaked derived values can reverse the weak PRNG to reconstruct the original secret, then authenticate to the remote management service with administrative privileges and achieve full site takeover. A publicly available proof-of-concept exists; no CISA KEV listing is present, and EPSS sits at 0.17%, indicating limited observed mass exploitation despite the public exploit.
Header-based identity forgery in AntFlow V2.0.0 allows unauthenticated remote attackers to impersonate any user by supplying an arbitrary userid value in the HTTP request header. The flaw exists because `JiMuMDCCommonsRequestLoggingFilter.java` treats a user-controlled request header as the authoritative identity token, implementing no cryptographic validation, signature check, or server-side session verification. With PR:N and AC:L confirmed by the CVSS vector, exploitation is trivially simple and results in full confidentiality breach of any targeted user account's sensitive data. EPSS is low (0.14%), and no KEV listing exists, but a public researcher write-up is available on GitHub, lowering the bar for exploitation.
Unauthenticated configuration disclosure in SuperDiamond (super-diamond-server) versions 1.3.3 and earlier exposes the Netty-based configuration distribution service on TCP port 8283 without any authentication mechanism. Any remote attacker who can reach the port can send a raw TCP request and retrieve the complete configuration of any managed project, including database passwords and API keys. A public write-up exists but there is no public exploit identified as weaponized tooling, and the flaw is not in CISA KEV; EPSS is low at 0.17% (6th percentile).
Authentication bypass in DWSurvey v6.14.0 lets remote unauthenticated attackers reach protected API functionality through the '/api/dwsurvey/none/' and '/api/dwsurvey/up/**' endpoint paths, which are treated as public and skip access-control checks. A public technical writeup describing the flaw exists; it is not listed in CISA KEV and the EPSS probability is low (0.18%, 8th percentile), indicating no evidence of widespread automated exploitation yet despite the critical 9.8 CVSS rating.
Authorization bypass in the Kimai open-source time-tracking application before 2.56.0 lets any authenticated user holding ROLE_TEAMLEAD (or any role granting edit_other_timesheet/delete_other_timesheet) read, modify, and permanently delete timesheets belonging to any user system-wide through the REST API, ignoring team boundaries. Because timesheet IDs are sequential integers, an attacker can enumerate and target every record, enabling destruction of billable hours and forgery of payroll/invoicing data. Publicly available exploit code exists (working API PoC in the GHSA advisory, verified against 2.52.0), though the vulnerability is not listed in CISA KEV and no EPSS score was provided.
Cross-user bookmark tampering in Kimai versions before 2.57.0 allows any authenticated low-privileged user to inject or remove timesheet entries from another user's favorites list via an IDOR flaw (CWE-639) in the favorite add and remove endpoints. Any account holding the standard `start_own_timesheet` permission can reference another user's timesheet identifier to manipulate their `favorite/recent` workflow state without administrative access. No confirmed active exploitation exists (not in CISA KEV); a PoC was submitted during responsible disclosure but removed before public release. Vendor-released patch is available in version 2.57.0.
Password reset links in Kimai before 2.58.0 function as persistent authentication credentials because the LoginLink HMAC signature is bound only to the user's database ID, not the password hash. An attacker who obtains an intercepted or cached reset link can authenticate as the victim up to 2 additional times within a 1-hour window even after the victim has changed their password, obtaining a fully authenticated session. A publicly documented proof-of-concept is included in the GHSA advisory; no active exploitation via CISA KEV has been confirmed.
Team membership disruption in Kimai before 2.63.0 allows authenticated teamleads to permanently strip all members from any team they can edit by exploiting a non-atomic delete-before-validate workflow in the PATCH /api/teams/{id} endpoint. The endpoint deletes all existing member rows before completing validation of the replacement list; when a malformed payload triggers a validation error, the deletion is not rolled back, leaving teams with no members or teamleaders and collapsing team-based access control. No public exploit has been identified and active exploitation is not confirmed by CISA KEV, but the CVSS 4.0 score of 8.7 and low-privilege attack vector make this a credible insider or compromised-account threat.
Authorization bypass in Kimai's QuickEntry controller allows authenticated network users holding view_other_timesheet and edit_other_timesheet permissions to create timesheet records on behalf of team members without possessing the required create_other_timesheet permission. The missing server-side authorization check (CWE-862) in the QuickEntry submission path enables unauthorized data manipulation across organizational user boundaries within the time-tracking system. No public exploit code or active exploitation has been identified; a vendor-released patch is available in Kimai 2.62.0.
Two domain-ownership authentication bypass flaws in @better-auth/sso allow authenticated organization owners to compromise user account integrity via unauthorized organization assignment or identity provider hijacking. Affected versions span the stable 1.6.x line (before 1.6.27), the 1.4.x maintenance line (before 1.4.8), and the 1.7 prerelease line (before 1.7.0-rc.5). An attacker holding an org-owner role can either silently recruit users with matching email domains into an attacker-controlled organization by registering an unverified SSO provider, or exploit a race condition between verification and update endpoints to substitute a different domain after DNS proof is collected - which, combined with implicit account linking, enables effective account takeover. No public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated file disclosure in GROWI (all versions before 8.0.2) exposes private page attachments to any caller who possesses a valid attachment identifier. The route handler retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts conditionally gates the page-viewer permission check on the presence of an authenticated session, meaning HTTP requests without a session entirely bypass authorization and receive the requested file. Both /attachment/:id and /download/:id endpoints are affected, and identifiers are obtainable by former users whose access was revoked or from any prior exposure of the attachment URL. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Authentication bypass in the Drupal Internationalization Single Sign-On contributed module (versions 0.0.0 through 1.8.0) lets remote unauthenticated attackers assume authenticated sessions by reaching an alternate authentication path or channel that skips the primary verification logic. Rated CVSS 9.8 with full confidentiality, integrity, and availability impact, it maps to CWE-288 and is addressed in a Drupal security advisory (SA-CONTRIB-2026-081). EPSS is low (0.18%, 8th percentile) and there is no public exploit identified at time of analysis.
Authorization bypass in the Drupal Webform REST contrib module (all versions from 0.0.0 up to and including 4.1.0) lets remote unauthenticated attackers reach REST resources they should not be able to access through forceful browsing. Because the module fails to properly enforce access checks on its endpoints, an attacker can read and potentially manipulate webform data or submissions guarded only by obscurity. No public exploit is identified at time of analysis and EPSS risk is low (0.18%, 7th percentile), but the CVSS 9.1 rating and SSVC 'total technical impact' make this a high-severity data-exposure issue.
Missing authorization in the Drupal PhotoSwipe - Responsive JavaScript Modal Image Gallery contributed module (all versions from 0.0.0 up to and including 3.2.0) lets unauthenticated remote users reach gallery resources they should not be able to see by directly requesting their URLs (forceful browsing). Because the module fails to enforce access control on protected content, an attacker can enumerate and retrieve images or associated data intended for privileged users only. No public exploit identified at time of analysis, and EPSS is low (0.13%), but the flaw is trivially automatable per CISA SSVC.
Incorrect authorization in the Drupal Edit in-place field contrib module (versions 0.0.0 through pre-2.1.1) enables authenticated users to perform forceful browsing against field-edit endpoints they lack permission to access, resulting in unauthorized read and write access to protected Drupal field data. The CVSS base score of 8.1 reflects high confidentiality and integrity impact, though real-world risk is tempered by the authentication prerequisite (PR:L) and an extremely low EPSS score of 0.13% (3rd percentile). A vendor-released patch is available; no public exploit identified at time of analysis.
Project scope bypass in OpenStack Keystone before 29.0.3 allows authenticated users holding delegated credentials - OAuth1 access tokens, application credentials, or trusts - to escape their intended project authorization boundary by submitting these tokens to the standard token-method authentication endpoint for reauthentication. When an application credential token is presented without an explicit scope parameter, Keystone incorrectly resolves scope to the credential owner's default project rather than the project for which the credential was originally issued, granting unintended cross-project access. No public exploit has been identified and the flaw is absent from CISA KEV, but the CVSS 4.0 score of 7.6 with high confidentiality and integrity impact makes this a priority for any multi-tenant OpenStack operator issuing delegated credentials across project boundaries.
Privilege escalation in OpenStack Keystone before 29.0.3 allows authenticated users holding delegated tokens - issued via OAuth1 access tokens, application credentials, or trust-scoped authentication - to create new long-lived credentials or authorize additional delegations that outlive the original parent credential. The core security contract of delegation scoping is broken: a derived token can exceed and survive the authority of the credential used to obtain it, because delegation restriction checks were not applied uniformly across all delegated token types. All Keystone deployments that have enabled OAuth1, application credentials, or trusts are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Improper Authentication in Apache Tomcat allows a remote, low-privileged attacker to gain authenticated access to applications even when the presented identity does not exist in the configured DataSourceRealm. The flaw is triggered specifically under CLIENT-CERT or SPNEGO authentication schemes, causing Tomcat to grant a session to a non-existent user. No public exploit or CISA KEV listing is present at time of analysis, but the CVSS C:H/I:H impact rating reflects the potential to fully compromise protected application resources if exploited in matching deployments.
Authorization bypass in Apache Tomcat's FORM-based authentication lets attackers reach protected resources that a security constraint was meant to restrict, defeating rules that grant a role POST access but withhold GET (or vice versa) on the same URL. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.0-8.5.100 and 7.0.0-7.0.109. There is no public exploit identified at time of analysis, and EPSS is low (0.28%), but CISA SSVC rates the technical impact as total and the attack as automatable.
Improper Authorization in Apache Tomcat causes security-role-ref mappings - intended only for servlet-level isUserInRole() checks - to be incorrectly applied as role aliases within the Realm's authorization logic, allowing authenticated low-privileged users to access resources protected by higher-privileged roles. Supported branches 9.0.25-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24 are confirmed affected, along with EOL branches 7.0.97-7.0.109 and 8.5.46-8.5.100. No public exploit identified at time of analysis, and EPSS probability stands at 0.20% (10th percentile), though the CVSS 8.1 score reflects meaningful integrity and availability exposure in deployments relying on Realm-enforced role separation.
Authentication bypass in Apache Tomcat's DIGEST authenticator lets a network attacker who has captured a valid DIGEST-authenticated request replay it once when its nonceCount sits on the upper boundary of the replay window and fewer than windowSize requests have since been made. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.x and 7.0.x branches, but only where DIGEST authentication is actually enabled. No public exploit identified at time of analysis; EPSS is low at 0.28% (20th percentile), so the assigned 9.8 overstates practical risk.
Security constraint bypass in Apache Tomcat (7.0.x through 11.0.x) lets remote unauthenticated attackers reach protected resources when a broader security constraint for a longer path is declared ahead of a more restrictive constraint for a shorter sub-path, causing the wrong constraint to be applied. The flaw (CVSS 9.1, CWE-284) exposes access-controlled application paths without valid credentials. No public exploit identified at time of analysis, and EPSS is low (0.23%), but the network-reachable, no-interaction profile makes it a meaningful patch priority.
Unauthenticated user data enumeration in Maccms v10 v2026.1000.4055 allows any remote attacker to retrieve the complete registered user database through the /api.php/user/get_list endpoint, which performs no authentication or authorization checks whatsoever. Attackers craft HTTP GET requests with limit and offset parameters to paginate through all user records, exposing usernames, email addresses, and any other stored profile data. EPSS at 0.32% (24th percentile) and absence from CISA KEV indicate no current widespread exploitation, though the trivial single-request attack mechanic makes this a viable data-harvesting vector if the application gains attacker attention.
Unauthenticated access to the NVIDIA NemoClaw inference server on Linux exposes sensitive model inference data and enables denial of service by adjacent network attackers. The flaw stems from a missing authentication check (CWE-306) on the inference service endpoint, meaning any host on the same network segment can interact with the service without credentials. No active exploitation has been confirmed by CISA KEV and no public exploit code is known at time of analysis, but the low attack complexity and absence of authentication barriers make this straightforward to exploit for any attacker with adjacent network positioning.
Web origin policy bypass in Google Chrome for Android before 152.0.7977.65 lets a malicious co-installed app abuse the CustomTabs component to escape same-origin restrictions and access content it should not. The flaw is a local privilege/authorization issue (Chromium-rated Low severity) requiring a second attacker-controlled app already present on the device; no public exploit has been identified and EPSS probability is very low (0.11%).
UI spoofing in Google Chrome's Passwords component (versions prior to 152.0.7977.65) lets a remote attacker who has already compromised the renderer process present forged interface elements via a crafted HTML page, enabling deception such as credential phishing. Chromium rated this severity Low, and no public exploit or active exploitation has been identified; EPSS is low at 0.23% (14th percentile). The headline NVD CVSS of 9.1 substantially overstates the practical impact given the required renderer compromise.
Incorrect authorization in the Chromoting component of Google Chrome on Windows prior to version 152.0.7977.65 enables a local attacker with standard user privileges to bypass system access restrictions by executing a crafted local program. The flaw (CWE-863) undermines Chrome Remote Desktop's authorization enforcement on Windows, allowing unauthorized access to protected system resources with both high confidentiality and integrity impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.11% places this in the 1st percentile, indicating very low current exploitation probability despite the 7.1 CVSS base score.
CustomTabs in Google Chrome for Android prior to version 152.0.7977.65 exposes a missing authorization flaw (CWE-862) that allows a local attacker, operating through a co-installed malicious application, to potentially escape the Chrome sandbox and execute arbitrary code. The Chromium security team rated this Medium severity internally, and the EPSS score of 0.13% at the 3rd percentile confirms no observed exploitation activity. A vendor patch has been released in Chrome 152.0.7977.65; no public exploit code or CISA KEV listing exists at time of analysis.
Sandbox escape via incorrect USB authorization in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox through a crafted HTML page combined with social engineering. The attack chain is multi-stage: the USB subsystem fails to correctly authorize renderer-process requests, enabling a scoped privilege escalation out of the sandbox (S:C in CVSS). No public exploit code is identified and SSVC assessment confirms no known exploitation at time of analysis, though successful exploitation would yield total technical impact.
UI misrepresentation in Google Chrome's Browser component prior to 152.0.7977.65 enables a remote attacker to bypass system access restrictions through a crafted HTML page combined with social engineering. The flaw (CWE-451) allows the browser to render misleading UI elements that deceive users into believing they are interacting with a trusted context, enabling restriction bypasses with high confidentiality and integrity impact. No public exploit code or CISA KEV listing exists at time of analysis; vendor patch is available.
Sandbox escape in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has first compromised the renderer process to break out of Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. Rooted in CWE-863 (Incorrect Authorization), the Chrome sandbox fails to correctly enforce permission checks on requests originating from a compromised renderer, permitting privilege escalation beyond the sandbox boundary. No public exploit code has been identified at time of analysis, and EPSS scores a low current exploitation probability of 0.24% (15th percentile), though the full-compromise impact potential warrants prompt patching across all Chrome desktop deployments.
Content Security Policy enforcement failure in Safari's AudioWorklet contexts allows remote attackers to bypass CSP restrictions when a user processes maliciously crafted web content. Affected platforms include Safari before 26.5, iOS and iPadOS before 18.7.9/26.5, and macOS Tahoe before 26.5. Apple has released patches across all affected platforms; no public exploit or CISA KEV listing is identified at time of analysis.
Cross-workspace authorization bypass in Airbyte Platform through v2.0.0 allows any authenticated workspace member to read, modify, and delete resources in workspaces they have no access to. The flaw in AuthenticationHeaderResolver.resolveWorkspace prioritizes a caller-supplied X-Airbyte-Workspace-Id value for authorization, while the actual operation executes against the caller-supplied resource identifier - with no subsequent reconciliation check. A publicly available exploit exists (reported by VulnCheck), and exploitation requires only basic workspace membership, making this a realistic lateral-movement vector in any multi-tenant Airbyte deployment.
Identity spoofing and authentication bypass in Alluxio's S3 REST proxy (versions through 2.9.5) lets remote unauthenticated attackers impersonate any user because the proxy does not verify AWS Signature Version 4 signatures in its default configuration. By reading the username directly from an unsigned Authorization header, an attacker can assume the identity of arbitrary users and service accounts to read, write, and delete data. Reported by VulnCheck with a CVSS 4.0 base score of 9.3; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in NVIDIA UFM Enterprise's web interface authorization component allows an attacker on the adjacent network to send specially crafted HTTP requests that circumvent authentication checks, yielding code execution and privilege escalation on the UFM management host. All four active release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are listed as affected per NVD CPE data. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.
Unauthenticated vector-store tampering in Nextcloud MCP Server before 0.117.2 lets any network attacker who can reach the /webhooks/nextcloud endpoint delete or force re-indexing of Qdrant semantic-search embeddings for arbitrary users. Because WEBHOOK_SECRET defaults to None and startup never enforces it, the webhook receiver processes forged POSTs and trusts the attacker-supplied user.uid, so looping over document IDs can wipe the entire search index for all users. A working proof-of-concept is published in the GHSA advisory; publicly available exploit code exists, though there is no public exploit identified in CISA KEV.
Authentication bypass in djust's WebSocket LiveView consumer allows unauthenticated remote clients to invoke protected event handlers on views gated by login_required, permission_required, or redirecting on_mount hooks. All djust versions prior to 1.0.4 are affected: handle_mount sends a navigate/redirect frame on auth denial but neither closes the WebSocket nor clears self.view_instance, leaving the socket open and exploitable. Because handle_event never rechecks authentication after mount, a non-browser WebSocket client that ignores the redirect can send arbitrary event frames and execute state-mutating or data-reading handlers without an authenticated session. No public exploit identified at time of analysis beyond the WebsocketCommunicator proof-of-concept reproducer disclosed in GHSA-xx4j-w367-7247; this vulnerability is not listed in CISA KEV.
WebSocket origin-validation bypass in PraisonAI's Browser Server (praisonai/browser/server.py) before 4.6.58 lets an attacker forge a Chrome-extension Origin header and drive connected browser extensions. The check uses re.match() against the unanchored pattern chrome-extension://[a-z0-9]{32}, so any Origin with 32+ trailing characters is accepted before websocket.accept(), after which start_session commands trigger arbitrary browser automation, cookie theft, and screenshot capture. This is a patch bypass of CVE-2026-40289 (GHSA-8x8f-54wf-vv92); a working PoC is published in the advisory, though it is not in CISA KEV - no public exploit weaponization beyond the advisory PoC is identified.
Path traversal in NLTK before 3.10.3 exposes arbitrary filesystem content and SQLite databases by bypassing the library's pathsec sandbox boundary. The LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors accept caller-supplied corpus root paths without enforcing the intended data-root restriction, enabling CWE-73 (External Control of File Name or Path) exploitation wherever applications forward user-controlled input to these constructors. No public exploit or CISA KEV listing has been identified at time of analysis; real-world severity is highly dependent on whether the affected constructors are reachable from an untrusted network path in the deploying application.
Authentication fail-open in PraisonAI's Recipe HTTP server allows unauthenticated remote attackers to invoke recipe execution endpoints despite authentication being nominally enabled. Versions prior to 4.6.58 of the pip package are affected: when the server is started with --auth api-key or --auth jwt but the corresponding PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET environment variable is absent, create_auth_middleware() silently bypasses all authentication checks. The CLI safety check that blocks external binding only verifies auth mode is not 'none', failing to detect this secret-absent misconfiguration, leaving POST /v1/recipes/run, /v1/recipes/stream, and /v1/recipes endpoints fully open to unauthenticated callers. No active exploitation is confirmed (not in CISA KEV); vendor-released patch is available in v4.6.58.
PraisonAI's async Jobs API FastAPI service exposes all seven `/api/v1/runs` endpoints - submit, list, status, result, cancel, delete, and stream - with zero authentication on every route, allowing any network-reachable caller to execute arbitrary prompts against the operator's configured LLM credentials and enumerate or exfiltrate cross-tenant job outputs. Publicly available exploit code is documented in GHSA-2jgc-f764-c5r2, with all five attack primitives confirmed via proof-of-concept returning HTTP 202/200/204 with no credentials. This is a distinct, unpatched sibling of CVE-2026-44338 - the Flask server fix at 4.6.34 did not touch the FastAPI jobs module, which remained fully unauthenticated through version 4.6.51.
Repository migration operations in JFrog Artifactory expose a missing authorization check (CWE-862) that allows any authenticated low-privileged user to initiate migrations against repositories they do not have permission to access or control. Affected instances across all Artifactory versions per the CPE wildcard are subject to information disclosure of restricted artifact contents, unauthorized state changes via migration side-effects, and high-impact service disruption to artifact delivery pipelines. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, though the CVSS 7.6 High rating and PR:L attack vector make it a realistic insider or compromised-credential threat.
PraisonAI's `praisonai serve` subsystem (agents and unified modes) accepts an `--api-key` CLI flag that is parsed but never wired into the underlying FastAPI application, leaving POST /agents, POST /agents/{name}, and POST /api/v1/agents/{id}/invoke fully unauthenticated regardless of any key configured by the operator. All versions prior to 4.6.58 are affected, with the flaw present since approximately 4.6.34 when the serve subsystem first shipped. A public proof-of-concept exists per the GHSA advisory; no public exploit identified at time of analysis in CISA KEV, but the zero-authentication network attack surface makes this a high-priority fix for any deployment exposing the serve interface to untrusted networks.
Authentication bypass in PraisonAI's HTTP agent-serving layer allows unauthenticated remote invocation of registered agents despite the operator having configured an API key via --api-key. The root defect is in _create_agents_app(): it never reads config["api_key"] and never attaches a FastAPI Depends() auth dependency to POST /agents and POST /agents/{agent_name}, making the advertised --api-key flag a no-op. A public proof-of-concept confirms HTTP 200 responses to credentialless requests on all agent invocation routes while sibling /api/v1/ routes correctly return 401; no CISA KEV listing was identified at time of analysis.
Unauthenticated remote agent invocation in PraisonAI versions 4.6.34 through 4.6.57 allows any network-reachable caller to execute configured agents via POST /agents and POST /agents/{agent_name} despite an operator-supplied --api-key. The FastAPI app created by _create_agents_app() accepts the key at the CLI layer but never applies it as middleware or a route dependency, rendering the documented authentication control entirely inert on those endpoints. A proof-of-concept is included in GHSA-7ww9-85pg-cv4x, and the flaw is fixed in v4.6.58 via an _authorise_request() method that enforces Bearer or X-Auth-Token header validation.
Authentication bypass in PraisonAI's AgentServer component exposes all routes - /publish, /events, /info, /health - to unauthenticated remote callers, even when operators have explicitly configured an auth_token in ServerConfig. The AgentServer._create_app factory never reads or enforces the configured token, rendering it dead code while /info actively misleads operators by displaying it as masked ('***'), creating a false sense of security. No public exploit code has been identified at time of analysis, and it is not listed in CISA KEV; the fix is confirmed in praisonaiagents 1.6.58.
Unauthenticated authentication bypass in miniOrange's SAML Single Sign-On extensions for Joomla (SAML SSO < 11.0.2, SAML SP Login with ADFS < 6.4, and SAML SSO login with Google Apps < 6.4) lets remote attackers log in as any Joomla account, including administrators. The mo_saml_validate_signature() function treats OpenSSL's -1 error return as a successful signature verification, so a crafted SAMLResponse with an attacker-chosen NameID and a deliberately malformed signature bypasses validation entirely. Rated CVSS 4.0 10.0; no public exploit identified at time of analysis, but the flaw is trivially reachable and yields full site takeover.
Remote code execution in the WatchGuard Agent allows an unauthenticated attacker with network access to trigger arbitrary code execution at elevated privilege due to an improper authentication flaw (CWE-306). The CVSS 4.0 base score of 9.3 reflects a network-reachable, no-interaction, no-privilege attack yielding full confidentiality, integrity, and availability impact on the affected host. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but the combination of pre-auth reachability and privileged code execution makes this a high-priority exposure.
Remote code execution in WatchGuard Agent lets an unauthenticated attacker positioned on an adjacent network chain a missing-authentication weakness (CWE-306) with path traversal into arbitrary code execution on the host. Rated CVSS 4.0 9.4 (Critical) by WatchGuard, the flaw combines an authentication bypass with directory traversal so no credentials or user interaction are required. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the network-adjacent, no-auth, high-impact profile makes it a high-priority patch item.
Privilege escalation in Ech0 before 4.4.3 allows an attacker holding an admin's profile:read access token to change the admin's password via a misauthorized PUT /user endpoint, then authenticate to obtain an unrestricted session token that bypasses all scope enforcement. The CWE-863 root cause is a mismatch between the declared read-only scope on the route and the write operations the handler actually performs; session tokens produced after login skip scope checks entirely, granting full admin API access. Publicly available exploit code exists per the GHSA advisory; no confirmed active exploitation in CISA KEV at time of analysis.
Scope enforcement bypass in Ech0's comment panel admin API allows any holder of a valid admin-issued access token - regardless of its configured permission scope - to perform unrestricted comment moderation operations across nine unprotected endpoints. All versions of Ech0 before 4.4.3 (CPE: cpe:2.3:a:lin-snow:ech0:*) are affected; the comment router omits the RequireScopes() middleware that every other admin route group in the application applies per-handler. No public exploit has been identified at time of analysis, but exploitation complexity is low for any attacker already holding a scoped access token, making upgrade to 4.4.3 the immediate priority.
Scope enforcement in Ech0 4.3.4 and earlier is opt-in at the route level, meaning privileged admin routes that omit the RequireScopes() middleware fall back to role-only checks and honor any valid admin token regardless of declared scope. An admin holding a deliberately narrowed API token - for example one scoped to echo:read - can reach endpoints such as /api/inbox, /api/panel/comments, and /api/backup/export, with the backup handler additionally stripping scope metadata entirely and returning a full database ZIP archive. No CISA KEV listing or confirmed public exploit code has been identified; the vulnerability is fixed in an upstream release (version discrepancy noted below).
Missing administrator authorization on dashboard log endpoints in Ech0 before 4.4.3 allows any authenticated low-privilege user to read historical system logs and subscribe to live log streams via GET /api/system/logs, SSE, and WebSocket endpoints. Affected deployments expose operational data including internal file paths, stack traces, admin activity records, background job output, and internal URLs to any valid session holder. No public exploit has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog, but the low exploitation complexity and high confidentiality impact make this a meaningful post-authentication information disclosure risk for multi-user deployments.
Authorization bypass in Ech0 before 4.5.1 allows any authenticated non-admin user to invoke privileged admin endpoints by sending a valid session token to routes unprotected by the RequireScopes middleware. Affected instances expose system logs, visitor statistics, user email addresses, and live WebSocket log streams to any logged-in user regardless of their assigned role. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, the low attack complexity and network accessibility make this a realistic threat in any multi-user Ech0 deployment.
Authentication bypass in Apache HiveServer2 4.0.0-4.2.0 allows unauthenticated network attackers to impersonate any Hive user and obtain a fully authenticated HiveServer2 session when SAML mode is enabled over HTTP transport. The root cause is an inverted HMAC signature comparison in HiveSamlAuthTokenGenerator.java - the original code used !MessageDigest.isEqual(), causing all tokens to pass validation regardless of signature correctness, meaning a forged bearer token with any embedded username is unconditionally accepted. No CISA KEV listing and an EPSS of 0.14% (4th percentile) indicate no confirmed active exploitation at time of analysis, but the logic flaw is trivially exploitable once the deployment condition is met.
Authentication bypass in LACT (Linux AMD GPU Configuration Tool) through version 0.10.0 allows a local attacker with low privileges to circumvent Polkit-based access controls by exploiting PID reuse in the UnixProcessSubject / Peer PID authentication mechanism (CWE-290). By winning a race condition between Polkit's process identity check and authorization grant, an attacker can spoof their process as a legitimately authorized caller and gain unauthorized control over privileged GPU configuration operations. No public exploit code has been identified and no active exploitation has been confirmed at time of analysis.
Cache-poisoning-based access control bypass in the Apache Solr for TYPO3 Enterprise Search extension allows anonymous visitors to read pages that should be protected by extendToSubpages-inherited frontend-group restrictions. The extension fails to isolate its forged access-restriction state during indexer sub-requests, writing empty frontend-group and subpage-inheritance flags into the shared TYPO3 rootline cache, where they persist and serve subsequent user requests without the original restrictions applied. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 7.6 with combined high confidentiality and integrity impact reflects meaningful severity for any TYPO3 deployment relying on page-level inherited access controls.
The femanager extension for TYPO3 CMS incorrectly accepts a regular user confirmation hash - obtainable by any visitor via the public resend-confirmation action - in place of the privileged admin confirmation token when processing account-approval requests. This allows a registrant whose account is pending administrator authorization to self-approve that account, fully bypassing the admin-approval gate. No public exploit code has been identified at time of analysis, but the attack is mechanically trivial given the public exposure of the prerequisite token; the CVSS 4.0 score of 8.3 reflects high confidentiality impact against the vulnerable system.
Insecure Direct Object Reference in the TYPO3 femanager extension exposes frontend user profile data - including name, email address, date of birth, and postal address - to any unauthenticated visitor who can reach the Detail or List plugin. The extension's user detail view accepts a caller-supplied user ID without validating that the requested record belongs to the configured or authenticated target, making horizontal privilege escalation trivial via ID enumeration. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
Unauthenticated record tampering in the TYPO3 Telephone Directory extension allows any visitor who can identify an employee UID to overwrite that employee's data via a direct POST request, bypassing HMAC-based edit-link authorization entirely. The extension enforces HMAC validation only at the form-render step, leaving the persistence action unprotected under CWE-862 (Missing Authorization). With a CVSS 4.0 score of 8.7 and an attack profile of network-accessible, no-privilege, no-interaction, no public exploit has been identified at time of analysis, but the attack requires no authentication and minimal attacker capability.
Unauthenticated record takeover in the TYPO3 'Club Directory' extension allows any visitor to overwrite or force-publish arbitrary club records by supplying a known record UID in requests to the frontend edit, update, and activate actions. The extension resolves records directly from user-controlled input without performing any ownership or authorization check, making this a textbook CWE-862 (Missing Authorization) / IDOR vulnerability. No public exploit has been identified at time of analysis, but exploitation is trivially simple given the network-accessible attack surface, absence of authentication, and sequential nature of TYPO3 record UIDs.
Broken access control in the TYPO3 Industry Directory extension allows unauthenticated network visitors to overwrite company records they do not own. The frontend edit form is gated by a template-level visibility flag, but the server-side write controller performs no corresponding ownership verification, making the UI restriction trivially bypassable via direct HTTP submission using any publicly visible record identifier. No public exploit code or CISA KEV listing has been identified at time of analysis, but the absence of authentication requirements and low attack complexity make independent exploitation straightforward against any exposed deployment.
Missing server-side ownership verification in the TYPO3 Forum extension allows any unauthenticated visitor to overwrite the content of any forum topic. Because topic identifiers are enumerable from the public forum listing, an attacker needs no credentials, special access, or non-default configuration to target arbitrary topics. The CVSS 4.0 score of 8.8 reflects high integrity impact; no public exploit or CISA KEV listing has been identified at time of analysis.
Cross-organizer event modification in the TYPO3 Events 2 extension allows any authenticated frontend event manager to tamper with events owned by other organizers. The frontend management update flow performs its authorization check against a different event identifier than the one the request ultimately modifies - a textbook CWE-639 IDOR mismatch - granting write access beyond the user's legitimate scope. No public exploit has been identified at time of analysis, but with a CVSS 4.0 score of 7.1 (VI:H) and only low-privilege authentication required (PR:L), the integrity risk is meaningful in any multi-organizer TYPO3 deployment.
Unauthenticated account takeover in the TYPO3 femanager extension 8.x allows a remote attacker to reset the password of and re-enable any existing frontend user account - including disabled or deleted ones - by exploiting an invitation controller that continues processing after issuing a redirect on invalid input. No prior authentication or user interaction is required. No public exploit code or active exploitation has been identified at time of analysis, but the impact is severe: full account takeover of arbitrary frontend users in any TYPO3 installation running femanager 8.x.
JWT token replay in AshAuthentication exposes any application using the stateless bearer-token path to full account takeover using purpose-scoped tokens. The `retrieve_from_bearer/3` helper in versions 3.10.5-4.14.2 and 5.0.0-rc.0-5.0.0-rc.13 verifies JWT signatures and rejects tokens with an `act` claim, but never validates that the token's `purpose` claim equals "user", allowing sign-in, remember-me, and TOTP-setup tokens to be silently accepted as full bearer credentials. No public exploit has been identified at time of analysis, but the attack requires only obtaining a still-valid, not-yet-exchanged sign-in token - a realistic threat surface via log leakage, referrer exposure, or intercepted magic-link delivery.
Hard-coded credentials in all versions of the Furuno FA-50 maritime AIS transponder allow any attacker with knowledge of the static credentials and access to the vessel's internal network to authenticate to the device's settings screen and alter the vessel's identification number. Modification of the AIS identification number (MMSI) carries serious maritime safety implications, enabling vessel impersonation or disruption of AIS-based collision avoidance and vessel tracking systems. Disclosed via JPCERT coordination and JVN advisory JVNVU95422936; no public exploit has been identified at time of analysis.
Configuration manipulation in the Furuno FA-50 maritime device (all versions) is possible without authentication from the vessel's internal network. The product fails to enforce access controls on its settings interface (CWE-306), allowing any attacker who gains internal network access to alter device configuration parameters. No public exploit code has been identified at time of analysis, and the device is not listed in CISA KEV, but the unauthenticated network-accessible vector and high integrity impact (CVSS 4.0: 8.7, VI:H) make this a meaningful risk in maritime operational environments.
Local privilege escalation to SYSTEM in SKYSEA Client View and SKYMEC IT Manager allows any authenticated Windows user to execute arbitrary code with SYSTEM-level privileges. The root cause is a missing authorization check (CWE-862) within one or more privileged components of these IT asset management products. No public exploit identified at time of analysis, and this vulnerability has not been listed in the CISA KEV catalog, but the low-privilege local exploitation path and full SYSTEM compromise make it a significant risk in multi-user or shared Windows environments where these products are deployed.
Privilege escalation via account takeover in InfusedWoo Pro (all versions up to and including 5.1.17) allows any authenticated subscriber-level user to hijack arbitrary WordPress accounts, including site administrators, by exploiting a missing capability check in the `ajax_iwar_preview_email()` AJAX function. The function incorrectly relies on `is_admin()` - a WordPress conditional that tests for admin-area request context rather than the requesting user's role - permitting low-privilege users to generate valid password reset links for any email address on the site. No public exploit has been identified at time of analysis, but the trivial exploitation path (subscriber-level access, no user interaction, no special configuration) makes this a high-priority remediation target for any site running the affected plugin.
Arbitrary file read in GitPython before 3.1.59 allows low-privileged remote attackers to exfiltrate sensitive files by supplying a crafted reference argument to TagReference.create(). The vulnerability arises because a positional reference parameter (e.g., '--file=/etc/passwd') bypasses the library's built-in unsafe option guard, causing git to interpret the value as a flag and return the targeted file's contents embedded in the annotated tag message. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 7.1 with high confidentiality impact reflects genuine disclosure risk in any application that exposes this code path to user-controlled input.
Credential extraction in Grav CMS before 2.0.16 allows authenticated users with page-edit permissions to read hashed passwords and two-factor authentication secrets from User objects via insufficiently filtered Twig template sandbox methods. The allow-listed offsetGet() and offsetExists() methods on User objects expose sensitive fields that should be restricted within the sandboxed template context, enabling offline password cracking and subsequent authentication bypass. No public exploit has been identified at time of analysis, but the exploit technique is straightforward for any attacker holding page-edit rights.
Origin validation bypass in Grav CMS before 2.0.16 lets remote attackers defeat the Referer-based same-origin check used by the Uri::referrer() and Pages::referrerRoute() methods. Because the check uses an unanchored str_starts_with() prefix match without a trailing delimiter, a request bearing a Referer from an attacker-controlled look-alike domain (e.g. https://example.com.attacker.tld) is accepted as same-origin, undermining CSRF/origin protections on protected routes. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Broken authorization in the Grav Login plugin before 1.0.16 lets an operator holding the api.users.write permission clear login lockout counters on admin.super accounts through the onApiUserListRowAction unlock handler, which never checks the target account's privilege tier. This strips brute-force protection from the highest-privilege accounts, enabling a lower-privileged user to set up password-guessing against super-admin credentials. Reported by VulnCheck with no public exploit identified at time of analysis and no CISA KEV listing.
Host header injection in Grav CMS before 3.9.2 allows attackers to poison outgoing invitation emails, replacing the legitimate site URL with an attacker-controlled domain in token-bearing links sent via the sendInvitationEmail() function. The vulnerability exploits a gap in Grav's existing Host header defenses: the require_trusted_host protection was applied only to password reset flows, leaving invitation emails without equivalent validation. When a poisoned invitation email is delivered and the recipient clicks the link, the one-time invitation token is transmitted to the attacker's server rather than the legitimate site. No public exploit has been identified at time of analysis, and the CVE is not listed in the CISA KEV catalog, though the reported CVSS 4.0 score of 8.7 reflects high confidentiality risk from token capture.
Authentication bypass in Ubiquiti UniFi OS lets a network-adjacent attacker circumvent login on affected devices by injecting CRLF sequences, granting full control over the appliance under certain conditions. It affects a broad range of UniFi OS platforms including Cloud Gateways, Dream Machines/Routers, Cloud Keys, and Enterprise NVR/NAS hardware. Reported by Ubiquiti with a CVSS of 9.0; there is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the high scope-changing impact makes it a priority to patch.
Broken authorization in the Grav API plugin (getgrav/grav-plugin-api) before 1.0.18 lets a holder of a scoped API key view - and potentially edit - a page's security/permission blueprint section beyond the scope their key was granted. The flaw lives in injectSecurityTab() of BlueprintController, which decides editability using raw isSuperAdmin()/hasPermission() checks and never calls scopeAllows(), so the per-key scope cap is silently bypassed. There is no public exploit identified at time of analysis and no KEV listing; the reporter (VulnCheck) explicitly could not confirm the end-to-end write-time impact, so confirmed effect is at least unauthorized disclosure of permission fields.
Broken authorization in getgrav/grav-plugin-api before 1.0.18 lets a scoped API key that belongs to a super-admin account perform privileged user-management actions it was never scoped for. Across seven sensitive endpoints the requireNotSuperTarget() guard in UsersController.php checks isSuperAdmin() on the underlying account instead of whether the presented key carries super authority (isSuperWithinScope()), so a deliberately down-scoped key can act against other super-admin accounts-disabling their 2FA, deleting avatars, and minting or deleting their API keys. Reported by VulnCheck; no public exploit identified at time of analysis, and it is not on CISA KEV.
Complete authentication bypass in TarsWeb (the web console for the TARS microservice framework) through 3.0.14 lets a remote unauthenticated attacker act as any account, including an administrator, by sending a forged X-Forwarded-For header naming the loopback address together with a uid query parameter. Because app.js trusts Koa's proxy option blindly and the SSO middleware treats the loopback allowlist match as authorization to adopt the caller-supplied uid, no ticket, cookie, or password is ever checked. No public exploit is identified at the time of analysis, but the technique is trivial and the CVSS 4.0 base score is 9.3 (Critical).
Missing authorization checks across four methods in TarsWeb's PatchController allow any authenticated account - regardless of its assigned application scope - to deploy arbitrary packages to any server managed by the console, retrieve or delete packages belonging to other applications, and alter default deployment configurations system-wide. Affected versions span TarsWeb through at least v3.0.16 as confirmed by the vulnerable source reference at that tag. No public exploit code has been identified at time of analysis, but the vulnerability is straightforwardly exploitable by any user with a valid TarsWeb account, making it a high-priority internal threat in multi-tenant or shared TarsWeb installations.
Missing authorization on DROP MATERIALIZED VIEW in StarRocks allows any authenticated account to permanently delete legacy synchronous materialized views across all databases, regardless of grants. The flaw exists because `AuthorizerStmtVisitor.visitDropMaterializedViewStatement` exits early without invoking the Authorizer; the authorization branch executes only when the resolved object is a modern `MaterializedView`, not when it is a legacy synchronous view stored as a rollup index on an `OlapTable`. Versions through 4.0.13 are affected per the VulnCheck advisory, and no public exploit has been identified at time of analysis.
Privilege escalation in Ubiquiti's UniFi Network Application allows an already-authenticated, high-privileged user with network access to gain elevated rights within the application through an improper access control (CWE-284) flaw. Ubiquiti self-reported the issue in Security Advisory Bulletin 067 and tags it as an authentication bypass; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. The vendor rates it CVSS 9.1, driven largely by an assumed scope change, though the practical bar is raised by the requirement for pre-existing high privileges.
Privilege escalation in Ubiquiti's UniFi Connect Application allows network-accessible unauthenticated attackers to elevate their access level within the application via an Improper Access Control flaw. The vulnerability, tagged as an authentication bypass, exposes access control management infrastructure to unauthorized privilege acquisition with no user interaction or prior credentials required. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity network attack vector and PR:N classification make this a straightforward target for opportunistic exploitation.
Privilege escalation in Ubiquiti UniFi OS lets a low-privileged actor with network access to an affected device elevate their rights to full administrative control, per Ubiquiti Security Advisory Bulletin 067 (CVE-2026-77536). The flaw stems from improper access control (CWE-284) and carries a near-maximum CVSS 9.9 due to a scope-changing impact across confidentiality, integrity, and availability. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Privilege escalation in Ubiquiti UniFi OS devices allows a network-adjacent attacker holding a low-privileged account to elevate to higher privileges on the affected device or instance due to an improper access control flaw. The issue spans Ubiquiti's core managed platforms - UniFi OS Server, Cloud Keys, Dream Machines/Routers, Cloud Gateways, NVR/Enterprise NVR, Enterprise NAS, and Enterprise Firewall/Fortress Gateway - and carries a critical CVSS 9.9 with a changed scope. No public exploit has been identified at time of analysis, but the low attack complexity and low privilege requirement make it high priority.
NSD's proxy protocol port fails to re-evaluate BLOCKED access control list entries on the second DNS query sent over a kept-open TCP or TLS connection, allowing a remote unauthenticated attacker to bypass ACL denials that should have blocked the request. NLnet Labs reported this against all NSD versions (CPE wildcard scope), classifying it under CWE-290 as an authentication bypass by spoofing. No public exploit code has been identified at time of analysis, but the bypass mechanic - sending a query twice on the same persistent connection - is mechanically trivial once the proxy protocol port is reachable.
IP range-based access control in NLnet Labs NSD is silently broken on little-endian systems due to an endianness mismatch in the range comparison logic. Both IPv4 and IPv6 addresses are compared as unsigned 32-bit integers using host byte order, while the actual stored values are in network byte order (big-endian), causing comparisons to produce incorrect results on the dominant x86/x86-64/ARM-LE server platforms. The practical consequence is a bidirectional access control bypass: operators relying on hyphen-range ACL syntax may inadvertently permit unauthorized IP addresses to access restricted DNS operations (such as zone transfers) while simultaneously denying legitimate clients. No public exploit has been identified at time of analysis, but the flaw is fully deterministic and requires no special attacker capability beyond network reachability.
Privilege escalation in Admin By Request (ABR) for macOS allows a low-privileged local user to obtain full administrator rights by exploiting a predictable PIN derivation mechanism via Apple's Cross-Process Communication (XPC) framework. The attacker masquerades as an Apple-signed process during XPC communication, bypassing ABR's authentication logic entirely. Covered by a vendor security advisory and a CSA alert, the flaw carries a CVSS 8.8 with a scope change; no public exploit or CISA KEV listing has been identified at time of analysis.
Unauthenticated arbitrary file write in the Avada WordPress theme (versions up to and including 7.16) combined with the Fusion Builder plugin (up to and including 3.16) lets remote attackers plant attacker-controlled files - including executable PHP - leading to remote code execution and full site takeover. The flaw is a cross-component chain of broken authorization and weak input validation (CWE-862) reported by Wordfence, and requires both components active plus specific administrator-authored content to be present. No public exploit is identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated account creation in the Project Manager WordPress plugin before version 4.0.7 allows any remote attacker to register WordPress user accounts regardless of the site's registration settings. The import routes in the plugin carry no authorization checks whatsoever (CWE-862), enabling an attacker who already knows the password they will submit to establish a persistent, valid WordPress account on the target site. A publicly available proof-of-concept exploit exists; however, EPSS is currently 0.18% (7th percentile), indicating low observed exploitation volume at the time of analysis.
Remote unauthenticated administrative compromise is possible across three WordPress plugins - BlogVault Backup & Staging, MalCare WordPress Security Plugin, and WP Remote WordPress Plugin - in versions 5.16 through 6.64, due to the combination of a weak pseudo-random number generator used to create site-binding secrets and unauthenticated endpoints leaking data derived from those secrets. An attacker who can observe the leaked derived values can reverse the weak PRNG to reconstruct the original secret, then authenticate to the remote management service with administrative privileges and achieve full site takeover. A publicly available proof-of-concept exists; no CISA KEV listing is present, and EPSS sits at 0.17%, indicating limited observed mass exploitation despite the public exploit.
Header-based identity forgery in AntFlow V2.0.0 allows unauthenticated remote attackers to impersonate any user by supplying an arbitrary userid value in the HTTP request header. The flaw exists because `JiMuMDCCommonsRequestLoggingFilter.java` treats a user-controlled request header as the authoritative identity token, implementing no cryptographic validation, signature check, or server-side session verification. With PR:N and AC:L confirmed by the CVSS vector, exploitation is trivially simple and results in full confidentiality breach of any targeted user account's sensitive data. EPSS is low (0.14%), and no KEV listing exists, but a public researcher write-up is available on GitHub, lowering the bar for exploitation.
Unauthenticated configuration disclosure in SuperDiamond (super-diamond-server) versions 1.3.3 and earlier exposes the Netty-based configuration distribution service on TCP port 8283 without any authentication mechanism. Any remote attacker who can reach the port can send a raw TCP request and retrieve the complete configuration of any managed project, including database passwords and API keys. A public write-up exists but there is no public exploit identified as weaponized tooling, and the flaw is not in CISA KEV; EPSS is low at 0.17% (6th percentile).
Authentication bypass in DWSurvey v6.14.0 lets remote unauthenticated attackers reach protected API functionality through the '/api/dwsurvey/none/' and '/api/dwsurvey/up/**' endpoint paths, which are treated as public and skip access-control checks. A public technical writeup describing the flaw exists; it is not listed in CISA KEV and the EPSS probability is low (0.18%, 8th percentile), indicating no evidence of widespread automated exploitation yet despite the critical 9.8 CVSS rating.
Authorization bypass in the Kimai open-source time-tracking application before 2.56.0 lets any authenticated user holding ROLE_TEAMLEAD (or any role granting edit_other_timesheet/delete_other_timesheet) read, modify, and permanently delete timesheets belonging to any user system-wide through the REST API, ignoring team boundaries. Because timesheet IDs are sequential integers, an attacker can enumerate and target every record, enabling destruction of billable hours and forgery of payroll/invoicing data. Publicly available exploit code exists (working API PoC in the GHSA advisory, verified against 2.52.0), though the vulnerability is not listed in CISA KEV and no EPSS score was provided.
Cross-user bookmark tampering in Kimai versions before 2.57.0 allows any authenticated low-privileged user to inject or remove timesheet entries from another user's favorites list via an IDOR flaw (CWE-639) in the favorite add and remove endpoints. Any account holding the standard `start_own_timesheet` permission can reference another user's timesheet identifier to manipulate their `favorite/recent` workflow state without administrative access. No confirmed active exploitation exists (not in CISA KEV); a PoC was submitted during responsible disclosure but removed before public release. Vendor-released patch is available in version 2.57.0.
Password reset links in Kimai before 2.58.0 function as persistent authentication credentials because the LoginLink HMAC signature is bound only to the user's database ID, not the password hash. An attacker who obtains an intercepted or cached reset link can authenticate as the victim up to 2 additional times within a 1-hour window even after the victim has changed their password, obtaining a fully authenticated session. A publicly documented proof-of-concept is included in the GHSA advisory; no active exploitation via CISA KEV has been confirmed.
Team membership disruption in Kimai before 2.63.0 allows authenticated teamleads to permanently strip all members from any team they can edit by exploiting a non-atomic delete-before-validate workflow in the PATCH /api/teams/{id} endpoint. The endpoint deletes all existing member rows before completing validation of the replacement list; when a malformed payload triggers a validation error, the deletion is not rolled back, leaving teams with no members or teamleaders and collapsing team-based access control. No public exploit has been identified and active exploitation is not confirmed by CISA KEV, but the CVSS 4.0 score of 8.7 and low-privilege attack vector make this a credible insider or compromised-account threat.
Authorization bypass in Kimai's QuickEntry controller allows authenticated network users holding view_other_timesheet and edit_other_timesheet permissions to create timesheet records on behalf of team members without possessing the required create_other_timesheet permission. The missing server-side authorization check (CWE-862) in the QuickEntry submission path enables unauthorized data manipulation across organizational user boundaries within the time-tracking system. No public exploit code or active exploitation has been identified; a vendor-released patch is available in Kimai 2.62.0.
Two domain-ownership authentication bypass flaws in @better-auth/sso allow authenticated organization owners to compromise user account integrity via unauthorized organization assignment or identity provider hijacking. Affected versions span the stable 1.6.x line (before 1.6.27), the 1.4.x maintenance line (before 1.4.8), and the 1.7 prerelease line (before 1.7.0-rc.5). An attacker holding an org-owner role can either silently recruit users with matching email domains into an attacker-controlled organization by registering an unverified SSO provider, or exploit a race condition between verification and update endpoints to substitute a different domain after DNS proof is collected - which, combined with implicit account linking, enables effective account takeover. No public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated file disclosure in GROWI (all versions before 8.0.2) exposes private page attachments to any caller who possesses a valid attachment identifier. The route handler retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts conditionally gates the page-viewer permission check on the presence of an authenticated session, meaning HTTP requests without a session entirely bypass authorization and receive the requested file. Both /attachment/:id and /download/:id endpoints are affected, and identifiers are obtainable by former users whose access was revoked or from any prior exposure of the attachment URL. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Authentication bypass in the Drupal Internationalization Single Sign-On contributed module (versions 0.0.0 through 1.8.0) lets remote unauthenticated attackers assume authenticated sessions by reaching an alternate authentication path or channel that skips the primary verification logic. Rated CVSS 9.8 with full confidentiality, integrity, and availability impact, it maps to CWE-288 and is addressed in a Drupal security advisory (SA-CONTRIB-2026-081). EPSS is low (0.18%, 8th percentile) and there is no public exploit identified at time of analysis.
Authorization bypass in the Drupal Webform REST contrib module (all versions from 0.0.0 up to and including 4.1.0) lets remote unauthenticated attackers reach REST resources they should not be able to access through forceful browsing. Because the module fails to properly enforce access checks on its endpoints, an attacker can read and potentially manipulate webform data or submissions guarded only by obscurity. No public exploit is identified at time of analysis and EPSS risk is low (0.18%, 7th percentile), but the CVSS 9.1 rating and SSVC 'total technical impact' make this a high-severity data-exposure issue.
Missing authorization in the Drupal PhotoSwipe - Responsive JavaScript Modal Image Gallery contributed module (all versions from 0.0.0 up to and including 3.2.0) lets unauthenticated remote users reach gallery resources they should not be able to see by directly requesting their URLs (forceful browsing). Because the module fails to enforce access control on protected content, an attacker can enumerate and retrieve images or associated data intended for privileged users only. No public exploit identified at time of analysis, and EPSS is low (0.13%), but the flaw is trivially automatable per CISA SSVC.
Incorrect authorization in the Drupal Edit in-place field contrib module (versions 0.0.0 through pre-2.1.1) enables authenticated users to perform forceful browsing against field-edit endpoints they lack permission to access, resulting in unauthorized read and write access to protected Drupal field data. The CVSS base score of 8.1 reflects high confidentiality and integrity impact, though real-world risk is tempered by the authentication prerequisite (PR:L) and an extremely low EPSS score of 0.13% (3rd percentile). A vendor-released patch is available; no public exploit identified at time of analysis.
Project scope bypass in OpenStack Keystone before 29.0.3 allows authenticated users holding delegated credentials - OAuth1 access tokens, application credentials, or trusts - to escape their intended project authorization boundary by submitting these tokens to the standard token-method authentication endpoint for reauthentication. When an application credential token is presented without an explicit scope parameter, Keystone incorrectly resolves scope to the credential owner's default project rather than the project for which the credential was originally issued, granting unintended cross-project access. No public exploit has been identified and the flaw is absent from CISA KEV, but the CVSS 4.0 score of 7.6 with high confidentiality and integrity impact makes this a priority for any multi-tenant OpenStack operator issuing delegated credentials across project boundaries.
Privilege escalation in OpenStack Keystone before 29.0.3 allows authenticated users holding delegated tokens - issued via OAuth1 access tokens, application credentials, or trust-scoped authentication - to create new long-lived credentials or authorize additional delegations that outlive the original parent credential. The core security contract of delegation scoping is broken: a derived token can exceed and survive the authority of the credential used to obtain it, because delegation restriction checks were not applied uniformly across all delegated token types. All Keystone deployments that have enabled OAuth1, application credentials, or trusts are affected; no public exploit code or CISA KEV listing has been identified at time of analysis.
Improper Authentication in Apache Tomcat allows a remote, low-privileged attacker to gain authenticated access to applications even when the presented identity does not exist in the configured DataSourceRealm. The flaw is triggered specifically under CLIENT-CERT or SPNEGO authentication schemes, causing Tomcat to grant a session to a non-existent user. No public exploit or CISA KEV listing is present at time of analysis, but the CVSS C:H/I:H impact rating reflects the potential to fully compromise protected application resources if exploited in matching deployments.
Authorization bypass in Apache Tomcat's FORM-based authentication lets attackers reach protected resources that a security constraint was meant to restrict, defeating rules that grant a role POST access but withhold GET (or vice versa) on the same URL. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.0-8.5.100 and 7.0.0-7.0.109. There is no public exploit identified at time of analysis, and EPSS is low (0.28%), but CISA SSVC rates the technical impact as total and the attack as automatable.
Improper Authorization in Apache Tomcat causes security-role-ref mappings - intended only for servlet-level isUserInRole() checks - to be incorrectly applied as role aliases within the Realm's authorization logic, allowing authenticated low-privileged users to access resources protected by higher-privileged roles. Supported branches 9.0.25-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24 are confirmed affected, along with EOL branches 7.0.97-7.0.109 and 8.5.46-8.5.100. No public exploit identified at time of analysis, and EPSS probability stands at 0.20% (10th percentile), though the CVSS 8.1 score reflects meaningful integrity and availability exposure in deployments relying on Realm-enforced role separation.
Authentication bypass in Apache Tomcat's DIGEST authenticator lets a network attacker who has captured a valid DIGEST-authenticated request replay it once when its nonceCount sits on the upper boundary of the replay window and fewer than windowSize requests have since been made. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.x and 7.0.x branches, but only where DIGEST authentication is actually enabled. No public exploit identified at time of analysis; EPSS is low at 0.28% (20th percentile), so the assigned 9.8 overstates practical risk.
Security constraint bypass in Apache Tomcat (7.0.x through 11.0.x) lets remote unauthenticated attackers reach protected resources when a broader security constraint for a longer path is declared ahead of a more restrictive constraint for a shorter sub-path, causing the wrong constraint to be applied. The flaw (CVSS 9.1, CWE-284) exposes access-controlled application paths without valid credentials. No public exploit identified at time of analysis, and EPSS is low (0.23%), but the network-reachable, no-interaction profile makes it a meaningful patch priority.
Unauthenticated user data enumeration in Maccms v10 v2026.1000.4055 allows any remote attacker to retrieve the complete registered user database through the /api.php/user/get_list endpoint, which performs no authentication or authorization checks whatsoever. Attackers craft HTTP GET requests with limit and offset parameters to paginate through all user records, exposing usernames, email addresses, and any other stored profile data. EPSS at 0.32% (24th percentile) and absence from CISA KEV indicate no current widespread exploitation, though the trivial single-request attack mechanic makes this a viable data-harvesting vector if the application gains attacker attention.
Unauthenticated access to the NVIDIA NemoClaw inference server on Linux exposes sensitive model inference data and enables denial of service by adjacent network attackers. The flaw stems from a missing authentication check (CWE-306) on the inference service endpoint, meaning any host on the same network segment can interact with the service without credentials. No active exploitation has been confirmed by CISA KEV and no public exploit code is known at time of analysis, but the low attack complexity and absence of authentication barriers make this straightforward to exploit for any attacker with adjacent network positioning.
Web origin policy bypass in Google Chrome for Android before 152.0.7977.65 lets a malicious co-installed app abuse the CustomTabs component to escape same-origin restrictions and access content it should not. The flaw is a local privilege/authorization issue (Chromium-rated Low severity) requiring a second attacker-controlled app already present on the device; no public exploit has been identified and EPSS probability is very low (0.11%).
UI spoofing in Google Chrome's Passwords component (versions prior to 152.0.7977.65) lets a remote attacker who has already compromised the renderer process present forged interface elements via a crafted HTML page, enabling deception such as credential phishing. Chromium rated this severity Low, and no public exploit or active exploitation has been identified; EPSS is low at 0.23% (14th percentile). The headline NVD CVSS of 9.1 substantially overstates the practical impact given the required renderer compromise.
Incorrect authorization in the Chromoting component of Google Chrome on Windows prior to version 152.0.7977.65 enables a local attacker with standard user privileges to bypass system access restrictions by executing a crafted local program. The flaw (CWE-863) undermines Chrome Remote Desktop's authorization enforcement on Windows, allowing unauthorized access to protected system resources with both high confidentiality and integrity impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.11% places this in the 1st percentile, indicating very low current exploitation probability despite the 7.1 CVSS base score.
CustomTabs in Google Chrome for Android prior to version 152.0.7977.65 exposes a missing authorization flaw (CWE-862) that allows a local attacker, operating through a co-installed malicious application, to potentially escape the Chrome sandbox and execute arbitrary code. The Chromium security team rated this Medium severity internally, and the EPSS score of 0.13% at the 3rd percentile confirms no observed exploitation activity. A vendor patch has been released in Chrome 152.0.7977.65; no public exploit code or CISA KEV listing exists at time of analysis.
Sandbox escape via incorrect USB authorization in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox through a crafted HTML page combined with social engineering. The attack chain is multi-stage: the USB subsystem fails to correctly authorize renderer-process requests, enabling a scoped privilege escalation out of the sandbox (S:C in CVSS). No public exploit code is identified and SSVC assessment confirms no known exploitation at time of analysis, though successful exploitation would yield total technical impact.
UI misrepresentation in Google Chrome's Browser component prior to 152.0.7977.65 enables a remote attacker to bypass system access restrictions through a crafted HTML page combined with social engineering. The flaw (CWE-451) allows the browser to render misleading UI elements that deceive users into believing they are interacting with a trusted context, enabling restriction bypasses with high confidentiality and integrity impact. No public exploit code or CISA KEV listing exists at time of analysis; vendor patch is available.
Sandbox escape in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has first compromised the renderer process to break out of Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. Rooted in CWE-863 (Incorrect Authorization), the Chrome sandbox fails to correctly enforce permission checks on requests originating from a compromised renderer, permitting privilege escalation beyond the sandbox boundary. No public exploit code has been identified at time of analysis, and EPSS scores a low current exploitation probability of 0.24% (15th percentile), though the full-compromise impact potential warrants prompt patching across all Chrome desktop deployments.
Content Security Policy enforcement failure in Safari's AudioWorklet contexts allows remote attackers to bypass CSP restrictions when a user processes maliciously crafted web content. Affected platforms include Safari before 26.5, iOS and iPadOS before 18.7.9/26.5, and macOS Tahoe before 26.5. Apple has released patches across all affected platforms; no public exploit or CISA KEV listing is identified at time of analysis.
Cross-workspace authorization bypass in Airbyte Platform through v2.0.0 allows any authenticated workspace member to read, modify, and delete resources in workspaces they have no access to. The flaw in AuthenticationHeaderResolver.resolveWorkspace prioritizes a caller-supplied X-Airbyte-Workspace-Id value for authorization, while the actual operation executes against the caller-supplied resource identifier - with no subsequent reconciliation check. A publicly available exploit exists (reported by VulnCheck), and exploitation requires only basic workspace membership, making this a realistic lateral-movement vector in any multi-tenant Airbyte deployment.
Identity spoofing and authentication bypass in Alluxio's S3 REST proxy (versions through 2.9.5) lets remote unauthenticated attackers impersonate any user because the proxy does not verify AWS Signature Version 4 signatures in its default configuration. By reading the username directly from an unsigned Authorization header, an attacker can assume the identity of arbitrary users and service accounts to read, write, and delete data. Reported by VulnCheck with a CVSS 4.0 base score of 9.3; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in NVIDIA UFM Enterprise's web interface authorization component allows an attacker on the adjacent network to send specially crafted HTTP requests that circumvent authentication checks, yielding code execution and privilege escalation on the UFM management host. All four active release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are listed as affected per NVD CPE data. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.
Unauthenticated vector-store tampering in Nextcloud MCP Server before 0.117.2 lets any network attacker who can reach the /webhooks/nextcloud endpoint delete or force re-indexing of Qdrant semantic-search embeddings for arbitrary users. Because WEBHOOK_SECRET defaults to None and startup never enforces it, the webhook receiver processes forged POSTs and trusts the attacker-supplied user.uid, so looping over document IDs can wipe the entire search index for all users. A working proof-of-concept is published in the GHSA advisory; publicly available exploit code exists, though there is no public exploit identified in CISA KEV.
Authentication bypass in djust's WebSocket LiveView consumer allows unauthenticated remote clients to invoke protected event handlers on views gated by login_required, permission_required, or redirecting on_mount hooks. All djust versions prior to 1.0.4 are affected: handle_mount sends a navigate/redirect frame on auth denial but neither closes the WebSocket nor clears self.view_instance, leaving the socket open and exploitable. Because handle_event never rechecks authentication after mount, a non-browser WebSocket client that ignores the redirect can send arbitrary event frames and execute state-mutating or data-reading handlers without an authenticated session. No public exploit identified at time of analysis beyond the WebsocketCommunicator proof-of-concept reproducer disclosed in GHSA-xx4j-w367-7247; this vulnerability is not listed in CISA KEV.
WebSocket origin-validation bypass in PraisonAI's Browser Server (praisonai/browser/server.py) before 4.6.58 lets an attacker forge a Chrome-extension Origin header and drive connected browser extensions. The check uses re.match() against the unanchored pattern chrome-extension://[a-z0-9]{32}, so any Origin with 32+ trailing characters is accepted before websocket.accept(), after which start_session commands trigger arbitrary browser automation, cookie theft, and screenshot capture. This is a patch bypass of CVE-2026-40289 (GHSA-8x8f-54wf-vv92); a working PoC is published in the advisory, though it is not in CISA KEV - no public exploit weaponization beyond the advisory PoC is identified.
Path traversal in NLTK before 3.10.3 exposes arbitrary filesystem content and SQLite databases by bypassing the library's pathsec sandbox boundary. The LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors accept caller-supplied corpus root paths without enforcing the intended data-root restriction, enabling CWE-73 (External Control of File Name or Path) exploitation wherever applications forward user-controlled input to these constructors. No public exploit or CISA KEV listing has been identified at time of analysis; real-world severity is highly dependent on whether the affected constructors are reachable from an untrusted network path in the deploying application.
Authentication fail-open in PraisonAI's Recipe HTTP server allows unauthenticated remote attackers to invoke recipe execution endpoints despite authentication being nominally enabled. Versions prior to 4.6.58 of the pip package are affected: when the server is started with --auth api-key or --auth jwt but the corresponding PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET environment variable is absent, create_auth_middleware() silently bypasses all authentication checks. The CLI safety check that blocks external binding only verifies auth mode is not 'none', failing to detect this secret-absent misconfiguration, leaving POST /v1/recipes/run, /v1/recipes/stream, and /v1/recipes endpoints fully open to unauthenticated callers. No active exploitation is confirmed (not in CISA KEV); vendor-released patch is available in v4.6.58.
PraisonAI's async Jobs API FastAPI service exposes all seven `/api/v1/runs` endpoints - submit, list, status, result, cancel, delete, and stream - with zero authentication on every route, allowing any network-reachable caller to execute arbitrary prompts against the operator's configured LLM credentials and enumerate or exfiltrate cross-tenant job outputs. Publicly available exploit code is documented in GHSA-2jgc-f764-c5r2, with all five attack primitives confirmed via proof-of-concept returning HTTP 202/200/204 with no credentials. This is a distinct, unpatched sibling of CVE-2026-44338 - the Flask server fix at 4.6.34 did not touch the FastAPI jobs module, which remained fully unauthenticated through version 4.6.51.
Repository migration operations in JFrog Artifactory expose a missing authorization check (CWE-862) that allows any authenticated low-privileged user to initiate migrations against repositories they do not have permission to access or control. Affected instances across all Artifactory versions per the CPE wildcard are subject to information disclosure of restricted artifact contents, unauthorized state changes via migration side-effects, and high-impact service disruption to artifact delivery pipelines. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, though the CVSS 7.6 High rating and PR:L attack vector make it a realistic insider or compromised-credential threat.
PraisonAI's `praisonai serve` subsystem (agents and unified modes) accepts an `--api-key` CLI flag that is parsed but never wired into the underlying FastAPI application, leaving POST /agents, POST /agents/{name}, and POST /api/v1/agents/{id}/invoke fully unauthenticated regardless of any key configured by the operator. All versions prior to 4.6.58 are affected, with the flaw present since approximately 4.6.34 when the serve subsystem first shipped. A public proof-of-concept exists per the GHSA advisory; no public exploit identified at time of analysis in CISA KEV, but the zero-authentication network attack surface makes this a high-priority fix for any deployment exposing the serve interface to untrusted networks.
Authentication bypass in PraisonAI's HTTP agent-serving layer allows unauthenticated remote invocation of registered agents despite the operator having configured an API key via --api-key. The root defect is in _create_agents_app(): it never reads config["api_key"] and never attaches a FastAPI Depends() auth dependency to POST /agents and POST /agents/{agent_name}, making the advertised --api-key flag a no-op. A public proof-of-concept confirms HTTP 200 responses to credentialless requests on all agent invocation routes while sibling /api/v1/ routes correctly return 401; no CISA KEV listing was identified at time of analysis.
Unauthenticated remote agent invocation in PraisonAI versions 4.6.34 through 4.6.57 allows any network-reachable caller to execute configured agents via POST /agents and POST /agents/{agent_name} despite an operator-supplied --api-key. The FastAPI app created by _create_agents_app() accepts the key at the CLI layer but never applies it as middleware or a route dependency, rendering the documented authentication control entirely inert on those endpoints. A proof-of-concept is included in GHSA-7ww9-85pg-cv4x, and the flaw is fixed in v4.6.58 via an _authorise_request() method that enforces Bearer or X-Auth-Token header validation.
Authentication bypass in PraisonAI's AgentServer component exposes all routes - /publish, /events, /info, /health - to unauthenticated remote callers, even when operators have explicitly configured an auth_token in ServerConfig. The AgentServer._create_app factory never reads or enforces the configured token, rendering it dead code while /info actively misleads operators by displaying it as masked ('***'), creating a false sense of security. No public exploit code has been identified at time of analysis, and it is not listed in CISA KEV; the fix is confirmed in praisonaiagents 1.6.58.
Unauthenticated authentication bypass in miniOrange's SAML Single Sign-On extensions for Joomla (SAML SSO < 11.0.2, SAML SP Login with ADFS < 6.4, and SAML SSO login with Google Apps < 6.4) lets remote attackers log in as any Joomla account, including administrators. The mo_saml_validate_signature() function treats OpenSSL's -1 error return as a successful signature verification, so a crafted SAMLResponse with an attacker-chosen NameID and a deliberately malformed signature bypasses validation entirely. Rated CVSS 4.0 10.0; no public exploit identified at time of analysis, but the flaw is trivially reachable and yields full site takeover.
Remote code execution in the WatchGuard Agent allows an unauthenticated attacker with network access to trigger arbitrary code execution at elevated privilege due to an improper authentication flaw (CWE-306). The CVSS 4.0 base score of 9.3 reflects a network-reachable, no-interaction, no-privilege attack yielding full confidentiality, integrity, and availability impact on the affected host. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but the combination of pre-auth reachability and privileged code execution makes this a high-priority exposure.
Remote code execution in WatchGuard Agent lets an unauthenticated attacker positioned on an adjacent network chain a missing-authentication weakness (CWE-306) with path traversal into arbitrary code execution on the host. Rated CVSS 4.0 9.4 (Critical) by WatchGuard, the flaw combines an authentication bypass with directory traversal so no credentials or user interaction are required. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the network-adjacent, no-auth, high-impact profile makes it a high-priority patch item.
Privilege escalation in Ech0 before 4.4.3 allows an attacker holding an admin's profile:read access token to change the admin's password via a misauthorized PUT /user endpoint, then authenticate to obtain an unrestricted session token that bypasses all scope enforcement. The CWE-863 root cause is a mismatch between the declared read-only scope on the route and the write operations the handler actually performs; session tokens produced after login skip scope checks entirely, granting full admin API access. Publicly available exploit code exists per the GHSA advisory; no confirmed active exploitation in CISA KEV at time of analysis.
Scope enforcement bypass in Ech0's comment panel admin API allows any holder of a valid admin-issued access token - regardless of its configured permission scope - to perform unrestricted comment moderation operations across nine unprotected endpoints. All versions of Ech0 before 4.4.3 (CPE: cpe:2.3:a:lin-snow:ech0:*) are affected; the comment router omits the RequireScopes() middleware that every other admin route group in the application applies per-handler. No public exploit has been identified at time of analysis, but exploitation complexity is low for any attacker already holding a scoped access token, making upgrade to 4.4.3 the immediate priority.
Scope enforcement in Ech0 4.3.4 and earlier is opt-in at the route level, meaning privileged admin routes that omit the RequireScopes() middleware fall back to role-only checks and honor any valid admin token regardless of declared scope. An admin holding a deliberately narrowed API token - for example one scoped to echo:read - can reach endpoints such as /api/inbox, /api/panel/comments, and /api/backup/export, with the backup handler additionally stripping scope metadata entirely and returning a full database ZIP archive. No CISA KEV listing or confirmed public exploit code has been identified; the vulnerability is fixed in an upstream release (version discrepancy noted below).
Missing administrator authorization on dashboard log endpoints in Ech0 before 4.4.3 allows any authenticated low-privilege user to read historical system logs and subscribe to live log streams via GET /api/system/logs, SSE, and WebSocket endpoints. Affected deployments expose operational data including internal file paths, stack traces, admin activity records, background job output, and internal URLs to any valid session holder. No public exploit has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog, but the low exploitation complexity and high confidentiality impact make this a meaningful post-authentication information disclosure risk for multi-user deployments.
Authorization bypass in Ech0 before 4.5.1 allows any authenticated non-admin user to invoke privileged admin endpoints by sending a valid session token to routes unprotected by the RequireScopes middleware. Affected instances expose system logs, visitor statistics, user email addresses, and live WebSocket log streams to any logged-in user regardless of their assigned role. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, the low attack complexity and network accessibility make this a realistic threat in any multi-user Ech0 deployment.
Authentication bypass in Apache HiveServer2 4.0.0-4.2.0 allows unauthenticated network attackers to impersonate any Hive user and obtain a fully authenticated HiveServer2 session when SAML mode is enabled over HTTP transport. The root cause is an inverted HMAC signature comparison in HiveSamlAuthTokenGenerator.java - the original code used !MessageDigest.isEqual(), causing all tokens to pass validation regardless of signature correctness, meaning a forged bearer token with any embedded username is unconditionally accepted. No CISA KEV listing and an EPSS of 0.14% (4th percentile) indicate no confirmed active exploitation at time of analysis, but the logic flaw is trivially exploitable once the deployment condition is met.
Authentication bypass in LACT (Linux AMD GPU Configuration Tool) through version 0.10.0 allows a local attacker with low privileges to circumvent Polkit-based access controls by exploiting PID reuse in the UnixProcessSubject / Peer PID authentication mechanism (CWE-290). By winning a race condition between Polkit's process identity check and authorization grant, an attacker can spoof their process as a legitimately authorized caller and gain unauthorized control over privileged GPU configuration operations. No public exploit code has been identified and no active exploitation has been confirmed at time of analysis.
Cache-poisoning-based access control bypass in the Apache Solr for TYPO3 Enterprise Search extension allows anonymous visitors to read pages that should be protected by extendToSubpages-inherited frontend-group restrictions. The extension fails to isolate its forged access-restriction state during indexer sub-requests, writing empty frontend-group and subpage-inheritance flags into the shared TYPO3 rootline cache, where they persist and serve subsequent user requests without the original restrictions applied. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 7.6 with combined high confidentiality and integrity impact reflects meaningful severity for any TYPO3 deployment relying on page-level inherited access controls.
The femanager extension for TYPO3 CMS incorrectly accepts a regular user confirmation hash - obtainable by any visitor via the public resend-confirmation action - in place of the privileged admin confirmation token when processing account-approval requests. This allows a registrant whose account is pending administrator authorization to self-approve that account, fully bypassing the admin-approval gate. No public exploit code has been identified at time of analysis, but the attack is mechanically trivial given the public exposure of the prerequisite token; the CVSS 4.0 score of 8.3 reflects high confidentiality impact against the vulnerable system.
Insecure Direct Object Reference in the TYPO3 femanager extension exposes frontend user profile data - including name, email address, date of birth, and postal address - to any unauthenticated visitor who can reach the Detail or List plugin. The extension's user detail view accepts a caller-supplied user ID without validating that the requested record belongs to the configured or authenticated target, making horizontal privilege escalation trivial via ID enumeration. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
Unauthenticated record tampering in the TYPO3 Telephone Directory extension allows any visitor who can identify an employee UID to overwrite that employee's data via a direct POST request, bypassing HMAC-based edit-link authorization entirely. The extension enforces HMAC validation only at the form-render step, leaving the persistence action unprotected under CWE-862 (Missing Authorization). With a CVSS 4.0 score of 8.7 and an attack profile of network-accessible, no-privilege, no-interaction, no public exploit has been identified at time of analysis, but the attack requires no authentication and minimal attacker capability.
Unauthenticated record takeover in the TYPO3 'Club Directory' extension allows any visitor to overwrite or force-publish arbitrary club records by supplying a known record UID in requests to the frontend edit, update, and activate actions. The extension resolves records directly from user-controlled input without performing any ownership or authorization check, making this a textbook CWE-862 (Missing Authorization) / IDOR vulnerability. No public exploit has been identified at time of analysis, but exploitation is trivially simple given the network-accessible attack surface, absence of authentication, and sequential nature of TYPO3 record UIDs.
Broken access control in the TYPO3 Industry Directory extension allows unauthenticated network visitors to overwrite company records they do not own. The frontend edit form is gated by a template-level visibility flag, but the server-side write controller performs no corresponding ownership verification, making the UI restriction trivially bypassable via direct HTTP submission using any publicly visible record identifier. No public exploit code or CISA KEV listing has been identified at time of analysis, but the absence of authentication requirements and low attack complexity make independent exploitation straightforward against any exposed deployment.
Missing server-side ownership verification in the TYPO3 Forum extension allows any unauthenticated visitor to overwrite the content of any forum topic. Because topic identifiers are enumerable from the public forum listing, an attacker needs no credentials, special access, or non-default configuration to target arbitrary topics. The CVSS 4.0 score of 8.8 reflects high integrity impact; no public exploit or CISA KEV listing has been identified at time of analysis.
Cross-organizer event modification in the TYPO3 Events 2 extension allows any authenticated frontend event manager to tamper with events owned by other organizers. The frontend management update flow performs its authorization check against a different event identifier than the one the request ultimately modifies - a textbook CWE-639 IDOR mismatch - granting write access beyond the user's legitimate scope. No public exploit has been identified at time of analysis, but with a CVSS 4.0 score of 7.1 (VI:H) and only low-privilege authentication required (PR:L), the integrity risk is meaningful in any multi-organizer TYPO3 deployment.
Unauthenticated account takeover in the TYPO3 femanager extension 8.x allows a remote attacker to reset the password of and re-enable any existing frontend user account - including disabled or deleted ones - by exploiting an invitation controller that continues processing after issuing a redirect on invalid input. No prior authentication or user interaction is required. No public exploit code or active exploitation has been identified at time of analysis, but the impact is severe: full account takeover of arbitrary frontend users in any TYPO3 installation running femanager 8.x.
JWT token replay in AshAuthentication exposes any application using the stateless bearer-token path to full account takeover using purpose-scoped tokens. The `retrieve_from_bearer/3` helper in versions 3.10.5-4.14.2 and 5.0.0-rc.0-5.0.0-rc.13 verifies JWT signatures and rejects tokens with an `act` claim, but never validates that the token's `purpose` claim equals "user", allowing sign-in, remember-me, and TOTP-setup tokens to be silently accepted as full bearer credentials. No public exploit has been identified at time of analysis, but the attack requires only obtaining a still-valid, not-yet-exchanged sign-in token - a realistic threat surface via log leakage, referrer exposure, or intercepted magic-link delivery.
Hard-coded credentials in all versions of the Furuno FA-50 maritime AIS transponder allow any attacker with knowledge of the static credentials and access to the vessel's internal network to authenticate to the device's settings screen and alter the vessel's identification number. Modification of the AIS identification number (MMSI) carries serious maritime safety implications, enabling vessel impersonation or disruption of AIS-based collision avoidance and vessel tracking systems. Disclosed via JPCERT coordination and JVN advisory JVNVU95422936; no public exploit has been identified at time of analysis.
Configuration manipulation in the Furuno FA-50 maritime device (all versions) is possible without authentication from the vessel's internal network. The product fails to enforce access controls on its settings interface (CWE-306), allowing any attacker who gains internal network access to alter device configuration parameters. No public exploit code has been identified at time of analysis, and the device is not listed in CISA KEV, but the unauthenticated network-accessible vector and high integrity impact (CVSS 4.0: 8.7, VI:H) make this a meaningful risk in maritime operational environments.
Local privilege escalation to SYSTEM in SKYSEA Client View and SKYMEC IT Manager allows any authenticated Windows user to execute arbitrary code with SYSTEM-level privileges. The root cause is a missing authorization check (CWE-862) within one or more privileged components of these IT asset management products. No public exploit identified at time of analysis, and this vulnerability has not been listed in the CISA KEV catalog, but the low-privilege local exploitation path and full SYSTEM compromise make it a significant risk in multi-user or shared Windows environments where these products are deployed.
Privilege escalation via account takeover in InfusedWoo Pro (all versions up to and including 5.1.17) allows any authenticated subscriber-level user to hijack arbitrary WordPress accounts, including site administrators, by exploiting a missing capability check in the `ajax_iwar_preview_email()` AJAX function. The function incorrectly relies on `is_admin()` - a WordPress conditional that tests for admin-area request context rather than the requesting user's role - permitting low-privilege users to generate valid password reset links for any email address on the site. No public exploit has been identified at time of analysis, but the trivial exploitation path (subscriber-level access, no user interaction, no special configuration) makes this a high-priority remediation target for any site running the affected plugin.
Arbitrary file read in GitPython before 3.1.59 allows low-privileged remote attackers to exfiltrate sensitive files by supplying a crafted reference argument to TagReference.create(). The vulnerability arises because a positional reference parameter (e.g., '--file=/etc/passwd') bypasses the library's built-in unsafe option guard, causing git to interpret the value as a flag and return the targeted file's contents embedded in the annotated tag message. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 7.1 with high confidentiality impact reflects genuine disclosure risk in any application that exposes this code path to user-controlled input.
Credential extraction in Grav CMS before 2.0.16 allows authenticated users with page-edit permissions to read hashed passwords and two-factor authentication secrets from User objects via insufficiently filtered Twig template sandbox methods. The allow-listed offsetGet() and offsetExists() methods on User objects expose sensitive fields that should be restricted within the sandboxed template context, enabling offline password cracking and subsequent authentication bypass. No public exploit has been identified at time of analysis, but the exploit technique is straightforward for any attacker holding page-edit rights.
Origin validation bypass in Grav CMS before 2.0.16 lets remote attackers defeat the Referer-based same-origin check used by the Uri::referrer() and Pages::referrerRoute() methods. Because the check uses an unanchored str_starts_with() prefix match without a trailing delimiter, a request bearing a Referer from an attacker-controlled look-alike domain (e.g. https://example.com.attacker.tld) is accepted as same-origin, undermining CSRF/origin protections on protected routes. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Broken authorization in the Grav Login plugin before 1.0.16 lets an operator holding the api.users.write permission clear login lockout counters on admin.super accounts through the onApiUserListRowAction unlock handler, which never checks the target account's privilege tier. This strips brute-force protection from the highest-privilege accounts, enabling a lower-privileged user to set up password-guessing against super-admin credentials. Reported by VulnCheck with no public exploit identified at time of analysis and no CISA KEV listing.
Host header injection in Grav CMS before 3.9.2 allows attackers to poison outgoing invitation emails, replacing the legitimate site URL with an attacker-controlled domain in token-bearing links sent via the sendInvitationEmail() function. The vulnerability exploits a gap in Grav's existing Host header defenses: the require_trusted_host protection was applied only to password reset flows, leaving invitation emails without equivalent validation. When a poisoned invitation email is delivered and the recipient clicks the link, the one-time invitation token is transmitted to the attacker's server rather than the legitimate site. No public exploit has been identified at time of analysis, and the CVE is not listed in the CISA KEV catalog, though the reported CVSS 4.0 score of 8.7 reflects high confidentiality risk from token capture.