Authentication Bypass

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.

Remote code execution in Qualcomm Snapdragon-based products allows unauthenticated network attackers to bypass authorization through the SocketIO interface and execute arbitrary code. The vulnerability carries a CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting full confidentiality, integrity, and availability impact, and no public exploit was identified at time of analysis. Exploitation is constrained primarily by whether the SocketIO endpoint is network-reachable, because exact affected firmware versions and default exposure state are not specified in the available data.

Unauthenticated attackers can reset the password of any Tankuam Places Kompini account, including administrative accounts, by tampering with the 'usuariId' parameter on the '/password/guardarClau/recover' endpoint. The recovery JWT is issued for the password-recovery workflow but is never checked against the account identifier it is used with, so any valid recovery token can be replayed against an arbitrary user ID - a classic insecure direct object reference (CWE-639) that yields full account takeover. Both the NVD-assigned CVSS 4.0 base score of 9.3 and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) rate this critical, and exploitation needs no authentication, no privileged role and no victim interaction; no public exploit code has been identified at time of analysis, and the practical constraint is simply that the affected deployment must be network-reachable at the recovery endpoint.

Erlang/OTP's ssl application in affected releases (OTP 22.2 through the fixed 27.3.4.18, 28.5.0.7 and 29.1.1) will complete a TLS 1.3 client handshake against any peer that answers with an unsolicited pre_shared_key extension, allowing that peer to impersonate the intended server while holding no certificate, no private key and no prior session. Because the bogus resumption flag short-circuits certificate handling, ssl:connect returns {ok, Socket} even though certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all skipped; an unauthenticated network-positioned attacker (man-in-the-middle, hijacked route/DNS, or a server the client is lured into contacting) can exploit this, and clients restricted to TLS 1.2 are not affected. A vendor patch is available and no public exploit code has been identified at time of analysis.

Unauthenticated attackers can bypass authentication in the WordPress plugin Taxi Booking Manager for WooCommerce (Magepeople Inc.) at versions before 2.0.8, reaching plugin functionality that should require a valid session - an alternate path or channel skips the authentication check entirely. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation is remote, unauthenticated, low-complexity, and requires no user interaction on a default install with the plugin (and WooCommerce) active; however, the all-LOW confidentiality, integrity, and availability scores mean the bypass yields only bounded access rather than full administrative takeover. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, so this is a genuine unauthenticated authentication-bypass issue whose real-world priority is moderate rather than critical.

Missing authentication in the WebSocket Service of the Gigatech PDV5701 point-of-sale terminal (firmware 1.0.31_240305_112640, exposed via /index.html) lets unauthenticated remote attackers reach functionality that should require credentials, yielding full confidentiality, integrity, and availability impact with a CVSS 4.0 score of 9.3. Exploitation needs only network reachability to the device's WebSocket endpoint - no credentials and no user interaction (PR:N/UI:N) - though practical exposure is limited to attackers who can route to the terminal, which is typically deployed on a constrained retail or fiscal LAN rather than the public internet. Publicly available exploit code exists; there is no confirmed evidence of active exploitation (not in CISA KEV), and the vendor was contacted prior to disclosure but did not respond.

DesktopSMS 1.11.0 (MrPear) exposes a local/loopback service that performs privileged SMS operations - sending messages, returning SMS-derived content, and persisting a paired identity - without any pairing confirmation, authentication, or user interaction, so any process already running on the same device can exercise the victim app's SMS permissions. Exploitation is strictly local: an attacker must first have code execution on the device (a co-installed malicious app, or ADB/loopback access), which is why the assessed vector is AV:L with PR:N and UI:N but a hard device-foothold prerequisite. Publicly available exploit code exists (a proof-of-concept client has been published), and while no confirmed active exploitation is recorded, the low complexity and absence of user interaction make this a practical post-foothold privilege-escalation primitive against the app's SMS capabilities.

Missing write-command registration for graph.UDF in the FalkorDB Redis module versions 4.20.1 through 4.20.4 allows a client that is already authenticated and authorized to issue module commands (CVSS PR:L, unauthenticated external attackers are not sufficient) to invoke a command that Redis does not treat as a write, producing incorrect behavior in deployments whose correctness depends on write-command semantics such as replication propagation, persistence, and replica handling. The assessed impact is primarily availability (A:H) with a minor integrity effect (I:L) and explicitly no confidentiality impact (C:N), giving a CVSS of 7.1; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the exposed version range is narrow. Note that the supplied 'Information Disclosure' tag is not supported by the assessed vector, which sets C:N and attributes risk almost entirely to availability.

Authentication bypass in Joplin Server prior to 3.7.2 allows an unauthenticated remote attacker who can control or influence a SAML identity assertion to obtain a valid session for an existing local password-based account purely by matching the asserted email address, granting read and write access to that user's notes, files, and settings without knowledge of the local password. The defect is gated to deployments running mixed authentication - local password accounts and SAML SSO enabled together (SAML_ENABLED=true) - so SAML-only, local-only, and default single-auth installations are not exposed. The issue is fixed in version 3.7.2 via a check that rejects SSO login for non-external accounts; no public exploit identified at time of analysis.

Path-based RBAC authorization bypass in Envoy Proxy lets an unauthenticated remote client reach protected backends such as /admin by appending a semicolon path parameter (e.g. /admin;x), because the router strips that suffix before route matching while the RBAC url_path matcher evaluates the untouched raw path. Exploitation is tightly gated rather than default: it requires a route configured with ignore_path_parameters_in_path_matching, a path-based RBAC rule (PathMatcher or UriTemplateMatcher) guarding the protected path, and a crafted request that still selects the protected route after stripping. All releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are affected; the vendor has published fixed releases, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.

Credential-holding attackers can completely bypass TOTP two-factor authentication on Sync-in Server versions prior to 2.4.0 by sending a single unauthenticated-looking request to POST /api/auth/token, which issues full access and refresh JWTs without ever checking the account's twoFaEnabled flag. The flaw is only exploitable by an authenticated party in the sense that the attacker must already hold a valid username and password obtained through phishing or credential theft (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, base 8.1), and it only yields an advantage against accounts that actually have TOTP enabled; the parallel POST /api/auth/login endpoint enforces the second factor correctly. No public exploit code was identified at time of analysis and CISA KEV does not list this CVE, but because the bypass converts stolen passwords directly into long-lived session tokens, the practical risk is high wherever 2FA is the last line of defense.

Privilege escalation in jshERP through 3.6 lets any authenticated user - including one holding only a low-privileged tenant account (CVSS PR:L, no administrative rights, user interaction, or non-default configuration required) - modify or delete arbitrary role definitions through the /role/update and /role/delete endpoints in RoleController, which perform no caller-permission checks. Successful abuse allows an attacker to widen a role's data scope to 'all data', delete roles, and consequently read every business record in the tenant. Publicly available exploit code exists (a proof-of-concept script has been published); there is no indication of confirmed active exploitation (not in CISA KEV), and no vendor-released fixed version has been identified from the available data, making this a genuine, actionable priority within its limited install base.

jshERP through 3.6 exposes unsalted MD5 password hashes via the /user/info endpoint, allowing any authenticated user to retrieve password digests for arbitrary users by supplying their user IDs. This information disclosure (CWE-200) affects all versions up to 3.6, and publicly available exploit code exists. Attackers with a low-privilege account can enumerate user IDs to obtain hashes, which can be cracked offline to recover plaintext passwords, potentially leading to full account takeover for weak passwords. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, reflecting the need for authentication and the high confidentiality impact.

Authenticated account takeover in jshERP through 3.6 allows any logged-in user to reset the password of any other account, including administrators, by issuing POST /user/resetPwd with an arbitrary target user ID. Because the endpoint performs no ownership or authority check on the supplied user ID and resets the victim's password to a known default value, an attacker holding even the lowest-privilege credentials can seize administrative control of the application. Publicly available exploit code exists (a Python PoC), and while there is no confirmed active exploitation (CISA KEV) or exploitation telemetry, the flaw is trivial to trigger and needs no user interaction, making insider or low-privilege-credential exposure the primary risk.

Cross-tenant record tampering in HomeBox versions prior to 0.26.0 allows an authenticated low-privileged user to overwrite or permanently delete another group's maintenance entries by supplying a maintenance-entry UUID that belongs to a different tenant. The flaw is a CWE-639 broken object-level authorization (IDOR) in the maintenance-entry update and delete repository paths, which act on the caller-supplied ID without confirming the record belongs to the caller's active group; exploitation requires a valid session plus knowledge of a non-enumerable random UUID, so it is access-gated rather than trivially reachable and is practically limited to multi-group/multi-tenant deployments. Impact is blind write/delete only with no data disclosure, and there is no public exploit identified at time of analysis and no indication of active exploitation. Vendor-released patch: 0.26.0.

Code execution with access to GCP, AWS, and Snowflake credentials is possible in Feast's own CI pipeline prior to version 0.65.0, because the pr_integration_tests.yml workflow uses pull_request_target together with the synchronize event and preserves ok-to-test, approved, or lgtm labels on newly pushed commits. A fork contributor can get maintainer approval for a benign revision and then push altered commits that are checked out from refs/pull/${{ github.event.pull_request.number }}/merge and run through privileged make targets, resulting in runner code execution, credential disclosure, and possible access to downstream cloud resources; the CVSS vector indicates the attacker needs only a low-privilege GitHub identity (PR:L) plus a maintainer's approval action (UI:P), and no public exploit code was identified at the time of analysis. This is a CI/CD pipeline misconfiguration in the upstream feast-dev/feast repository rather than a flaw in deployed Feast installations, and it is fixed in 0.65.0.

Account fixation in Hatchet's OAuth callback handling lets an unauthenticated attacker bind a victim's existing Hatchet session to an OAuth identity the attacker controls, achieving login CSRF and account takeover. The flaw affects Hatchet versions prior to 0.91.1 and is only reachable when the deployment has enabled at least one OAuth integration (auth.google.enabled, auth.github.enabled, or the Slack integration) and the victim has already completed an OAuth flow in the current browser session; exploitation still requires victim interaction (the victim's browser must follow the attacker's crafted callback URL containing an empty state parameter and the attacker's own authorization code). The vendor-released patch is version 0.91.1 (upstream commit f90464189ad642251e09412d0f99fde353036428); there is no indication of confirmed active exploitation (no CISA KEV listing) and no public exploit code identified at time of analysis, although the upstream fix ships an integration test that documents the bypass chain.

Authentication bypass in Mailu 2.0 through 2024.06.55 and Mailu helm-charts before 2.7.3 allows unauthenticated remote attackers to spoof the trusted proxy identity via a client-controlled X-Forwarded-By header, bypassing header-based proxy authentication. This affects only deployments with PROXY_AUTH_WHITELIST configured and REAL_IP_HEADER unset; default configurations are not vulnerable. The vendor has released fixes in Mailu 2024.06.55 and helm-charts 2.7.3, and no public exploit has been identified at time of analysis.

OpenBao versions prior to 2.6.0 fail to reject syntax-significant characters when templated identity data is substituted into ACL, PKI, and SSH policies, allowing an authenticated principal who can write that identity data to broaden path matching, obtain certificates for unauthorized domains, or add unauthorized SSH principals. Exploitation is gated on a non-default configuration: the policy must use templates that substitute attacker-modifiable identity metadata (for example {{identity.entity.metadata.domains}} or {{identity.entity.metadata.sans}}), and the attacker must already hold the capability to update that identity record (such as update on identity/entity), consistent with the assessed CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N. Deployments whose templates rely solely on the randomly generated identity.entity.id value are not affected, there is no user interaction, and no public exploit code was identified at time of analysis.

Signature verification bypass in Red Hat's openshift/oc-mirror tool allows an attacker who can intercept or manipulate traffic to the release-signature endpoint to have a forged PGP-signed release payload accepted and mirrored into a disconnected OpenShift 4 registry. The defect (CWE-347) causes oc-mirror to evaluate signature errors before the full signed body has been processed, so a message carrying a legitimate Red Hat release key ID but an invalid signature can pass validation during a normal mirror operation. Exploitation is gated by a demanding precondition: the attacker must already hold a man-in-the-middle/on-path position on the network path and the victim must be actively running an oc-mirror signature-verifying operation; no credentials against oc-mirror are required (PR:N) and no user interaction beyond running the mirror process is needed (UI:N). The realistic impact is integrity-only, since the assessed vector scores C:N/I:H/A:N, and no public exploit has been identified at time of analysis.

Cross-event EventReport disclosure and tampering in MISP versions before 2.5.47 lets an authenticated user who can submit module (enrichment) results reparent, read, or overwrite another event's report by supplying a forged 'id' field in the resolved module data. The root cause is an authorization bypass through a user-controlled key (CWE-639): the report loop in Event::processModuleResultsData did not unset the client-supplied 'id' before calling save(), so the CakePHP ORM updated an existing report row belonging to a different event instead of inserting a new one. Exploitation is gated by authentication and the module-result-submission privilege, and by knowledge of a valid target EventReport id; the independent assessment rates this a genuine but moderate authorization flaw rather than a mass-data-exposure issue, and no public exploit code was identified at time of analysis, though the vendor has published an upstream fix commit (4c1a03b20).

NooBaa's S3 presigned URL verification fails to reject unsigned x-amz- headers, allowing an attacker who holds a valid SigV4 presigned PUT URL to inject an x-amz-copy-source header and convert an upload into a CopyObject operation. This can lead to unauthorized copying of any data the original signer can access within the NooBaa / OpenShift Data Foundation 4 storage system. The issue affects noobaa-core and is rated 7.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N); no public exploit or active exploitation has been identified at time of analysis.

Unauthenticated attackers on the local network can bypass authentication and gain full control of D-Link DIR-X1860 and DIR-X1860Z routers (firmware up to 1.0.2.220120.165402) by manipulating the passwd_set argument in the /ubus interface of the routerd component. Publicly available exploit code exists, and the vulnerability has a CVSS 4.0 score of 7.4, though it is not confirmed as actively exploited (no KEV).

Unauthenticated comment deletion in the Tripzzy WordPress plugin (versions 1.1.8 through before 1.5.1) lets any remote attacker permanently delete arbitrary comments on an affected site with a single crafted request. The plugin's AJAX action is registered for unauthenticated users by design but performs neither an authorization/capability check nor validation of the comment identifier being removed, so it is a textbook missing-authorization plus IDOR weakness (CWE-284, CVSS 3.1 7.5 HIGH, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). Publicly available exploit code exists, but the impact is bounded: exploitation only yields permanent integrity/data loss of comment content, with no code execution, privilege escalation, or data exfiltration, and the vendor has shipped a fix in version 1.5.1.

Unauthenticated remote attackers can abuse a missing authorization check in a REST route of the Botiga Pro WordPress plugin (versions before 1.6.5) to update arbitrary WordPress options, inject stored web scripts that execute on every front-end page, and move arbitrary posts to the trash. The option-write primitive enables privilege escalation and full site takeover, for example by altering registration or default-role settings, while the stored script injection yields persistent cross-site scripting against all site visitors. The issue is rated CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), publicly available exploit code exists, and no CISA KEV listing has been observed; the only deployment prerequisite is that the Pro add-on plugin is installed and active, as the free Botiga theme alone is unaffected.

CordysCRM before 1.7.2 exposes its SSE notification endpoints anonymously, allowing a remote unauthenticated attacker who can reach the backend HTTP interface to read another user's workflow events, approval requests, mentions, and alerts, inject SYSTEM_HEARTBEAT messages into that user's stream, or close that user's SSE channel. The flaw is missing authentication (CWE-306) in the Shiro public-path whitelist and the controller's trust in a caller-supplied userId; the provided source advisory CVSS 4.0 score is 9.3, while the independent CVSS 3.1 assessment is 8.6 because confidentiality impact is high but integrity and availability impact are limited to a selected user's notification stream. No CISA KEV entry or public exploit code was identified at time of analysis, but exploitation requires only network reachability and a target userId.

Authorization bypass in IBM Guardium Data Protection 12.2 lets remote, unauthenticated network attackers (CVSS vector AV:N/PR:N/UI:N) reach the product's management/web interface and sidestep intended authorization checks, granting access to data-protection functions they should not be able to invoke. IBM scores the flaw 8.1 (HIGH) with full unscoped impact (C:H/I:H/A:H) and AC:H, while our independent assessment keeps the same unauthenticated network vector but lowers the assessed impact to C:L/I:L/A:L - meaning the practical effect is more likely unauthorized read/modification of limited functionality than complete compromise, with the high complexity reflecting a non-trivial precondition (a specific request state, timing, or authorization configuration) that the vendor does not disclose. No public exploit identified at time of analysis, and a vendor fix is available through IBM support node 7288035.

IBM Guardium Data Protection 12.2 accepts TLS peer certificates it should reject, letting an attacker positioned on the network path impersonate a trusted endpoint and bypass the security restrictions the encrypted channel is meant to enforce. The vector is PR:N and UI:N, so no credentials or user action are needed, but the practical barrier is the MITM foothold itself - ARP or DNS spoofing, a rogue access point, or a compromised intermediate segment - which is exactly why the score carries AC:H and why properly segmented deployments are largely shielded. There is no public exploit code identified at time of analysis and the issue is not listed in CISA KEV; IBM has published a vendor fix.

Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-reachable attackers to invoke privileged load-balancer operations, compromising the integrity and availability of the affected deployment. The flaw is rated 9.9 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) and maps to CWE-306, so no credentials or user interaction are required; the practical barrier is that the Guardium management interface exposing the servlet must be reachable across the network, and such interfaces are usually confined to segmented internal networks. Impact is concentrated on load-balancer control operations rather than broad data exposure (confidentiality impact is low), and no public exploit identified at time of analysis; the issue is not listed in CISA KEV. IBM has published a patched release through its support advisory.

Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the ChangeTrackerServlet, which is missing authentication (CWE-306). The vendor CVSS 3.1 vector rates this 9.9 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L), and the independent assessment preserves the unauthenticated network-reachable nature while treating scope as unchanged; no public exploit was identified at time of analysis and there is no CISA KEV confirmation. IBM has published patch information, so affected deployments should be updated and have network access to the management web tier restricted until patched.

Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based access controls guarding the Guardium management interface and reach that interface without satisfying the network allowlist. IBM rates the flaw 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but our independent assessment scores it materially lower (C:L/I:N/A:N) because the bypass defeats the IP filter rather than the interface's own authentication, so real impact hinges on what the management interface permits once reached and whether it applies its own credentials. No public exploit code has been identified at time of analysis, and exploitation is only possible where the management interface is network-reachable and administrators treat IP allowlisting as the primary or sole control; deployments whose management plane is fully segmented behind a firewall with no attacker path are not exposed.

Authentication bypass in IBM Sterling File Gateway lets a remote, unauthenticated attacker forge or inject an unvalidated SSO header and obtain a fully authenticated session on the gateway's web interface. The flaw is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) because no credentials, privileges, or user interaction are required, and a successful bypass yields high confidentiality and integrity impact over file-transfer workflows. No public exploit identified at time of analysis, but exploitation is trivial for anyone who can reach an SSO-header-enabled deployment, so internet-exposed instances should be treated as high priority; IBM has published a fix advisory.

Unauthenticated attackers who can reach the PD Master's /pd_register WebSocket endpoint can register arbitrary nodes in LightLLM through 1.2.0, causing full user prompts routed to the attacker's socket to be disclosed, disrupting service by displacing legitimate nodes, and forcing the PD Master to issue requests toward internal network addresses. The root cause is CWE-306 (missing authentication for a critical function): the registration handler accepts crafted JSON without validating the peer address, and the CVSS 4.0 score of 9.3 with PR:N/UI:N reflects high confidentiality, integrity, and availability impact requiring no credentials or user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited to multi-node prefill-decode (PD) disaggregated deployments where the endpoint is network-reachable; single-node or properly firewalled deployments are not exposed.

Missing object-level authorization in the OpenStack Blazar V2 lease API allows any authenticated user to modify or delete leases belonging to other users and projects if they know the target lease UUID. The defect affects Blazar releases before 17.0.1 and arises because the oslo.policy authorize() wrapper resolves the wrong request parameter, so the ownership check silently degrades into comparing the requester against their own project_id and user_id and therefore always passes. No public exploit code has been identified at time of analysis, and exploitation requires a valid cloud credential plus a deployment that actually runs the optional reservation service, but the integrity and availability impact on lease objects is high because reservations underpin the scheduled resource allocations of other tenants.

An authenticated user with access to the OpenStack Blazar V2 REST API can enumerate leases belonging to other projects in Blazar versions before 17.0.1, because the GET /v2/leases endpoint enforces neither project scoping nor an administrator-only policy. This broken access control (CWE-862) exposes lease IDs, reservation IDs, resource IDs, and reservation metadata; the leaked lease IDs can then be leveraged with a separate object-level authorization bypass to modify or delete those leases. The flaw requires valid Blazar credentials and a deployment running the optional Blazar reservation service, and no public exploit identified at time of analysis.

Malicious or compromised Model Context Protocol (MCP) server containers run under ToolHive CLI before 0.30.1 or ToolHive Studio before 0.38.0 are not network-isolated by default, allowing them to reach Docker gateway addresses (host.docker.internal, gateway.docker.internal, 172.17.0.1) and, critically, ToolHive's own API and MCP proxy endpoints, which are reachable without authentication (CVSS vector PR:N). A hostile MCP server can therefore read exposed data and logs, invoke sibling MCP tools, alter process or workload state, and disrupt services without ever escaping the container, with the scope change (S:C) reflecting a pivot from the container into the ToolHive control plane; exploitation requires user interaction because an operator must choose to run the untrusted server (UI:R). The vendor rates this 8.8 (High/Critical); no public exploit code was identified at time of analysis and the issue is not in CISA KEV, though the impact is severe for anyone running third-party MCP servers on Docker with default settings. Fixes are available in ToolHive CLI 0.30.1 and ToolHive Studio 0.38.0, which flip network isolation to enabled by default.

Cross-workspace impersonation and complete authorization bypass in kcp (kcp-dev) before 0.31.4 and 0.32.x before 0.32.2 let any authenticated tenant forge Kubernetes-style identity headers that the shard accepts as trusted authentication assertions. Because the front-proxy and the server localproxy forward inbound X-Remote-User, X-Remote-Group, and X-Remote-Extra-* headers without clearing them, an attacker with valid credentials for any single workspace can supply values such as X-Remote-Group: system:masters, authorization.kcp.io/warrant, authentication.kcp.io/scopes, or a group used for per-workspace required-group gating to read, write, or delete resources, secrets, RBAC data, APIExports, APIBindings, and LogicalClusters across the installation. Exploitation requires authenticated access (CVSS vector PR:L, AV:N, no UI), yields changed scope per the vendor vector (CVSS 9.9), and no public exploit code or confirmed active exploitation was identified at time of analysis; fixed releases 0.31.4 and 0.32.2 are published.

Unauthenticated access to the network video streaming service in CareCam CM2507 (HMT CM2507) IP cameras exposes live camera video to anyone who can reach the device across the network. Because the streaming endpoint ships with no authentication requirement at all (CWE-306), a remote attacker needs only network reachability - no credentials, no user interaction, and no special mode or configuration - to pull the live feed. The realistic blast radius is bounded by exposure and product footprint rather than by exploit difficulty: devices that are internet-facing or reachable through port forwarding are the ones at genuine risk, while units isolated on a dedicated LAN/VLAN are far less exposed. No public exploit code has been identified at the time of analysis, no confirmed active exploitation is indicated by the available intelligence, and CISA ICS-CERT has published advisory ICSA-26-258-08 describing the issue.

Hardcoded MQTT credentials shipped inside Bransys ELD grant unauthenticated read access to real-time telemetry for every active device belonging to a subset of carriers connected to the affected MQTT broker. Because the static credential is embedded in the product, remote attackers who recover it - for example by reverse-engineering the shipped binary or firmware - can subscribe to the broker with any standard MQTT client, and no user interaction or per-victim authentication is required (PR:N/UI:N). The exposure is confidentiality-only against live fleet data (C:H/I:N/A:N in our assessed CVSS 3.1 vector) and no public exploit code or confirmed active exploitation was identified at time of analysis; the reported CVSS 4.0 score of 8.7 reflects the broad device population reachable with a single shared credential, and CISA ICS advisory ICSA-26-260-01 documents the issue.

hickory-resolver releases before 0.26.2 fail to propagate a 'bogus' DNSSEC proof state out of the high-level Resolver::lookup() and Resolver::lookup_ip() APIs, so records that fail DNSSEC signature validation are handed back to the caller as successful, apparently validated answers. This is an integrity-only bypass affecting unauthenticated remote attackers (CVSS:4.0 8.7 / assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) who either control the authoritative zone answering the query or sit on the network path to inject forged records with invalid RRSIGs; applications that do not compile the crate's __dnssec feature are unaffected because they never expected validation in the first place. A vendor fix is available in 0.26.2 (commit 30720f4, PR 3871), and no public exploit code or confirmed active exploitation was observed at time of analysis. This is a genuine, high-priority integrity flaw despite the absence of exploitation telemetry.

Root shell compromise of NetBackup Flex OS appliances is possible for authenticated, low-privileged users who have access to the NetBackup Flex OS management shell. By supplying a specially formed access credential, such a user can bypass the cryptographic signature verification step of a privileged support command (CWE-347), gaining unrestricted root control over the Flex appliance host and all hosted containers, with complete confidentiality, integrity, and availability impact. The vendor CVSS 4.0 score is 9.4 (PR:L, no user interaction); supplied intelligence does not indicate CISA KEV active exploitation or publicly available exploit code, so no public exploit identified at time of analysis.

Quarkus HTTP security path-normalization discrepancy allows unauthenticated remote attackers to craft a URL that the security matcher treats as public while the dispatcher routes it to a protected endpoint, bypassing path-based authorization and reading sensitive data (CVSS 3.1 7.5, C:H/I:N/A:N). This affects deployments that rely on Quarkus HTTP security path-pattern policies to gate confidential endpoints; applications using only handler-level role or annotation checks are not bypassed this way. No public exploit identified at time of analysis.

Sustained brute-force attacks against the HCL BigFix Service Management v27 login interface are possible because the product fails to adequately lock out or throttle repeated failed authentication attempts, letting remote unauthenticated attackers (CVSS PR:N/UI:N) make unlimited credential guesses that, if successful, grant full access as scored (C:H/I:H/A:H). The vendor scores this 9.8, but our independent assessment uses AC:H because the missing lockout does not itself grant access - the attacker must still obtain or guess valid credentials, so real-world impact hinges on password strength, MFA, and whether the login page is internet-exposed. Competing signals frame this as a high-severity design weakness with low current urgency: EPSS is 0.25% (17th percentile), SSVC records Exploitation: none with partial technical impact, no CISA KEV listing exists, and no public exploit code has been identified at time of analysis.

Broken access control in HCL BigFix Service Management lets a low-privileged authenticated user reach administrative screens and functions reserved for higher-privileged roles, effectively escalating their privileges within the ITSM instance. Per the vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 8.1 High), the attacker must already hold a valid standard-role account and can reach the application over the network without user interaction, obtaining full read and write capability over the exposed administrative functionality with no direct availability impact. No public exploit code has been identified at time of analysis, and the vulnerability is not listed as confirmed actively exploited (CISA KEV).

SQL injection and cross-tenant data exposure flaws in HCL BigFix Service Management allow an attacker who can reach the application's request-handling layer to inject database commands and to manipulate tenant/organization scoping values so that another organization's profile data and PII can be read. The vendor rates this 9.8 Critical using a vector that encodes PR:N, but the advisory text itself states the attack requires an authenticated attacker - an internal contradiction; our independent assessment resolves it as AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, so exploitability hinges on whether a valid account is genuinely required, and the cross-tenant half of the impact only applies to multi-tenant deployments hosting multiple organizations. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no fix version was disclosed in the provided data; organizations should treat the vendor KB article as the authoritative source for patched builds.

An authentication bypass in ManageEngine DataSecurity Plus deployments running builds earlier than 6310 allows unenrolled agents to send requests to the server's agent communication interface without completing enrollment or authentication, potentially exposing or altering the data that interface handles. The vulnerability is remotely reachable and requires no user interaction and no prior authentication (CVSS vector PR:N/UI:N), though the vendor's AC:H rating and our own lower independent assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) indicate the practical impact is modest and gated by preconditions such as knowledge of the proprietary agent request format. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so active exploitation is unconfirmed; the risk is hard to pin down because the vendor advisory is the only source and the description is terse.

An authentication downgrade in NASA CryptoLib 1.5.0 lets a remote, unauthenticated attacker defeat Space Data Link Security (SDLS) authentication on the Telecommand receive path by crafting a frame whose Security Parameter Index (SPI) names a weaker Security Association (SA) than the one legitimately authorized for that frame's Global Virtual Channel ID (GVCID). Because the receiver never checks that the selected SA is permitted for the frame's GVCID, the command is processed under the attacker-chosen SA, giving high integrity impact (VI:H, C:N, A:N) against spacecraft or ground-segment command handling. Exploitation is constrained rather than trivially remote: the attacker must be able to inject frames into the TC uplink/command channel (typically an RF ground link or internal command network, not the public internet) and a misconfigured or weaker SA must already exist for the targeted GVCID. No public exploit code was identified at time of analysis, and the flaw is an authorization/downgrade weakness rather than a confidentiality exposure.

Privilege escalation in Azure Database for PostgreSQL allows an authenticated attacker with low privileges to elevate privileges over the network, potentially achieving full control over database resources. With a critical CVSS score of 9.9 due to scope change and high impact, the flaw requires a valid low-privileged identity to exploit; no public exploit code has been identified at time of analysis.

Authentication bypass by spoofing in Microsoft Fabric lets unauthenticated network attackers impersonate a trusted identity and elevate privileges, with a scope change indicating the bypass can cross the initial authorization boundary to affect resources or tenants beyond the attacker's own. Microsoft and independent assessment both score this CVSS 3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting full confidentiality, integrity, and availability impact on the affected multi-tenant analytics service. No public exploit code exists and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis, and because Fabric is a Microsoft-operated SaaS, exposure depends on vendor-side remediation rather than customer patching.

Privilege escalation in Microsoft's Azure Billing service allows unauthenticated, remote attackers to reach full compromise of confidentiality, integrity, and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) by abusing insufficient verification of data authenticity (CWE-345); publicly available exploit code exists, yet CISA's SSVC framework currently records Exploitation as none. Signals therefore conflict and must be weighed carefully: the flaw is rated critical and marked Automatable with Technical Impact total, but EPSS is low at 0.32% (25th percentile) and there is no KEV listing confirming active exploitation. Because Azure Billing is a Microsoft-hosted cloud service, customer-side exposure depends on Microsoft's server-side remediation rather than on local deployment choices, and the description names no specific feature, endpoint, or configuration prerequisite.

Unauthenticated remote attackers can reach a critical function inside Microsoft Azure AI Foundry that performs a privileged operation without any authentication check, giving high confidentiality, integrity and availability impact across the affected service (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, CWE-306). The weakness lives in a Microsoft-operated cloud service rather than a customer-installable product, so both the exposed surface and the fix are controlled server-side by Microsoft and the specific impacted feature is not publicly disclosed. Exploitation signals currently conflict: no public exploit code has been identified and CISA's SSVC rates exploitation as 'none' (automatable: yes, technical impact: total) with a low EPSS of 0.49% (41st percentile), yet the unauthenticated, no-user-interaction path makes the bug trivially automatable once technical details circulate.

Improper access control in Microsoft Azure Logic Apps allows an unauthenticated remote attacker to elevate privileges over the network, gaining high confidentiality and integrity impact against the affected service. The flaw rates CVSS 3.1 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), meaning the vector assumes no privileges and no user interaction are needed, though Microsoft's use of "elevate privileges" in the description hints that some pre-existing tenant or service context may be required - a discrepancy worth verifying against the MSRC advisory. There is no public exploit identified at time of analysis: EPSS is 0.45% (39th percentile), CISA SSVC records exploitation as "none," and no KEV listing exists, but SSVC rates the issue fully automatable with total technical impact.

Authentication bypass by spoofing in Microsoft Dataverse - the data backend underlying Power Platform and Dynamics 365 - lets an unauthenticated remote attacker forge a trusted identity assertion and thereby gain elevated privileges over the network, with full impact to confidentiality, integrity, and availability per the assessed CVSS 8.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is gated by high attack complexity: the attacker must successfully spoof a trusted authentication or identity assertion, which typically requires a condition outside full attacker control (for example a timing/race element or knowledge of environment-specific values) rather than a single deterministic request. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; EPSS is low at 0.38% (32nd percentile), and CISA's SSVC decision framework rates exploitation as 'none' with 'not automatable', so the AC:H precondition remains the principal factor limiting realistic risk.

Authorization bypass in Microsoft Container Registry (MCR) lets an unauthenticated remote attacker supply a manipulated, user-controlled key to reference registry resources they are not authorized to access, producing high confidentiality and integrity impact with a scope change; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) independently computes to a maximum 10.0. Because MCR is a Microsoft-operated cloud service, every tenant and consumer that pulls images, charts, or artifacts from mcr.microsoft.com is potentially exposed through the hosted endpoint rather than through any customer-deployed software. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but the unauthenticated, low-complexity, network-reachable nature of the flaw means the exposure window is determined entirely by how quickly Microsoft remediates server-side.

Session-swapping authentication bypass in the Elixir library AshAuthentication (versions 4.10.0 before 4.15.0 and 5.0.0-rc.0 before 5.0.0-rc.14) allows an attacker who can plant a remember-me cookie in a victim's browser to displace the victim's live authenticated session with one belonging to the attacker's own account, so anything the victim enters afterwards is captured under attacker-controlled state. The root cause is a guard/reader key mismatch: AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 checks the session for a '<subject_name>_token' key, but store_in_session/2 only writes that key when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name, leaving the already-signed-in short-circuit unreachable and the remember-me sign-in running on every request through the per-request browser pipeline plug. No public exploit code or confirmed active exploitation was identified at time of analysis, but exploitation is constrained by prerequisites - the attacker needs a remember-me token for their own account, a cookie-injection channel (shared/parent-domain cookie write, XSS, or on-path position), and subsequent victim interaction - which independent assessment reflects with CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N; vendor fixes are available in 4.15.0 and 5.0.0-rc.14.

Unauthenticated, unauthenticated-by-design HTTP GET requests to WeGIA's deletar_socios.php endpoint before version 3.8.5 can irrevocably wipe member and contributor records, because the endpoint's only gate is a SHA-256 comparison against a hardcoded key string that ships in the public source repository and is therefore known to any attacker who reads the code. Per the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N, no session, credential, or user interaction is needed; the practical limits are that the target must run a pre-3.8.5 release, the endereco, pessoafisica, pessoajuridica, and socio tables must exist, and the web process's database account must hold TRUNCATE privileges. With a CVSS base score of 9.1 and integrity/availability impact rated High (and no confidentiality impact), the flaw is a low-friction data-destruction issue; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, though the required key value is exposed by design in the repository. Vendor-released patch: 3.8.5.

Speakr, a self-hosted audio transcription web app, is affected before 0.8.21-alpha by a chained authentication bypass in which a bogus token supplied as a query parameter permanently disables CSRF protection for a targeted view, letting a remote, unauthenticated attacker who lures a logged-in victim to attacker-controlled content on a sibling subdomain perform state-changing actions as that victim - editing profile data, custom prompts, transcription settings and preferences, toggling administrative status through admin_toggle_admin, and, for SSO-only accounts, silently setting a local password that bypasses SSO. No valid token or credentials are needed because the token check trusts any present token without hashing or database validation, but exploitation is conditional: it requires a victim with an active session, mandatory user interaction, a sibling-subdomain foothold, and a domain-scoped session cookie, which is why the independent assessment rates it as moderate-but-conditional risk under CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N. There is no public exploit identified at time of analysis; the vendor has released a fix in 0.8.21-alpha.

Unauthenticated OAuth handling in Obsidian Web MCP (obsidian-web-mcp) prior to 0.2.0 lets any remote caller who can reach the deployment obtain the static VAULT_MCP_TOKEN and then invoke vault_read, vault_write, vault_search, vault_list, vault_move, and vault_delete against the entire Obsidian vault. Because /oauth/authorize issues an authorization code with no login, consent, or session check, and /oauth/token exchanges that code for the bearer token without authenticating a client, the flaw carries a CVSS of 9.4 (AV:N/AC:L/PR:N/UI:N, C:H/I:H) and grants full read and write control of personal notes; optional PKCE does not stop an attacker-initiated flow, and /oauth/register additionally returns the configured VAULT_OAUTH_CLIENT_SECRET, exposing a client_credentials path. No CISA KEV listing is present and no public exploit identified at time of analysis - exploitation requires only that the server be network-reachable, which is realistic for instances published through the project's recommended Cloudflare Tunnel.

Unauthenticated passkey enrollment in OpenReception appointment-booking software prior to 1.1.1 lets remote attackers inject a controlled WebAuthn credential for a guessed userId and then log in as that staff member, yielding a valid STAFF session without any credentials. The attacker only needs the tenant's public tenant ID and a target staff email address, plus reachability of the public booking API, to run an inject-then-login oracle that identifies the matching userId and completes authentication with their own assertion. Successful hijacking of a STAFF account exposes tenant data, and escalation to TENANT_ADMIN identifiers allows modification or deletion of tenant resources and key shares, which can render appointment data permanently undecryptable and take booking services offline; GLOBAL_ADMIN accounts are not reachable through this tenant-scoped path. There is no public exploit identified at time of analysis, though the vendor has released a fix in version 1.1.1 and the code diff demonstrates the defect unambiguously.

Replay protection bypass in Keycloak deployed in stateless mode with a MySQL or MariaDB backend allows remote, unauthenticated attackers who have captured a still-valid single-use artifact - such as a JWT client assertion, a DPoP proof, or a TOTP code - to replay it against the token endpoint or login flow and obtain unauthorized access. The weakness is a mismatch in row-count semantics between the MySQL/MariaDB database driver and Keycloak's application logic, which silently defeats the one-time-use check; the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.4) reflects high confidentiality and integrity impact tempered by the hard configuration prerequisite and the requirement to intercept a valid artifact before it expires. At time of analysis no public exploit identified at time of analysis and the flaw has not been confirmed actively exploited (CISA KEV); the non-default stateless plus MySQL/MariaDB deployment combination, the need for a network position capable of capturing artifacts, and the narrow validity window keep practical exploitability constrained.

A stale-pointer (use-after-free) lifetime bug in the Linux kernel NFSv4 client can leave a freed nfs_client reachable through the NFSv4.0 callback identifier registry, so that a later callback lookup by cb_ident takes a reference to freed memory with high confidentiality, integrity and availability impact. The defect is triggered only when the host is configured as an NFSv4.0 client and an initialization step inside nfs4_alloc_client() fails after the callback identifier has been registered - typically an allocation failure under memory pressure that is not attacker-controlled - which is why the input CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N) is badly overstated and the independent assessment rates it CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Linux kernels carrying the NFSv4 callback IDR code are affected up to the stable backports fixing it (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6 and 7.3-rc1); no public exploit identified at time of analysis, and the 'Authentication Bypass' tag does not match the assessed local, privileged failure-path defect.

AsyncHttpClient (AHC) 2.1.0 through 2.16.0 and 3.0.x before 3.0.12 can disclose authenticated SOCKS proxy credentials - including directly reversible Basic credentials and NTLM/Kerberos/SPNEGO material - to the origin server because the library attaches a Proxy-Authorization header to a request carried over a SOCKS tunnel without first confirming that the destination is an HTTP proxy. Any Java application that configures AHC with an authenticated SOCKS4 or SOCKS5 proxy in those versions is exposed: in the preemptive-authentication path the header is emitted on plaintext HTTP requests to any origin, and in the default non-preemptive path a hostile origin that answers with HTTP 407 triggers ProxyUnauthorized407Interceptor to push the proxy credentials back through the tunnel to that origin. The reporter-assigned CVSS is 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), a confidentiality-only, high-impact issue that requires an authenticated SOCKS proxy configuration to be present; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.

Authentication bypass in pgAdmin 4 (versions 6.2 through 9.17) lets any client that can reach the pgAdmin web interface assume an arbitrary identity - including an existing Administrator account - without supplying a password or any other credential, when the non-default 'webserver' authentication source is enabled. The flaw, a spoofing-based authentication bypass (CWE-290), arises because the WebserverAuthentication class fell back to reading config.WEBSERVER_REMOTE_USER directly from client-controlled inbound HTTP request headers when the WSGI/CGI environment lookup returned nothing, and because headers named with an HTTP_ prefix or hyphens (for example HTTP_X_FORWARDED_USER or X-Forwarded-User) are placed into the WSGI environment by the server itself, satisfying the 'trusted' environment path. Per the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H the attack is unauthenticated and requires no user interaction, so unpatched deployments in webserver-auth mode should be treated as fully compromised by any network-reachable client; no public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV).

Authentication bypass in the Elixir library ash_authentication lets an attacker who operates one federated identity-provider connection of a `dynamic_oidc` strategy be signed in as a local user whose identity row was created through a different IdP connection, because the intended per-connection namespacing of the `strategy` field never persists. Affected are versions 5.0.0-rc.10 through 5.0.0-rc.13 (fixed in 5.0.0-rc.14); the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, so the flaw is network-reachable and unauthenticated in the token-presentation sense, but real-world exploitation is tightly gated: the deployment must use `dynamic_oidc` with more than one identity-provider connection, the attacker must control (or have a trusted operator position on) one of those connections, and must be able to mint tokens with a chosen `sub` claim that collides with a target subject. No public exploit code was identified at time of analysis, and this CVE is not listed in CISA KEV; patch commits are already public, so the exposure window for unpatched, multi-connection deployments is the operational concern.

Address-book poisoning in the @libp2p/peer-store component of js-libp2p (8.0.0 up to, but not including, 12.0.24) allows an unauthenticated remote peer to store attacker-controlled multiaddrs as certified addresses under a victim peer ID, because consumePeerRecord validates only the RecordEnvelope signer and never checks that the signed PeerRecord.peerId matches the signer's own peer ID. The gossipsub Peer Exchange path makes this trivially reachable: it lets the attacker supply its own peer ID as the expectedPeer option while naming a victim in the signed payload, so the poisoned addresses are accepted and persisted for the victim, enabling dial redirection, dial failure, routing manipulation and reachability disruption. The connection upgrade still verifies the remote peer's true identity, so full identity takeover or traffic interception is not achieved; no public exploit identified at time of analysis, and the issue is fixed in peer-store 12.0.24 (CVSS 8.2, AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:L, CWE-290).

Account takeover in Vendure (@vendure/core) prior to 3.7.0 allows an attacker to bind their own external OAuth/social identity to a victim's pre-existing customer account by presenting the victim's email address through a custom AuthenticationStrategy that does not enforce provider-verified email ownership. A successful link exposes the victim's orders, addresses and personal information and permits account changes or order placement as the victim, and the flaw is remotely reachable without authentication per the reported vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 9.1 vendor score). Real-world exposure is materially narrower than that score suggests: only non-default deployments that configure at least one external strategy forwarding an unverified email are affected, and a pre-existing account with the same address must already exist; native email/password-only stores and strategies that always require provider-verified emails are unaffected. No public exploit code was identified at time of analysis and there is no CISA KEV listing indicating confirmed active exploitation; the issue is fixed in 3.7.0.

Account takeover in AshAuthentication (Elixir/Ash) 4.14.0 through 4.14.x and 5.0.0-rc.10 through 5.0.0-rc.13 lets unauthenticated remote attackers obtain a session for another user's account by linking their own OAuth2 provider identity to an account that was matched on an attribute other than email, and the same upsert rewrites the victim's email to the attacker's address so subsequent account recovery flows reach the attacker. Exploitation is conditional: the application must configure the OAuth2/Auth0/Apple strategy with a register-action upsert_identity that matches existing accounts on a non-email attribute, or use the registration_enabled? false sign-in path where accounts are matched by the sign-in action's read filter, and the attacker only needs control of a provider identity whose email_verified claim is true. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV); vendor patches are available in 4.15.0 and 5.0.0-rc.14.

Privilege escalation and information tampering in Dell OpenManage Server Administrator versions prior to 11.1.0.3 allow a low-privileged authenticated remote attacker to modify data and gain unauthorized access through improper privilege management. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, base 8.1) indicates network reachability with low attack complexity, requiring only low privileges and no user interaction, and resulting in high integrity and availability impact with no confidentiality loss. No public exploit identified at time of analysis.

vm2 versions 3.11.4 through 3.11.6 allow untrusted JavaScript running inside the sandbox to bypass cross-realm registered-symbol filtering and write Node.js internal stream symbols onto host WebStream objects, corrupting host-visible stream state - for example making stream.Readable.isDisturbed() return false for an already-consumed stream, which can defeat host logic that enforces one-shot body consumption or rejects errored streams. Exploitation is unauthenticated per the CVSS vector (PR:N) but requires a non-default setup: the embedder must expose both a host WebStream object and the host stream/web module to sandboxed code, and the host must run a Node.js release that exposes nodejs.stream.disturbed and nodejs.stream.errored on WebStream prototypes (validated on Node.js v25.8.0). Impact is integrity-only, with no host code execution, confidentiality, or availability loss in the reported proof; no public exploit code has been identified at time of analysis, and the flaw is fixed in vm2 3.11.7.

Sandbox escape in vm2 before 3.11.7 allows an attacker who can already execute JavaScript inside the vm2 sandbox to bypass the external package allowlist and cause unauthorized host packages to be loaded and executed in the host context. The flaw is an incorrect authorization check: vm2 uses non-exact substring matching when validating package names against the allowlist, so a colliding package name that contains an allowlisted substring is approved. Exploitation requires the host application to use vm2 for untrusted code and to rely on the external package allowlist as a trust boundary; the CVSS vector indicates PR:L, meaning low privileges are required, and no public exploit or CISA KEV confirmed active exploitation was identified at time of analysis.

Unauthenticated routing-table poisoning in SGLang through 0.5.19 lets any attacker who can reach the prefill bootstrap service in a prefill/decode (PD) disaggregation deployment issue a PUT /route request and rewrite the KV transfer routing table. By supplying arbitrary rank_ip and rank_port values, the attacker redirects decode workers to attacker-controlled endpoints, which yields a denial of service against the serving cluster and discloses KV transfer metadata such as session identifiers and tensor-parallel topology parameters. The flaw is remotely reachable, unauthenticated, and requires no user interaction (CVSS 8.8; CVSS 4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H), but it is conditionally gated: it only applies to the non-default, multi-node PD disaggregation topology where the prefill bootstrap service is network-reachable, so single-node or default deployments are unaffected. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the practical limiting factor is deployment configuration and exposure of the bootstrap port rather than the exploitation technique itself.

Unauthenticated remote attackers can take over arbitrary MobiAPParc accounts by abusing the product's forgotten-password flow, which accepts a predictable, sequential numeric user_id without any proof that the requestor owns the target account, allowing the attacker to set a new password and gain full control of the account. The affected builds are MobiAPParc up to and including 2.28 and up to and including 2.42 (CPE cpe:2.3:a:mobiapparc:mobiapparc:*), and exploitation requires only network reachability of the application - the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H confirms no privileges or user interaction are needed. No public exploit code has been identified at time of analysis and no EPSS or CISA KEV signal is available, so the elevated 8.8 base score should be read alongside the product's limited deployment footprint rather than as evidence of active exploitation.

Unauthenticated attackers can bypass the authentication logic of the miniOrange Headless Single Sign On WordPress plugin at versions up to and including 1.7.0, gaining access as arbitrary users - potentially administrators - with full confidentiality, integrity, and availability impact (CVSS 3.1 9.8). Per the assessed vector (AV:N/AC:L/PR:N/UI:N), exploitation requires no credentials, no user interaction, and no client-side prerequisites against an affected installation; the practical limiting factor is deployment, since this is a niche headless-SSO component with a modest install footprint, and the precise configuration state that triggers the bypass is not described in the advisory. At time of analysis there is no CISA KEV entry and no public exploit identified, so the risk is driven by the severity of the flaw and the ease of the network attack path rather than by observed exploitation. Reported by Patchstack (EUVD-2026-81491).

Unconfirmed accounts can obtain an authenticated session in the AshAuthentication Elixir library, defeating the mandatory email-confirmation gate configured through the password strategy's require_confirmed_with option. The check in AshAuthentication.Strategy.Password.Actions.check_user/2 compares the confirmation attribute against nil with a bare is_nil(Map.get(user, field)), so Ash's %Ash.NotLoaded{} and %Ash.ForbiddenField{} sentinels - returned when the attribute is not selected on the loaded record or is hidden from the current actor by a field policy - are treated as a confirmed value; the check also exists only inside the strategy's Actions module and is not attached to the sign-in/register action itself, so callers that invoke the action directly, including API layers such as AshGraphql and AshJsonApi in the default configuration, skip it entirely. Unauthenticated per the CVSS 4.0 vector (PR:N, with AT:P indicating the target must actually have require_confirmed_with configured), CVSS 9.1, CWE-305 (Authentication Bypass by Primary Weakness); no public exploit identified at time of analysis, and vendor patches are available in 4.15.0 and 5.0.0-rc.14.

Authentication bypass in the AshAuthentication library for Elixir/Ash lets an authenticated attacker who holds a valid sign-in token minted for one Ash resource replay it to be signed in as a user of a different resource, because the JWT 'sub' claim's path segment - the only portion recording which subject the token was issued for - is parsed with URI.parse/1 and thrown away, leaving only the query string. Affected are ash_authentication releases from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14, specifically the Password sign-in-with-token, WebAuthn sign-in and remember-me preparations; the magic-link sign-in path pins the subject against the resource and is not vulnerable. Exploitation is configuration-dependent - it requires two or more authenticated resources whose primary-key field names are identical (for example, both 'id') - and no public exploit code was identified at time of analysis.

An authenticated account-takeover primitive exists in the Elixir library AshAuthentication (ash_authentication) versions 0.5.0 through 4.14.x and 5.0.0-rc.0 through 5.0.0-rc.13: an attacker who can register their own account can replay the confirmation token generated for their own email change against a victim's record, causing the victim's address to be overwritten with the attacker's and confirmed_at to be stamped, after which a routine password reset hands over the account. Exploitation requires the application to use the Confirmation add-on with monitored fields (typically :email), the attacker's own registered account (authenticated, PR:L), and knowledge of the victim's record id (normally a UUID primary key); no action by the victim is required. The confirmation flow the library itself generates is not affected, and no public exploit code has been identified at time of analysis.

Hard-coded credentials in Dell OpenManage Server Administrator (OMSA) managed-node builds before 11.1.0.3 let an unauthenticated remote attacker reach the management service and log in with credentials baked into the product, bypassing authentication entirely (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H). Affected builds are the Windows managed-node patch package and the RHEL 8.10, RHEL 9.4, SLES 15, and Ubuntu 22.04 managed-node packages; exploitation needs only network reachability to the OMSA service, but in practice those interfaces are usually confined to internal management networks, so internal and lateral exposure is the more realistic path. Exploitation status: no public exploit identified at time of analysis (CISA SSVC records Exploitation: none), and EPSS is low at 0.31% (24th percentile); a vendor patch exists in version 11.1.0.3, which removes the condition outright, so the residual risk is driven by unpatched, network-exposed OMSA instances rather than by observed attack activity.

Use of a hard-coded cryptographic key in Dell OpenManage Server Administrator (OMSA) Managed Node builds prior to 11.1.0.3 means an unauthenticated remote attacker who can reach the OMSA management service may recover the statically embedded key shared by every installation and leverage it to bypass authentication for unauthorized access to managed nodes. Affected builds are the Windows managed-node patch and the RHEL 8.10, RHEL 9.4, SLES 15 and Ubuntu 22.04 packages, all of which are fixed in vendor version 11.1.0.3. Exploitation has not been confirmed in the wild (no CISA KEV listing), CISA's SSVC decision framework rates the issue as not automatable with no observed exploitation, and EPSS is low at 0.38% (32nd percentile), while the assessed CVSS of 9.8 reflects full confidentiality, integrity and availability impact if the flaw is successfully abused.

AVideo's PGP second-factor verification can be bypassed, allowing an attacker who already holds a victim's password to complete authentication without ever supplying a valid PGP challenge response. The LoginControl component's verifyChallenge.json.php endpoint compares the submitted response against an uninitialized session variable using PHP loose equality, so a single parameter-less GET request evaluates null == null and marks the login fully authenticated; EUVD tracking places the affected range at AVideo 0 through 29.0. No public exploit code or confirmed active exploitation was identified at time of analysis, but the attack needs only one unauthenticated-to-the-endpoint network request with no user interaction, and the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, making it a high-priority authentication bypass wherever PGP 2FA is the sole remaining protection and credential theft or reuse is feasible.