Authentication Bypass

Unauthenticated data disclosure in ServiceNow AI Platform instances stems from an authorization bypass (CVSS 8.7) that lets remote attackers read records they are not entitled to access. ServiceNow has already remediated its hosted instances, so exposure now concentrates on self-hosted and partner-managed deployments that have not applied the KB3159623 update or upgraded to a patched release. No public exploit code has been identified and no confirmed active exploitation (CISA KEV) has been reported, yet this remains a genuine priority for ServiceNow customers even in the absence of exploitation telemetry.

Missing authentication for a critical device function in Dell ThinOS 10 (all versions prior to SecurityAddon_2605.10.2766_T10) allows an unauthenticated remote attacker who can reach the exposed function to gain unauthorized access to it, reflected in a CVSS:3.1 base score of 8.6 under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L, where the high integrity impact dominates and confidentiality and availability effects are limited. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a genuine priority signal rather than a confirmed-exploited emergency. The main practical constraint on exploitation is network reachability: ThinOS endpoints are typically deployed inside enterprise/VDI network segments rather than exposed to the public internet, so meaningful risk arises when an attacker already has a foothold on a segment from which the affected service can be reached.

Unauthenticated network requests against unpatched ServiceNow AI Platform instances can create, modify, or delete instance data beyond what was intended, per a vendor-remediated improper access control flaw rated 8.7 under CVSS 4.0 (independent assessment: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). Impact is integrity-only - no confidentiality or availability loss is described - and ServiceNow scopes exploitation to "certain circumstances," so the flaw is not universally reachable on every default deployment and undisclosed configuration preconditions appear to gate it. ServiceNow patched hosted instances in August 2026 and shipped the update to partners and self-hosted customers, leaving residual exposure concentrated in self-hosted and partner-managed instances that have not yet applied it. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis.

Improper TLS certificate validation in Dell ThinOS 10 endpoints running SecurityAddon builds prior to 2605.10.2766_T10 lets an adjacent-network attacker bypass a protection mechanism and gain unauthorized access to client communications and credentials. The flaw is rated CVSS 8.3 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L), meaning no authentication or user interaction is required, but the attacker must already sit on the same Layer-2 segment, VLAN, or Wi-Fi network as the thin client to position themselves for a machine-in-the-middle interception. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a genuine elevated-priority issue rather than an emergency - the practical risk is driven by how flat and trusted the thin-client network segment is.

Authorization bypass in the ServiceNow AI Platform lets any authenticated user with an ordinary low-privilege account read records and data they are not entitled to, and because the flaw crosses a security scope boundary it can also enable further unintended access on resources beyond the vulnerable component. Exploitation is network-reachable and requires only a valid low-privilege session - no elevated role, no user interaction, and no special client configuration - so the practical attack path is a compromised, internal, or low-tier tenant account rather than an anonymous attacker. ServiceNow has already remediated hosted instances and distributed the update to partners and self-hosted customers, and the vendor states it is not aware of malicious exploitation; no public exploit code or CISA KEV entry was identified at time of analysis, leaving unpatched self-hosted and partner deployments as the primary exposure.

Unauthenticated remote code execution in Honeywell PD45 Industrial Printer firmware F10.19.010040 lets any network-reachable attacker upload attacker-controlled files through the web management interface and execute them as malicious files and commands. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H) reflects the complete absence of authentication or user interaction required, consistent with CWE-306 missing authentication for a critical function, so a single unauthenticated HTTP request path is enough to gain code execution on the device. Honeywell has released fixed firmware F10.22.030745; no public exploit code has been identified at time of analysis, but exposure is constrained mainly by the fact that these industrial printers typically sit on internal warehouse or manufacturing networks rather than the public internet, meaning an attacker usually needs an existing network foothold or adjacent access first.

TREK, a collaborative travel-planning web application, authorizes the DELETE /api/trips/:tripId/collab/notes/:noteId/files/:fileId endpoint against the caller-supplied tripId but then deletes the attachment resolved solely by noteId and fileId, so an authenticated user with edit rights on any single trip can permanently destroy note-file attachments belonging to other users' trips. Exploitation requires only a low-privileged authenticated account with edit access to at least one trip (CVSS:3.1/AV:N/AC:L/PR:L/UI:N, 7.1) and is made practical by sequential, enumerable identifiers, though impact is confined to integrity and availability of attachments - read paths remain trip-scoped, so no data disclosure is possible. All TREK deployments prior to 3.3.0 in a multi-user configuration are affected; no public exploit code has been identified and there is no evidence of active exploitation at time of analysis.

Authorization bypass in the ixo Blockchain x/bonds module (all versions before v8.0.0) lets any unauthenticated remote account move another user's token balance into an attacker-controlled bond by simply adding the victim's blockchain address as a verification method on a DID the attacker owns - no victim keys, signatures, consent, or prior system compromise are required. The flaw affects the MsgMakeOutcomePayment, MsgBuy, MsgSell, MsgSwap and MsgWithdrawShare handlers plus the bonds batch order processor and its EndBlocker, and the vendor advisory reports the technique was exploited on ixo mainnet (ixo-5) on 2026-06-20, with the proceeds later withdrawn and bridged off-chain. With a CVSS 9.3 rating, PR:N/UI:N reachability, and every account holding a balance in a bond-usable token in scope, this is a genuine top-priority issue rather than a high-score-but-low-real-risk case.

Decepticon versions prior to 1.1.17 fail to neutralize ChatML-style special-token literals (e.g. <|im_start|>, <|eot_id|>, <start_of_turn>, [INST], <<SYS>>) embedded in web crawl results returned by agent reconnaissance, so an attacker who plants such a string on a crawled page can forge an authoritative operator turn that the model acts on, bypassing Decepticon's agent guardrails and achieving arbitrary command execution inside the Kali Linux sandbox. Exploitation is unauthenticated (PR:N) but conditional: it requires the BYOK deployment model with a self-hosted or OpenAI-compatible backend (vLLM, SGLang, TGI, Ollama, LM Studio, text-generation-webui) whose tokenizer preserves special-token IDs, and the operator must actually crawl attacker-controlled or attacker-compromised content - both normal for a red-team tool. Deployments using hosted providers such as OpenAI or Anthropic are not vulnerable because those strip special tokens server-side; no public exploit code has been identified at time of analysis, and the advisory ships with a vendor fix in 1.1.17.

MFA bypass in ZITADEL Login V2 (versions 4.0.0 through 4.16.0) lets an attacker who already holds a victim's valid first-factor password complete an OIDC or SAML login to a customer application without ever satisfying the user's voluntarily enrolled TOTP, OTP, or U2F second factor. The browser session created after password verification is reused when the login flow is abandoned at the MFA step and restarted, and the pre-fix session-validity check only demanded MFA when the organization had Force MFA or Force MFA for local users enabled. The assessed CVSS 3.1 vector is 8.2 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) reflecting the requirement of the victim's password; Login V1, the ZITADEL Console, Management/Admin APIs, and user self-management are unaffected, a vendor patch is available as 4.16.1, and no public exploit code has been identified at time of analysis.

ZITADEL Actions V1 on affected releases (3.0.0 through pre-3.4.13 and the 4.x line before 4.16.1) fails to restrict the goja Node-compatible require() registry, so an authenticated organization Action author holding ORG_OWNER, org.action.write, and org.flow.write can execute JavaScript at OIDC, SAML, or login-flow triggers and load arbitrary files readable by the ZITADEL server process. This exposes mounted configuration and secrets - notably credentials referenced by ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH and ZITADEL_FIRSTINSTANCE_MACHINEKEYPATH - and recovered bootstrap credentials can let an organization administrator escalate to instance administrator; host command execution is not established. CVSS 3.1 base score is 8.7 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N), reflecting a high-privilege prerequisite; no public exploit code has been identified at time of analysis, and the issue is patched in 3.4.13 and 4.16.1.

Unauthenticated MCP tool invocation in DBHub versions prior to 0.22.5 allows a malicious website to reach the HTTP transport endpoint and dispatch database tool calls against connected Postgres, MySQL, SQL Server, Oracle, MariaDB, or SQLite databases, because the server's Origin-equals-Host check is defeated by DNS rebinding. The flaw applies only when DBHub is launched in the non-default HTTP transport mode (for example --transport http --port 8080); the default stdio transport is unaffected, and exploitation requires a victim's browser to load attacker-controlled content and successfully complete the rebind window, per the independent assessment. No public exploit has been identified at time of analysis, and while the CVSS 4.0 vector scores 9.3, the assessed real-world severity is lower (CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L), with impact bounded by DBHub's configured tool permissions and database credentials - read-only configurations limit exposure to disclosure.

Authentication bypass in Python Social Auth (social-core) versions prior to 5.0.0 allows unauthenticated remote attackers to impersonate any VK user when an application uses the vk-app backend, as the backend skips signature verification if the auth_key parameter is omitted. An attacker can forge callback fields such as viewer_id, access_token, api_id, and api_result to authenticate as an arbitrary VK identity, potentially taking over accounts in the target application. The vulnerability is fixed in version 5.0.0, and no public exploit code or active exploitation has been identified at this time.

An authorization gap in OpenWA before 0.23.5 allows a low-privilege VIEWER API key to receive the `session.qr` pairing event over the /events WebSocket gateway, even though the equivalent REST endpoint GET /api/sessions/{sessionId}/qr enforces the OPERATOR role. When a session is in the waiting-to-be-paired state, the leaked QR code lets the key holder link an external device to the linked WhatsApp account, after which they can read and send messages outside OpenWA and outside its audit trail. Exploitation is authenticated (CVSS PR:L) and gated by a transient pairing window that drives the high attack-complexity rating (AC:H); no public exploit code identified at time of analysis. Vendor-released patch: 0.23.5.

Multi-factor authentication bypass in authentik (goauthentik) allows an attacker who already knows a target user's password to redirect the email authenticator's one-time code to an address they control, complete enrollment of the email factor as the victim, and obtain a session with access to any single sign-on applications behind the account. Only deployments that enroll the email authenticator during an authentication or enrollment flow are affected, and only where the target has not yet enrolled the email factor; other authenticator types are unaffected. Rated 8.9 by the vendor (independent re-assessment scores it slightly lower on availability impact), there is no public exploit identified at time of analysis and no CISA KEV listing, but the precondition of prior credential knowledge makes this a high-value account-takeover primitive for attackers who phish or reuse passwords. Fixed in 2026.2.7, 2026.5.7, and 2026.8.2.

Authentication bypass in authentik's SAML Source lets an unauthenticated attacker who holds any validly-signed, unexpired SAML assertion from a trusted identity provider log in as the user named in that assertion, because releases before 2026.2.7, 2026.5.7, and 2026.8.2 never verify that the assertion was issued for that Source (no audience, Destination, or SubjectConfirmationData Recipient binding) and never record assertions already accepted, permitting replay. Attackers must therefore obtain an assertion minted for a different service provider or reuse a previously captured assertion; no authentik-side credentials or user interaction are required (PR:N/UI:N), which is why the issue scores 7.4 despite the High attack complexity driven by that prerequisite. Only SAML Sources are affected - SAML Providers and other Source types are explicitly not - and no public exploit code was identified at time of analysis, with no CISA KEV listing.

Door access control readers operated by Norwegian Cruise Line grant entry based solely on the static 7-byte UID of an NTAG212 NFC credential, so anyone who can read that UID can reproduce a working key to the ship's doors. Because the UID is a manufacturer serial number transmitted in the clear during every read and the NTAG212 has no challenge-response capability, the weakness is intrinsic to the access-control design and present by default rather than a toggled configuration, affecting every credential and reader pair deployed in this scheme. NVD rates the issue 7.5, but the supplied vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) is internally inconsistent with the physical nature of the attack; our independent assessment re-scores it as CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, reflecting proximity-based exploitation with full integrity impact on door state. Exploitation requires close-range skimming of a victim's NTAG212 chip (typically a few centimetres) followed by physically presenting the cloned credential at a reader, and no public exploit code has been identified at time of analysis.

Stored social and enterprise SSO provider access tokens can be retrieved from Logto's Account API by a low-trust application that holds only an `openid`-scoped same-user access token, because the third-party token handlers in packages/core/src/routes/account/third-party-tokens.ts authenticate the caller but omit the `identities` scope check that protects neighboring identity-detail endpoints. Logto deployments from 1.31.0 through 1.41.x are affected; version 1.42.0 adds the missing scope gate to the GET /api/my-account/identities/{target}/access-token, GET /api/my-account/sso-identities/{connectorId}/access-token, and related PUT routes. No public exploit code was identified at time of analysis, and exploitation is constrained: federated token-set storage must be enabled in the tenant and the victim must already have linked a supported social or enterprise SSO connector, with downstream impact bounded by the scopes granted to the leaked provider token.

Unauthenticated attackers can bypass TOTP-based two-factor authentication in phpMyFAQ 3.2.0 through 4.1.5 and take over any 2FA-enabled account, including administrator accounts, by submitting a victim's numeric user ID together with a valid or brute-forced six-digit code to the public 2FA verification flow in index.php without ever supplying the account password. The flaw rates CVSS 3.1 base 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H); the high attack complexity reflects the cost of guessing a TOTP code inside its rolling validity window, while the practical enabler pre-patch is the complete absence of any failed-attempt limit and the fact that token verification was never bound to a prior password-authenticated session. There is no public exploit identified at time of analysis and no CISA KEV listing, but exploitation requires only that the targeted account have 2FA enabled, making the exposure significant for deployments that adopted TOTP. Vendor-released patch: 4.1.6.

Path traversal in the pulpcore content upload API allows an authenticated user holding only low-privilege file-repository permissions to read arbitrary files accessible to the Pulp server process by submitting a crafted 'file:' URL through the 'file_url' parameter, which is dispatched to the file downloader despite an intended scheme check. Baseline impact is confidentiality loss on the Pulp host; in deployments that include Pulp Container the same flaw escalates to theft of the container registry token signing private key, enabling forged bearer tokens and unauthorized access to every private container repository in the registry. Downstream products embedding pulpcore are affected, including Red Hat Satellite 6, Red Hat Ansible Automation Platform 2, and Red Hat Update Infrastructure 4/5. There is no public exploit identified at time of analysis, and EPSS data was not provided; Red Hat tracks the issue under advisory https://access.redhat.com/security/cve/CVE-2026-90959.

Authentication bypass in OpenStack Zaqar before 22.0.2 allows an unauthenticated remote attacker who knows a target project's UUID to send a request carrying an empty URL-Signature header and defeat both Keystone authentication and pre-signed URL verification, gaining the ability to read, enumerate, create, and delete that project's queues, messages, claims, and subscriptions. Only deployments using the WSGI transport with an authentication strategy configured are exposed; the websocket transport is explicitly not affected, and escalation to administrative operations such as managing pools and flavors additionally requires an admin_mode deployment in which the attacker asserts an administrative role. The issue is rated CVSS 4.0 base 9.2, while independent assessment scores it CVSS 3.1 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) with the AC:H component reflecting the prerequisite knowledge of the victim project UUID; no public exploit code or confirmed active exploitation was identified at time of analysis.

Authentication bypass in PortSwigger Burp Suite DAST (formerly Burp Suite Enterprise Edition) before 2026.8 allows unauthenticated remote attackers to reach restricted functionality through an alternate path or channel, yielding high confidentiality, integrity and availability impact on the scanning platform. The CVSS 4.0 base score of 9.2 and CISA SSVC technical impact rating of 'total' reflect complete compromise of the affected management interface, although an undisclosed attack precondition (AT:P) must be satisfied and the product is normally deployed on segmented internal networks rather than being internet-facing. No public exploit identified at time of analysis, and SSVC exploitation is rated 'none', so this is a serious but not currently imminent priority. Authentication requirements are confirmed unauthenticated by the CVSS vector (PR:N, UI:N). Vendor-released patch: 2026.8.

Unauthenticated arbitrary file read, write, append, and delete in Rejetto HFS2 up to and including 2.4.0 allows remote attackers to compromise the confidentiality, integrity, and availability of the host filesystem. The vulnerability arises because the template engine's macro dispatcher performs no authorization check and the path resolver fails to confine absolute paths to the shared folder, letting attackers manipulate macros to access files anywhere the HFS service account has permissions. Public exploit code exists, and exploitation works against default configurations; the legacy 2.x branch is affected, while HFS 3.x is a separate codebase.

Privilege escalation in Rapid7 Velociraptor allows an authenticated user holding only the 'investigator' role to execute arbitrary VQL statements with administrator privileges on the Velociraptor server by populating the internal 'compiled_collector_args' field when submitting a hunt-creation/scheduling API request. Because the server accepts this internal field from the caller, the attacker-supplied pre-compiled VQL is trusted and the ACL checks that normally gate artifact compilation are skipped (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Exploitation requires a valid investigator-or-higher account that can schedule hunts, making this an insider/privilege-escalation path rather than an unauthenticated remote compromise; no public exploit identified at time of analysis, and no confirmed actively exploited (CISA KEV) status was provided. The vendor advisory is published at https://docs.velociraptor.app/announcements/advisories/cve-2026-19072/.

Authentication bypass in TÜBİTAK ULAKBİM's UlakPDF allows remote unauthenticated attackers to reach functionality or data that should be protected by authorization checks, affecting builds through 09092026. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.4) indicates exploitation needs no credentials and no user interaction, but the High attack complexity means a non-trivial precondition - such as a specific request/parameter combination, a valid resource identifier, or a particular application state that causes the authorization decision to be evaluated incorrectly (CWE-863) - must be satisfied, which reduces reliability. Risk assessment: this is a genuinely notable authorization flaw but not a top-tier emergency; no confirmed actively exploited (CISA KEV) status and no public exploit identified at time of analysis, and the product's limited real-world footprint narrows targeting opportunity.

Improper authentication in Delta Electronics DIAEnergie before 1.11.00.022 allows authentication bypass, enabling remote attackers to reach protected functionality without valid credentials. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires no authentication, no user interaction, and no non-default configuration - only network reachability to the DIAEnergie service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the practical exposure is limited chiefly by the product's footprint, as DIAEnergie is a niche ICS energy-management platform typically deployed on operational or enterprise networks rather than the public internet.

An authentication bypass in the EthPress - Web3 Login WordPress plugin, affecting all versions up to and including 2.3.5, allows unauthenticated remote attackers to log in as any WordPress user with a linked Ethereum wallet address - including administrators - simply by supplying that user's public wallet address together with an arbitrary, well-formed (but invalid) signature, resulting in full site takeover. The root cause is a missing return statement in verify_login() that lets execution fall through to the cookie-setting login routine even when signature verification fails; no public exploit code has been identified at time of analysis, and the assessment rates it 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), with the 'high' attack complexity reflecting the need to discover a valid linked wallet address rather than any authentication barrier. Because exploitation is unauthenticated and requires no user interaction, any site where at least one account (especially an administrator) has linked a wallet should be treated as exposed until patched or the plugin is disabled.

TLS client-authentication bypass in the RabbitMQ trust-store plugin lets a remote unauthenticated attacker whose forged self-signed certificate carries the issuer DN and serial number of any whitelisted certificate pass mutual-TLS authentication. Only deployments that have the rabbitmq_trust_store plugin enabled and wired in as the TLS verify_fun for a client-certificate listener are affected, and an attacker must first learn or guess at least one whitelisted certificate's {Issuer, Serial} pair, which is non-secret and is exposed by the plugin's list command, logs, or any copy of the certificate. All RabbitMQ server releases prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 are vulnerable; vendor-released patches exist in those versions, and no public exploit identified at time of analysis.

Account takeover in Klever-Go's KleverUpdateAccountPermission built-in (all versions prior to 1.7.20) allows an attacker-controlled smart contract to replace a victim account's entire permission set without any victim key or signature. The handler authorizes updates using the attacker-supplied vmInput.RecipientAddr instead of the authenticated vmInput.CallerAddr, and because the default self-signer created by createDefaultOwnerPermission satisfies the contractHasValidPermission check, a contract can name any permissioned victim as recipient and install attacker-supplied Owner permissions - enabling asset theft or permanent lockout of the victim. The CVSS 4.0 score is 8.7 with a low-privilege vector (PR:L), reflecting that the attacker must be able to deploy or control a contract that can issue an indirect built-in call; accounts without stored permissions and the native transaction path are not affected. Exploitation requires no user interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis; this is nevertheless a genuine high-priority vulnerability given its unauthenticated-from-the-victim's-perspective account takeover impact on a production blockchain.

Unauthenticated attackers can overwrite or hijack other users' in-progress multi-page or save-for-later submissions in the Craft CMS Formie plugin by enumerating sequential submission IDs against the anonymous formie/submissions/submit endpoint, which trusted a client-supplied submissionId with no session binding, ownership check, or edit-token validation (CWE-639, CVSS 3.1 base 8.2, vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N, so no authentication or user interaction is required). Affected installations are Formie 3.0.0 through 3.1.30 on Craft 5 and all versions before 2.2.23 on Craft 4; completed submissions are unaffected because the vulnerable code path only loads records with isIncomplete=true, meaning exposure requires the site to actually use multi-page forms or save-for-later. Exploitation status: no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV; vendor-released patches exist (3.1.31 for Craft 5, 2.2.23 for Craft 4).

Missing authorization in Formie's IntegrationsController::actionFormSettings control panel action lets any authenticated user (no integration permission required) override outbound host properties such as apiUrl on an already-configured integration, causing the server to send stored API keys or OAuth tokens to an attacker-controlled or internal host and return the remote response in the JSON body. This is a non-blind SSRF combined with credential exfiltration affecting verbb/formie versions before 2.2.23 (Craft 4) and 3.0.0 through 3.1.30 (Craft 5); patched releases are 2.2.23 and 3.1.31. Authentication with any level of access is required, so exposure is greatest on sites permitting low-privileged or front-end/member authentication (including public self-registration), and a CRM, email-marketing, or webhook integration must already be configured with stored credentials for exfiltration to be meaningful; no public exploit code was identified at time of analysis, and the flaw is an incomplete remediation of GHSA-cvpc-hccg-wmw4, whose 3.1.28 permission gate omitted this action.

Unauthenticated remote attackers can read protected data from WordPress sites running the Tangible Loops & Logic plugin at version 4.2.4 or earlier, because the plugin fails to enforce proper authorization on a reachable feature (CWE-862 broken access control). The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5 HIGH) confirms the flaw is network-reachable with no authentication, no privileges, and no user interaction, and the impact is limited to confidentiality - no modification or availability effect is possible. Exploitation requires only that the plugin be installed and active; there is no public exploit identified at time of analysis, and exposure is bounded because the plugin is a niche, developer-oriented templating tool rather than a widely deployed one.

Unauthenticated broken access control in the Online Booking & Scheduling Calendar for WordPress by vcita plugin (slug meeting-scheduler-by-vcita) through version 4.6.0 lets remote attackers reach protected plugin functionality without logging in and use it to modify data or settings, with the assessed vector (AV:N/AC:L/PR:N/UI:N) showing no privileges or user interaction required. Impact is limited to integrity (C:N/I:H/A:N) - booking, scheduler, or configuration data can be altered, while confidentiality and availability are not reported as affected. No CISA KEV entry is present and no public exploit identified at time of analysis; the advisory does not disclose the specific endpoint or action, which currently raises the effort of exploitation even though the vulnerability is remotely reachable.

FileMaker Server deployments that expose the Web Publishing Engine can be driven into serving the XML Web Publishing interface even when an administrator has explicitly disabled the Custom Web Publishing with XML option, because a request-supplied extended privilege header is trusted without validating it against the configured publishing state. The bypass carries a CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), so unauthenticated remote attackers reach high confidentiality and integrity impact with no user interaction, but only against servers where the Web Publishing Engine is actually deployed and network-reachable; installations that do not run Web Publishing are unaffected. No public exploit code and no confirmed active exploitation have been identified at time of analysis (EPSS 0.15%, 3rd percentile; CISA SSVC exploitation: none), and Claris remediated the issue in FileMaker Server 26.0.3.

Local privilege escalation in Claris FileMaker Pro for Windows lets a low-privileged local user drop a malicious DLL into the directory used by the product's installer and thereby execute arbitrary code in the administrator context once a privileged user runs that installer. Only Windows installer builds prior to 26.0.3 are affected (EUVD records the range as 0 through 26.0.3); the installed application at runtime is not impacted. Exploitation requires local host access plus an admin-initiated installer run (CVSS:3.1/AV:L/AC:L/PR:L/UI:R), so it is neither remotely reachable nor automatable - CISA's SSVC rates Exploitation as none and Automatable as no - and no public exploit code exists, with EPSS at 0.15% (3rd percentile) reflecting the narrow local-use precondition. This is a local privilege-escalation issue with realistic but constrained risk; a vendor fix is available.

Unauthorized message injection in the Moquette lightweight Java MQTT broker affects all releases prior to 0.18.1: PostOffice.publishWill publishes a client's Last-Will Testament without running the canWrite authorization and reserved-topic checks that gate a normal PUBLISH, so remote unauthenticated attackers (CVSS vector PR:N) can register a Will on a topic they are not allowed to write and have the broker deliver that message to subscribers when the connection is abruptly dropped. This is an integrity-only flaw (C:N/I:H/A:N) whose real-world severity depends on how sensitive the restricted topic is - for example device command-and-control channels - and exploitation requires that an ACL or IAuthorizatorPolicy actually restricts writes to the targeted topic; vendors score it 8.7 (CVSS 4.0). Publicly available exploit code exists (the upstream advisory ships source-level PoCs, including a wildcard-ACL injection proof), but there is no indication in the supplied data of confirmed active exploitation (CISA KEV), and no patch is available other than upgrading to vendor-released version 0.18.1.

Missing authentication for a critical function in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift allows a remote, unauthenticated attacker to read sensitive information and modify system configurations on an affected deployment. With CVSS 7.3 (AV:N/AC:L/PR:N/UI:N), no credentials, user interaction, or non-default configuration are required, so any network-reachable FTM instance with the vulnerable function exposed is at risk; exploitation is limited chiefly by FTM's narrow enterprise-payments install base and whether that endpoint is actually reachable. No public exploit code has been identified at time of analysis, and IBM has released a patch.

Message-filtering bypass in xdg-dbus-proxy before 0.1.9 lets a malicious or already-compromised sandboxed application - most notably a Flatpak app, but also deployments under frameworks such as Firejail - escape its confinement and execute arbitrary code on the host by attaching a forged reply serial number to non-reply D-Bus messages. The flaw carries a CVSS 4.0 base score of 8.7 (AV:N/AC:L/PR:N/UI:P, with high confidentiality, integrity and availability impact scoped to the sandbox-escape boundary) and is rated a genuine high-priority sandbox-escape issue rather than a CVSS-inflated paper risk; the practical precondition is that an attacker must first get code running inside a sandbox that routes its session bus through the vulnerable proxy, typically by tricking a user into installing or launching a hostile or trojanized app. No confirmed active exploitation (CISA KEV) and no public exploit code were identified at time of analysis; vendor-released patch: 0.1.9.

Missing authentication for a critical function in Dell Secure Connect Gateway (SCG) Policy Manager before version 5.34.00.16 allows remote attackers to reach functionality that should require a credential check, resulting in unauthorized access with high confidentiality and integrity impact. The assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (7.4) confirms no privileges and no user interaction are required, while the high attack-complexity rating indicates a non-trivial precondition must be satisfied rather than a guaranteed single-request compromise. Real-world risk is bounded by exposure: the Policy Manager interface must be network-reachable, and SCG is a specialized enterprise gateway typically deployed in restricted management networks; no public exploit was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).

Privilege escalation in ZohoCorp ManageEngine Applications Manager 182000 and earlier allows a holder of an authenticated low-privileged account to read an administrator's API key and then replay that key to carry out administrator-level actions over the network. Exploitation requires a valid low-privilege login (CVSS vector PR:L) on a vulnerable instance, but needs no user interaction and no special configuration, and successful abuse grants full high-integrity, high-confidentiality control of the application. No public exploit code or confirmed active exploitation was identified at time of analysis; the primary limiting factor is the mandatory pre-existing low-privilege account, which is why this rates as a genuine high-priority flaw rather than a benign high-CVSS artifact.

Broken scope enforcement in ZohoCorp ManageEngine Applications Manager (versions 182200 and below) lets an authenticated, low-privileged user trigger administrator-configured MBean actions against monitors that lie outside that user's assigned scope, resulting in high integrity impact with limited confidentiality and availability effects (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L, 7.6 HIGH). Exploitation requires a valid low-privileged Applications Manager account and the prior existence of administrator-configured MBean actions on the target instance; no user interaction is needed, and authentication requirements are confirmed as authenticated (PR:L) by the published vector. No public exploit code was identified and the flaw is not listed in CISA KEV, so there is no public exploit identified at time of analysis; the absence of a public exploit and the PR:L prerequisite are the main factors limiting immediate mass exploitation.

WatchGuard AuthPoint Gateway contains a missing authentication check in its LDAP Sync first-factor authentication that allows unauthenticated remote attackers to bypass single-factor password verification under non-default conditions. Exploitation requires the gateway to be configured with LDAP Sync as the first-factor method and involves some user interaction, but default deployments are unaffected; only the first factor is bypassed, so any additional MFA factors still apply and prevent full account compromise. No public exploit has been identified at time of analysis, and the vendor (WatchGuard PSIRT) rates this as CVSS 4.0 7.4 High with vector AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N.

Authentication bypass in Zoho ManageEngine OpManager 12.8.710 and earlier allows an attacker reaching the web console to skip an authentication control when the optional Application Manager Plugin is enabled, with high impact to confidentiality, integrity, and availability (CVSS 8.8). Only instances with that specific non-default add-on are exposed; deployments without the plugin are not affected. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:L/UI:N) combined with the CWE-306 missing-authentication root cause means the precondition is worth treating as near-unauthenticated until the vendor advisory clarifies it.

Broken access control in ZohoCorp ManageEngine OpManager and ManageEngine Firewall Analyzer 12.8.710 and earlier lets an authenticated low-privilege console user create alert notifications for firewalls that fall outside their assigned scope. The weakness (CWE-639, authorization bypass through a user-controlled key) only matters in deployments that actually enforce separate scopes - multi-user, multi-team, or multi-tenant setups - since a flat single-administrator installation has no boundary to cross. Exploitation requires a valid, even minimal, console account (CVSS vector PR:L, no user interaction) and there is no public exploit identified at time of analysis: no CISA KEV listing, no EPSS score, and no POC were provided.

Broken access control in ZohoCorp ManageEngine OpManager and Firewall Analyzer 12.8.710 and below allows an authenticated low-privilege user to modify Change Management report schedule configurations for firewalls outside their assigned scope. The vendor CVSS 3.1 vector is 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), but independent assessment adjusts confidentiality to Low (C:L/I:L), because impact is limited to cross-scope report scheduling data and requires a pre-existing low-privilege account plus a multi-scope/RBAC deployment. No public exploit or CISA KEV listing was identified at time of analysis.

Authentication can succeed when it should have been rejected in Apache Tomcat deployments that use CLIENT_CERT (mutual-TLS) authentication with soft fail disabled, allowing network attackers to reach resources that the mutual-TLS configuration was meant to protect. The affected range is broad - 9.0.92 through 9.0.121, 10.1.22 through 10.1.59, and 11.0.0-M14 through 11.0.25 - but the flaw is gated on two non-default conditions (the CLIENT_CERT authenticator in use and soft fail turned off) and, per the vendor, only manifests in some scenarios, so it is not universally reproducible even on correctly configured vulnerable instances. No public exploit code has been identified at time of analysis, and no evidence of active exploitation is present; the attacker needs network reachability to the mTLS-protected listener.

Authentication bypass in Apache Tomcat allows unauthenticated remote attackers to reach WebSocket endpoints that are supposed to be protected by container-managed security constraints, simply by referencing the endpoint under an alternate name so the constraint is never matched. Exploitation requires only that the application expose one or more WebSocket endpoints and rely on container-level (web.xml security-constraint) authentication or authorization rules to guard them; no credentials, no user interaction, and no non-default configuration beyond that are needed, and per the CVSS vector (PR:N) the attack is unauthenticated and network-reachable. Affected lines are Tomcat 11.0.0-M1 through 11.0.25, 10.1.0-M1 through 10.1.59, 9.0.0.M1 through 9.0.121, plus end-of-support 8.5.0-8.5.100 and 7.0.43-7.0.109; no public exploit code has been identified at time of analysis and Apache has released fixed versions 11.0.26, 10.1.60 and 9.0.122.

Cross-application authentication realm leakage in Apache Tomcat's Jakarta Authentication integration causes requests to be validated against the realm established by whichever co-hosted web application authenticated first, breaking per-application authentication boundaries. The flaw (CWE-287, improper authentication) affects Tomcat 11.0.0-M1 through 11.0.25, 10.1.0-M1 through 10.1.59, and 9.0.0.M4 through 9.0.121, plus end-of-life 8.5.0 through 8.5.100. Exploitation is gated by a non-default deployment - SimpleAuthConfigProvider as the default Jakarta Authentication provider with two or more applications sharing it - and the independent assessment rates the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L (unauthenticated, high attack complexity, low impact); no public exploit identified at time of analysis, the issue is not in CISA KEV, and the vulnerable configuration is not Tomcat's default.

Unauthenticated code installation on the Reachy Mini robot daemon (Pollen Robotics) allows any host on the same LAN to execute arbitrary Python code on the robot by posting an attacker-controlled Hugging Face Space to POST /apps/install. The endpoint is reachable without credentials because the wireless variant of the daemon binds to 0.0.0.0, and the handler's dependency chain (Depends(get_app_manager)) never performs an authorization check; the chosen Space's build/setup code is then executed by the daemon via uv or pip. Affected are all Reachy Mini units before the vendor's v1.11.0 patched release (CPE cpe:2.3:a:pollen_robotics:reachy_mini:*); there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), though the attacker prerequisites are trivial for anyone sharing the robot's Wi-Fi network. Scoring is AV:A/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact, consistent with full compromise of the robot host.

Every desktop application generated by Pake inherits two upstream template defaults that together hand native IPC functionality to untrusted web content, allowing scripts served from any HTTPS origin to invoke the application's own native commands, including download_file. The root cause is a wildcard Tauri capability ("remote": { "urls": ["https://*.*"] } in src-tauri/capabilities/default.json) paired with "withGlobalTauri": true in src-tauri/tauri.conf.json, which places window.__TAURI__.core.invoke() within reach of ordinary page JavaScript; because Tauri's access control list only validates plugin: commands and not commands registered by the application itself via generate_handler!, no permission entry is required to call them. Exploitation is unauthenticated per the assessed vector (PR:N) but requires user interaction (UI:R) - the victim must run the generated app and attacker-controlled JavaScript must execute inside it, whether directly or through third-party analytics, advertising, or a compromised CDN loaded by the wrapped site. Chained with the path traversal tracked separately as CVE-2026-82635, this escalates to arbitrary file write and persistent code execution; no public exploit identified at time of analysis, and the issue is fixed in Pake V3.17.0.

Unauthenticated remote attackers can reach internal Apache Doris Frontend (FE) metadata service endpoints in affected 2.0.x through 4.1.x releases and read sensitive cluster information, because those endpoints authenticate callers using client-supplied node information rather than verifying the requesting party (CWE-287, header trust). Exploitation is gated by deployment: it only succeeds 'under certain network configurations' where the FE meta interfaces are reachable by the attacker, so clusters with the FE meta service kept off attacker-reachable networks are not exposed. The vulnerability is rated CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) with confidentiality-only impact - no integrity or availability effect - and no public exploit has been identified at time of analysis; there is no CISA KEV listing. Vendor-released patches exist in Apache Doris 4.0.8 and 4.1.4.

Authenticated users holding only a Subscriber-level account can abuse the field-management AJAX action in the WC Fields Factory WordPress plugin before 4.1.11 to create, modify, or delete arbitrary post meta on any post - including WooCommerce products they do not own - and to rewrite stored pricing rules so that a product checks out at a reduced price. The root cause is a missing authorization check (CWE-862) on a field-management endpoint, rated CVSS 8.1 by NVD (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N; our assessment reaches the same 8.1 base score but caps confidentiality at Low: C:L/I:H/A:N), and no public exploit code or CISA KEV listing was identified at time of analysis. Exploitation requires only that the site runs a vulnerable version of the plugin alongside WooCommerce and that the attacker can obtain a basic account, which is trivially satisfied where WooCommerce customer self-registration is enabled.

Identity-assertion confusion in the WP OAuth Server (Login with WordPress) plugin before 6.4.0 allows a user holding a Subscriber-level account or above to obtain a validly signed OpenID Connect identity assertion belonging to another user - including an administrator - and use it to authenticate as that victim at any relying application that trusts the WordPress site as an SSO identity provider. The plugin fails to bind the assertion it issues to the authorization grant being exchanged, instead returning the assertion of whichever user authenticated most recently, so exploitation depends on a race/interaction window (assessed vector AC:H, UI:R) in which the targeted higher-privileged user is the most recently authenticated identity. No public exploit code was identified at time of analysis, and there is no CISA KEV entry indicating active exploitation.

Incorrect authorization handling (CWE-863) in Google Chrome before 154.0.8037.57 allows remote, unauthenticated attackers to bypass intended authorization checks by convincing a user to load attacker-controlled web content, resulting in high confidentiality and integrity impact with no availability impact (CVSS 3.1 base 8.1, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). Because exploitation hinges on the UI:R component, it is not a fully drive-by condition - the victim must visit a malicious or compromised page while running an unpatched build, and the requirement for that user action is the main limiting factor. Exploitation status at time of analysis is that no public exploit code has been identified, and CISA KEV does not list this CVE; EPSS is low at 0.22% (12th percentile), suggesting limited observed exploitation pressure despite the high base score. Vendor-released patch: 154.0.8037.57.

An authorization-bypass flaw in Google Chrome desktop builds prior to 154.0.8037.57 lets remote attackers escape a security boundary by having the victim load crafted web content in the browser. Successful exploitation crosses a sandbox boundary (S:C) and can compromise confidentiality, integrity and availability of the affected system, but the CVSS vector (AC:H, UI:R) means the attacker must satisfy specific timing or memory-state conditions and the user must actively visit or interact with the malicious page. No confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and a vendor patch is available, so prioritization should reflect a high-severity but hard-to-trigger client-side issue rather than an imminent mass-exploitation event.

Missing authorization enforcement in Google Chrome builds earlier than 154.0.8037.57 (classified CWE-862 and tagged as an authentication bypass) lets an attacker defeat an access-control decision in the browser, with the impact scored as high confidentiality and high integrity loss (CVSS 3.1 base 8.1, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). The flaw is network-delivered and requires no authentication or prior privileges, but exploitation is not silent: the victim must navigate to or render attacker-controlled web content (UI:R), which keeps the practical attack path dependent on user browsing behavior rather than on a remotely reachable service. Google has shipped the fix in Chrome 154.0.8037.57 and the issue is tracked as ENISA EUVD-2026-89222 / Chromium issue 540265100; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so there is no confirmed active exploitation.

Authentication bypass in Google Chrome prior to 154.0.8037.57 allows an attacker with local access to the machine to slip past an authorization check in a browser component, yielding high confidentiality, integrity, and availability impact. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N) means no privileges and no user interaction are needed once local access exists, so the realistic prerequisite is the ability to execute or otherwise interact with the vulnerable Chrome component on the host rather than reaching it over the network; a purely remote, unauthenticated web-based attack is not supported by the available data. Exploitation signals are currently weak and non-urgent: EPSS is only 0.22% (12th percentile), there is no CISA KEV listing, and no public exploit code was identified at time of analysis, while the vendor has shipped a fixed build. Note that the affected feature or component is not named in the available data because no vendor description was published, so the exact local precondition should be confirmed against the Chrome release advisory.

A missing-authorization flaw (CWE-862) in Google Chrome desktop builds prior to 154.0.8037.57 can be triggered by an unauthenticated local attacker with no user interaction, and the assessed CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) rates confidentiality, integrity and availability impact as high, consistent with the 'Authentication Bypass' tagging applied by the reporting vendor. The local attack vector and absence of a user-interaction requirement mean the attacker must already have some form of local execution context on the target host, which sharply constrains mass remote exploitation; no public exploit code has been identified at time of analysis and EPSS is low at 0.24% (13th percentile). Exploitation is limited to unpatched builds and is fully mitigated by the vendor-released fix in Chrome 154.0.8037.57, so this should be handled as a moderate-priority patch rather than an emergency, though the 8.4 score and high CIA impact still warrant prompt update cycles.

Remote, unauthenticated attackers who can reach the application endpoints of IBM Financial Transaction Manager (FTM) for Red Hat OpenShift can perform unauthorized actions because the software fails to properly authenticate requests and subsequently omits authorization checks. Affected deployments are those running versions 4.0.6.0 through 4.0.10.0 Interim Fix 064, including Operator 4.4.6+20260807.081800 and the 4.0.6.0 Refresh build, per the EUVD version list. Impact is confined to integrity - attackers can trigger unauthorized operations or modify data, but there is no confidentiality or availability consequence per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), and there is no public exploit identified at time of analysis, with EPSS at only 0.60% (47th percentile) and CISA SSVC recording no observed exploitation.

Hard-coded credentials embedded in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift let a local, low-privileged attacker - someone with at least an account, shell, pod, or container context in the deployment - reach a privileged FTM interface or data store and both read sensitive information and modify transaction data. Impacted releases include FTM for OpenShift 4.0.6.0 through the 4.0.6.0.0.6.0 Refresh (Operator 4.4.6+20260807.081800), plus 4.0.7.0, 4.0.8.0, 4.0.9.0, and 4.0.10.0 Interim Fix 064. The issue is not remotely exploitable (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 7.1), is not listed in CISA KEV, has no public exploit identified at time of analysis, and carries an EPSS of 0.14% (3rd percentile), keeping realistic risk moderate and largely confined to insiders or attackers who already hold a local foothold.

IBM Financial Transaction Manager (FTM) for Red Hat OpenShift can be driven into performing unauthorized actions by remote, unauthenticated attackers because its HTTP method-based security constraints do not cover every verb, allowing requests that fall outside the configured constraint set to reach protected functions. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 9.1) and CWE-306 assignment confirm a low-complexity, network-reachable missing-authentication defect with high confidentiality and integrity impact and no availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and IBM has published a patch advisory for the affected product line.

Authenticated users of Unleash (the open-source feature management platform) can bypass project-scoped authorization and reach configuration data and write operations belonging to projects and environments they should not control, due to a cluster of broken-access-control defects fixed in version 8.0.3. The most serious is a missing `await` on an async permission check in POST /api/admin/segments/strategies, which lets any authenticated account with an admin-API session modify segment assignments on any strategy in any project; four additional cross-project IDOR issues (CWE-639) expose variant configurations, strategy configurations, environment information, and permit tag modification across project boundaries. Exploitation requires only a valid Unleash account at any privilege level with network reach to the admin API - no anonymous access and no administrator role - so practical exposure is concentrated in multi-project or multi-tenant deployments where authenticated users are not uniformly trusted with every project; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited.

Vaultwarden through 1.37.3 permits authenticated users who hold a revoked or not-yet-confirmed organization membership to retain read, write, delete, and attachment access to organization ciphers, because three cipher access-restriction queries omit a membership status filter. Exploitation requires a Vaultwarden account with a prior (revoked) or pending membership linkage to the target organization and only affects deployments that use collection- or group-based cipher sharing, so a wholly external user with no org relationship cannot exploit it; no public exploit code was identified at time of analysis, and the issue is fixed upstream via PR #7554 (upgrade past 1.37.3).

Missing authorization in the Kaneo bulk task endpoint (PATCH /api/task/bulk) allows any authenticated workspace member holding only a viewer or member role to permanently delete every task in the workspace or silently rewrite task status, priority, assignee, due date, and labels - actions that all other task endpoints correctly restrict by role. Affected deployments are Kaneo versions 2.3.12 through 2.12.1 (fixed in 2.12.2). Exploitation requires valid credentials and existing membership in the target workspace (PR:L), no user interaction, and no special configuration; no public exploit code or confirmed in-the-wild activity has been identified at time of analysis, and the CVSS 4.0 base score is 7.2 (High) reflecting high integrity and availability impact with no confidentiality loss.

Hard-coded credentials in LTSecurity LTK3500SF devices allow unauthenticated remote attackers who can reach Telnet or SSH to recover the root and guest passwords from reversible hashes in /etc/shadow and obtain full root-level operating system access. The affected firmware is AC3F_V1.1.0_build191121, and because the hashes are weak/reversible and identical across units, one successful cracking effort can compromise any reachable device. Publicly available exploit code exists, but there is no confirmed active exploitation (not in CISA KEV); EPSS is 0.51%, and real-world risk is bounded by the narrow deployment base and management-service exposure.

Unauthenticated remote access to an HPE Analytics and Location Engine (ALE) deployment can yield limited sensitive-information disclosure, partial bypass of security controls, or a partial denial of service. The flaw is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, base 7.3), so it is exploitable by anyone able to reach the ALE service or to intercept and manipulate its network traffic. HPE has published an advisory (hpesbnw05137en_us), and no public exploit code and no CISA KEV entry were identified at time of analysis; with each impact dimension rated only Low, this is a broad but shallow weakness rather than a full-system compromise.

Unauthenticated remote write access to the file system with elevated privileges in HPE Analytics and Location Engine (ALE) lets any attacker who can reach the product's internal administrative component overwrite files as a privileged user, with the potential for full system compromise. The flaw carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no special privileges are required against a vulnerable instance; the practical constraint is network reachability, since ALE admin interfaces are normally confined to internal management networks rather than exposed to the internet. No public exploit code was identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but the combination of an authentication-bypass class defect, a critical severity rating, and privileged file-write impact makes this a genuinely high-priority remediation item wherever ALE is deployed.

Default, hard-coded credentials shipped on several administrative and system accounts in HPE's Analytics and Location Engine (ALE) allow an unauthenticated remote attacker to log straight into the management interface and the underlying operating system, yielding full compromise of the appliance. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) because no authentication, user interaction, or special configuration is required - the attacker only needs the known default secrets, which are typically published in advisories or recoverable from firmware - and there is no CISA KEV listing or public exploit code reported at time of analysis. Practical exposure is tempered by deployment context: ALE normally sits inside enterprise WLAN/management networks rather than on the public internet, so real-world risk depends on an attacker already having a foothold or reachability into those internal segments.

Authenticated store customers can seize other shoppers' guest carts in Spree Commerce by calling PATCH /api/v3/store/carts/:id/associate with a derivable, reversible prefixed cart ID, gaining access to the cart's billing and shipping address data and disrupting the guest's in-progress checkout. The flaw affects the 5.4.x line from 5.4.0 and the 5.5.x line up to but not including the fixed releases 5.4.4 and 5.5.4, and only manifests on stores that permit guest checkout and where an eligible guest cart containing address data exists. Rated CVSS 3.1 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), this is a genuine but moderate IDOR-style authorization weakness rather than an unauthenticated takeover; no public exploit code and no confirmed active exploitation were identified at time of analysis.

Incorrect authorization in Adobe Experience Manager Forms JEE (the 6.5 and 6.5 LTS branches) allows a remote, unauthenticated attacker to bypass intended access controls and execute arbitrary code in the context of the running AEM service account, with no user interaction required. The scope-change (S:C) rating and the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H produce a maximum 10.0 base score, reflecting that successful exploitation can affect resources beyond the vulnerable component itself. Exposure is limited to deployments where the Forms JEE component is installed and network-reachable - typically internet- or intranet-facing AEM Forms servers - and at time of analysis no public exploit code or confirmed active exploitation (CISA KEV) was identified, though the pre-authorization nature of the flaw makes it an attractive target for rapid weaponization.

Improper input validation in Adobe's Content Credentials Rust SDK and its companion command-line tool lets unauthenticated remote attackers supply a crafted asset or Content Credentials manifest that slips past the SDK's validation logic, bypassing the intended security control and allowing unauthorized write/forgery of Content Credentials provenance data. The defect is network-reachable with no authentication and no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N), but the impact is integrity-only - confidentiality and availability are unaffected (C:N/I:H/A:N) - so exposure is bounded to applications and workflows that actually invoke the SDK or CLI to validate attacker-supplied content, particularly those relying on these credentials for media authenticity or trust decisions. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS or KEV data was supplied; Adobe's advisory (APSB26-147) is the authoritative source.

Unauthenticated network callers can drive Jira and Confluence tool handlers using an operator's globally configured credentials in sooperset/mcp-atlassian prior to 0.22.0, when the server is run over the HTTP streamable-http transport without an independent authentication boundary. The root cause is a missing-authentication flaw (CWE-306) scored CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), giving remote, unauthenticated, low-complexity read and write access with the permissions of the configured service account and no availability impact. Exploitation is configuration-dependent - stdio deployments and instances fronted by an authenticating proxy or enforcing per-user OAuth identities are not exposed - and no public exploit or CISA KEV listing was identified at time of analysis. The issue is fixed in version 0.22.0.

MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 applies its ENABLED_TOOLS and TOOLSETS least-privilege filters only when tools are enumerated via tools/list, and never re-checks them when a request is dispatched through tools/call. An authenticated, low-privileged MCP client that knows or guesses the exact name of an excluded tool can therefore invoke read, write, and delete operations against Confluence and Jira that the operator deliberately hid, yielding full confidentiality, integrity, and availability impact against Atlassian data (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-862 Missing Authorization). The flaw is meaningful only where the toolset configuration is the trust boundary - the highest risk is in shared-credential or multi-tenant deployments - and no public exploit code was identified at time of analysis. A vendor-released patch is available in version 0.22.0.

Unauthenticated attackers can rewrite any tenant's account balance in Softaculous Virtualizor before 3.2.9 (Patch 9) and in 3.0.0 by POSTing crafted 'act' and 'from_billing_module' parameters together with a 'billing_data' body containing arbitrary uid and balance values to the admin panel dispatcher, which executes a parameterized UPDATE against the users table without performing any authorization check. Publicly available exploit code exists, and vendor patches are available (3.2.9 Patch 9 and 3.3.0). Because no credentials, privileges, or user interaction are required (CVSS:3.1 PR:N/UI:N), any internet-reachable Virtualizor admin panel is directly exposed; the assessed impact is integrity-only - account balance manipulation that can drive automated service suspension for targeted accounts - not code execution or data disclosure.

Unauthenticated network clients that can reach an mcp-atlassian server running in HTTP (streamable-http) transport mode can invoke Atlassian tools using the operator's globally configured Jira or Confluence credentials, inheriting that account's read and write access to both products. The flaw is an authentication deficiency (CWE-287) in which the request path through UserTokenMiddleware, AtlassianOpaqueTokenVerifier, and _get_fetcher accepts a request without a verified user identity and falls back to the shared, operator-scoped credential set; exploitation requires no authentication (PR:N), user interaction, or special privilege once the endpoint is reachable, which is why the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N (10.0). Exposure is limited to the shared-credential/multi-tenant deployment pattern - stdio-transport installs and per-user token deployments that never fall back to global credentials are not affected - and at the time of analysis no public exploit code had been identified and the issue was not confirmed actively exploited (CISA KEV).

Remote code execution in Adobe Campaign Classic allows an unauthenticated network attacker to invoke functionality that should have been access-controlled, achieving arbitrary code execution in the context of the current application user without any user interaction. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, score 10.0) reflects a scope-changing flaw, meaning the vulnerable component can affect resources beyond its own security boundary - a combination that makes this a genuine top-priority vulnerability for any internet- or partner-reachable ACC deployment. As of analysis there is no CISA KEV listing and no public exploit identified at time of analysis; Adobe's advisory APSB26-142 is the authoritative source for affected and fixed builds.

Unauthenticated remote code execution in Adobe Campaign Classic allows attackers to execute arbitrary code in the context of the current user due to an incorrect authorization flaw (CWE-863). The flaw is network-reachable with low complexity and no user interaction (CVSS 9.1), though code execution is limited to the application user context rather than system privileges. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.

Missing authentication on Postiz's enterprise/reseller organisation provisioning endpoint lets an authenticated low-privilege user escalate into full control of a newly minted top-tier organisation. Because the enterprise controller was omitted from the authentication middleware's allow-list, the route is network-reachable without any session, and its sole gate - a signature check on a token in the request body - is satisfied by the attacker's own ordinary login token, since login tokens are signed with the same instance secret and carry no purpose, audience or expiry claim. The endpoint then creates an organisation on the highest subscription tier flagged lifetime with an oversized channel allowance, provisions an owner account for the attacker, and returns a working API key for the public API in the response body (CVSS 3.1 7.1, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L; CWE-306). No public exploit code has been identified at time of analysis, but the attacker only needs any valid account on the instance, which on self-registration-enabled deployments means anyone. Vendor-released patch: v2.24.0.

Authentication bypass in 9Router (npm package '9router') before 0.5.6 lets a remote, unauthenticated attacker reach the public LLM API under /api/v1/* by simply adding the header X-9r-Real-Ip: 127.0.0.1, which the application's isLocalRequest() logic in src/dashboardGuard.js trusts when deciding whether canAccessPublicLlmApi() may skip API-key validation. Successful abuse grants unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models; the verified affected route is GET /api/v1/models. Per the assessed vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, 7.3), no authentication or user interaction is required, but exploitation is only possible on deployments where requests reach Next.js directly without the bundled custom-server.js wrapper and where the LLM API is network-reachable (the default bind is 0.0.0.0); instances correctly served through custom-server.js are not exploitable. The vendor advisory includes a proof-of-concept showing a 401 baseline request succeeding with 200 OK after the sole header is added.

Authenticated viewer accounts in Frigate NVR can abuse the WebSocket message handler to invoke admin-only control topics, causing service restarts and disabling security monitoring functions across cameras. The flaw affects all releases prior to 0.17.2 and stems from the nginx authentication subrequest proving identity without conveying role information, so frigate/comms/ws.py forwards client-supplied topics to the dispatcher without any role check (CWE-862, missing authorization). Exploitation requires authentication to be enabled plus valid viewer-level credentials, meaning the realistic threat is an insider or the holder of a leaked or shared low-privilege account rather than an anonymous internet attacker; no public exploit code has been identified at time of analysis, and the vendor-released patch is version 0.17.2.

Account takeover in Databasement before 1.7.14 allows an unauthenticated remote attacker who possesses a pending invitation link to load the acceptance page, wait until the legitimate invitee accepts, and then submit acceptance using the cached authorization to overwrite the account password and gain access to managed database credentials and secrets. The vendor-published CVSS 4.0 score is 9.1 (AV:N/AC:L/AT:P/PR:N/UI:N), while the independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N because exploitation requires a leaked or forwarded invitation link and a timing race rather than a default-open path. Exploitation status is no public exploit identified at time of analysis, and no CISA KEV status was provided.

Unauthenticated remote attackers can completely compromise the web management portal of Lantronix console servers, reading sensitive configuration files, writing files to arbitrary filesystem locations, and ultimately achieving remote code execution. Affected are SLC8000 units below firmware 9.7.0.5, EMG8500/EMG7500 units below firmware 9.7.0.1, and SLB882/SLCx-03/SLCx-02 devices, which are vulnerable in every firmware version released to date. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; vendor CVSS 4.0 score 10.0) requires nothing more than HTTP reachability to the portal upload endpoint - no credentials, user interaction or non-default settings - and exploitation yields total loss of confidentiality, integrity and availability on the device plus potential impact on serial-connected downstream equipment; no public exploit code has been identified at time of analysis, though a third-party technical writeup accompanies the disclosure.

Predictable session-token generation in the web management portal of Lantronix SLC8000, EMG8500, EMG7500, SLB882, SLCx-03 and SLCx-02 console servers allows unauthenticated attackers to derive a valid token belonging to a logged-in user and replay it from a different source address, achieving elevated privileges on the device and potentially on downstream serial-attached equipment. Session tokens are produced deterministically from the device model plus the current time at one-second resolution, leaving only a small enumerable keyspace, and a crafted URI that abuses file-extension handling in the web server's path routing defeats the per-session source-IP and User-Agent validation. Rated CVSS 4.0 base 8.9 (AV:N/AC:L/AT:P/PR:N/UI:A, all impacts High) with our independent assessment at CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H; exploitation requires network reachability to the portal and a legitimate user session to be live, no public exploit has been identified at time of analysis, and all firmware versions are affected so version-based mitigation is unavailable from the provided data.

Hard-coded credentials in NVIDIA Infrastructure Controller for Linux (versions 0 through 1.9) let an unauthenticated attacker who can reach the device from an adjacent network segment log in with embedded, static credentials, resulting in high confidentiality, integrity, and availability impact (CVSS 3.1 8.8, AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Because the password is static across installations and recoverable by anyone who can inspect the binary or firmware image, exploitation requires no user interaction and no prior authentication, but it does require the attacker to reside on the same broadcast or management network segment rather than the open internet. No public exploit code has been identified at time of analysis, there is no CISA KEV listing, and EPSS is low at 0.23% (14th percentile), with CISA SSVC rating exploitation as "none" and the attack as not automatable.

Missing authentication for a critical function in NVIDIA Infrastructure Controller for Linux (versions 0 through 1.9) allows remote, unauthenticated attackers to reach a privileged operation without credentials, enabling data tampering, denial of service, and information disclosure. The vendor-assigned CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8), and the independent assessment concurs, meaning no authentication, no user interaction, and no special complexity are required against a network-reachable instance; the practical limiting factor is exposure, since this is a specialized AI/HPC datacenter management component usually confined to internal management networks. There is no public exploit identified at time of analysis and EPSS is low at 0.41% (35th percentile), though CISA SSVC rates technical impact as partial and automatable exploitation as 'no'; the specific critical function lacking authentication is not named in the available data.

Hard-coded credentials in NVIDIA Infrastructure Controller for Linux (versions 0 through 1.9) let an unauthenticated remote attacker who possesses the embedded secret log in to the controller's management interface and obtain full control, resulting in privilege escalation, data tampering, denial of service, and information disclosure; the CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-798). Because the embedded credential itself is the authentication mechanism, no pre-existing account is required, but practical exploitation depends on the controller being network-reachable and on the attacker extracting or knowing the hard-coded value from the firmware/image or documented defaults. There is no public exploit identified at time of analysis and the product is not listed in CISA KEV, though the specialized datacenter/DPU infrastructure-management role of this component means exposure is typically limited to segmented management networks rather than the public internet.

Improper authentication in NVIDIA Infrastructure Controller for Linux (versions 0 through 1.9, tracked as EUVD-2026-84409) allows a remote, unauthenticated network attacker to bypass authentication and obtain privilege escalation, information disclosure, and data tampering with full confidentiality, integrity, and availability impact per the CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8 critical). No public exploit code has been identified and there is no confirmed active exploitation (CISA KEV does not list this CVE); EPSS is 0.32% (25th percentile), and CISA's SSVC assessment rates exploitation as none, automatable as no, and technical impact as partial, indicating low near-term mass-exploitation likelihood. Practical exposure is further limited because the affected component is a specialized NVIDIA datacenter/GPU-infrastructure management service typically deployed on internal management networks rather than internet-facing hosts; the specific vulnerable endpoint or protocol is not disclosed in the advisory.

Missing authorization in the MarketKing multivendor marketplace plugin for WordPress (before 2.1.72) lets any authenticated user with subscriber-level access or higher read other vendors' payout pages, financial reports, and dashboard content by submitting an arbitrary vendor user ID to the marketking_get_page_content AJAX action. Exploitation is a single parameter-tampering request over the network with no victim interaction, but it requires a valid low-privilege session on a site that runs the plugin as an active marketplace with vendor accounts holding financial data, as reflected in the assessed CVSS vector (PR:L, UI:N). Impact is limited to confidentiality - no modification or denial of service is possible - and no public exploit code has been identified at time of analysis; the vendor has released a fix in 2.1.72.

Missing authentication in the ManageEngine ADSelfService Plus REST API (all builds before 7001) lets remote, unauthenticated attackers reach API functionality that should require a valid session or credential, as classified under CWE-306. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H (8.6), meaning no credentials and no user interaction are needed, with the highest rated component being availability impact and more limited confidentiality/integrity effects - the exact reachable endpoints are not disclosed in the vendor advisory. No public exploit code and no confirmed active exploitation were identified at time of analysis, so EPSS/KEV signals cannot be used to prioritize this; risk is driven by internet-exposed instances of a pre-7001 build, and patching to build 7001 removes the exposure entirely.

Replay of a captured Tempo subscription credential in ZenHive mpp 0.14.0 through 0.16.1 lets an attacker who already holds a validly signed Tempo KeyAuthorization repeatedly charge the same payer's wallet. The signed authorization is bound only to chain id, key type, key id, expiry, limits, and scopes - never to the challenge that prompted it - so it verifies against every challenge the server issues for the same subscription terms, and because Subscription.activate/4 deduplicates activations solely by challenge id, a fresh challenge yields a new dedup key and the settlement transaction is rebuilt and broadcast again. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the flaw class is a straightforward capture-replay, exploitation requires only that the attacker obtain one signed credential (attack requirements: present, AC:H), and the independent assessment rates integrity impact High on a CVSS:3.1 base of 8.2.