Authentication Bypass

Access-control bypass in Traefik v3.7.13's Kubernetes Ingress NGINX provider allows unauthenticated remote attackers to reach ssl-passthrough Ingress backends protected by auth-type, auth-url, or whitelist-source-range annotations when a non-TLS entry point is exposed and the attacker knows the Ingress host. The flaw is configuration-gated-affected deployments must use the Ingress NGINX provider with ssl-passthrough Ingresses and a reachable plain HTTP entry point-and the bypass is silent because nothing is logged. No public exploit code or active exploitation is identified in the provided intelligence; upgrade to v3.7.14.

Mutual TLS enforcement in Traefik Proxy can be bypassed, allowing unauthenticated remote clients to reach routers that are configured to require client certificates without presenting one. The flaw affects builds made with the Go 1.27 toolchain, where the request TLS state can be evaluated as nil and the SNI check is consequently skipped; an attacker sends an HTTP/2 request carrying the ':scheme http' pseudo-header over the TLS connection to sidestep certificate validation. Fixed in v2.11.58 and v3.7.14, the issue is exploitable only when an mTLS-protected router actually exists and the binary was compiled with the affected Go version, so default deployments that do not use client-certificate authentication are not exposed; no public exploit code was identified at time of analysis.

Delegated 'Users Admin' accounts in WWBN AVideo before version 29.4.0 can delete, overwrite, or demote full administrator accounts by posting directly to confirmDeleteUser.json.php or userAddNew.json.php with an administrator's user ID, destroying that admin's videos and account in the process. The flaw is a server-side authorization gap: the interface already hides admin-row actions from non-admins, but the endpoints themselves never re-verified that the caller outranks the target, so a crafted request bypasses the cosmetic UI restriction. Exploitation requires an authenticated account holding the Permissions::canAdminUsers() delegated role, so anonymous visitors and ordinary users are not affected; no public exploit code has been identified at time of analysis and no EPSS or CISA KEV signal is present in the available data.

A password change performed through Roundcube Webmail's optional Modoboa password driver can be applied to a different mailbox than the one the user is authenticated as. Only deployments running Roundcube 1.6.0 through 1.6.19 or 1.7.0 through 1.7.4 with the password plugin configured to use modoboa.php are exposed; all other password backends are unaffected, and the attacker must already hold a valid Roundcube login able to invoke the password-change function. No public exploit has been identified at time of analysis, EPSS is low at 0.34% (26th percentile), and there is no CISA KEV listing, but the flaw crosses an authorization boundary with high confidentiality and integrity impact on the mis-targeted account, and fixed releases 1.6.20 and 1.7.5 are available.

Improper access control in Splunk Enterprise 9.4, 10.0, 10.2, and 10.4 allows a low-privileged authenticated user to cross a security boundary and achieve high confidentiality, integrity, and availability impact, making the release a 9.9 severity fix. The flaw was found during Cisco's internal hardening review rather than through external reporting, and the affected ranges are 9.4 before 9.4.16, 10.0 before 10.0.11, 10.2 before 10.2.8, and 10.4 before 10.4.4. No public exploit code has been identified and there is no CISA KEV entry, but vendor patch availability combined with an act_now priority label places upgraded discipline on anyone running an unpatched instance; the trigger is not described in the available sources.

Authenticated Splunk Enterprise users whose roles include the schedule_search capability can use the scheduled search workflow to run risky SPL commands that the platform would normally block, resulting in disclosure or alteration of Splunk data or disruption of Splunk availability. The issue affects Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and is fixed in those releases. The assessed vector requires low privileges (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact; no public exploit identified at time of analysis.

Unauthenticated remote attackers can retrieve a signed Biscuit identity token belonging to any approved, bootstrap-enrolled peer from the Google OSS Agent Mesh (SAM) control plane in versions 0.1.0-alpha.1 through 0.1.0-alpha.8, then replay it as a bearer credential to read mesh authorization policies via /policies and to overwrite advertised router multiaddrs via /routers/lease. The chain requires only the peer_id that the unauthenticated GET /info endpoint discloses, so no credentials or user interaction are needed; a related POST /enroll flaw let any bootstrap-token holder re-fetch another peer's credential. Vendor-released patch: 0.1.0-alpha.9, which enforces cryptographic proof of possession of the enrollment private key on credential-releasing endpoints, adds rate limiting, and validates router lease addresses; no public exploit code or confirmed active exploitation was identified at time of analysis.

Laravel TokenGuard authentication bypass is a genuine high-priority issue, not an inflated CVSS score: unauthenticated attackers can send a crafted non-string credential, such as an array-valued api_token, to routes protected by TokenGuard and, under affected MySQL or MariaDB configurations, be matched to an unintended existing user, enabling account takeover. The flaw affects Laravel Framework before 12.68.0 and 13.x before 13.29.0 and requires the vulnerable guard plus database type-coercion behavior; no public exploit was identified at time of analysis, and vendor-released fixes are available in 12.68.0 and 13.29.0.

Unauthenticated remote attackers can read and tamper with critical data handled by Oracle Java SE through its JSSE (Java Secure Socket Extension) component, rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:N). Affected builds are Java SE 8u511 and 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, plus Oracle GraalVM for JDK 17.0.21 and 21.0.13 and GraalVM Enterprise Edition 21.3.20. Oracle's alert states the flaw is reachable via APIs of the affected component, such as a web service feeding untrusted data into JSSE, and adds a secondary sandbox-escape path for deployments running untrusted code in Java Web Start applications or applets; no public exploit code or active exploitation was identified at time of analysis, but the missing authentication prerequisite and network reachability make this a high-priority patch target rather than a paper finding.

Unauthenticated screen capture in the vCast media streaming service on ViewSonic ViewBoard devices (v0.0.0 through v3.2.715) lets a remote attacker retrieve the display's current screen as JPEG images by sending GET requests to the exposed /snapshot or /screen endpoint. The flaw is CWE-306 missing authentication for a critical function and rates CVSS 7.5, but impact is confidentiality-only (C:H/I:N/A:N) and bounded to content currently rendered on the display. EPSS is 0.29% (20th percentile), no KEV designation is provided in the supplied intelligence, and a public blog reference describing a Vcast/ViewSonic exploitation chain exists but is not verified as working exploit code for this CVE.

Authorization bypass in Jupyter Server gateway mode (2.0.0 through 2.6.0) allows a restricted authenticated user to open an upstream kernel channel and execute code even when the configured Authorizer explicitly denies the kernel execute action, exposing kernel data and credentials and permitting environment modification or disruption. Exploitation requires a non-default GatewayClient.url configuration (or, in 2.6.0 and later, manual registration of the deprecated jupyter_server.gateway.handlers module) plus a valid low-privileged account whose policy denies execute; the default gateway configuration in 2.6.0 and later is fixed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the CVSS 8.8 score reflects high confidentiality, integrity, and availability impact under that gated configuration.

Unauthenticated remote clients can force Apache Traffic Server's origin_server_auth plugin to sign attacker-chosen AWS request headers with the proxy's own AWS credentials, potentially allowing access to or modification of origin resources permitted to that identity. The issue affects ATS 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0, but only installations using the non-default plugin to sign origin requests with AWS credentials are exposed. The vendor rates it High with a CVSS 4.0 base score of 7.0; no public exploit identified at time of analysis.

Unauthenticated network access to the shared proxy cache is possible in Apache Traffic Server deployments that load and enable the experimental tsmemcache plugin, allowing remote attackers to read, modify, and delete cached objects without credentials. Affected releases span 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0; the exposure is gated by the plugin being explicitly enabled and its memcache-style interface being network-reachable, since it is not active in a default installation. No public exploit code or confirmed active exploitation was identified at time of analysis, though the CVSS 4.0 base score of 9.4 and the unauthenticated nature of the interface once exposed make this a high-priority fix for anyone running the plugin.

Response-framing desync in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0) allows a malformed 302 response that should have been rejected as a parse error to pass the rejection path through the Transfer-Encoding: chunked carve-out, so the proxy stores and serves a response that different peers interpret differently. Per the CVSS vector the issue is remote and unauthenticated (AV:N/AC:L/PR:N/UI:N, scope changed, I:H/C:L), enabling cache poisoning and response-framing desync against deployments acting as caching or forwarding proxies. No public exploit code or CISA KEV entry is associated at time of analysis; the practical precondition is that a suitable malformed upstream response actually traverses the proxy. Fixed versions 9.2.16, 10.1.5, and 10.2.1 are published by the vendor.

Unauthenticated remote attackers can take full administrative control of Apache Pulsar Manager 0.3.0 and later by creating an administrator account through an endpoint that remains reachable after initialization, and every account has effective full privileges. In all versions, the manager proxies requests to the Pulsar admin API without enforcing its own authentication and can attach its configured Pulsar credential to a requester-chosen destination, allowing unauthenticated users to perform permitted admin operations and steal the credential. No public exploit code was identified at time of analysis, but the product is retired, unsupported, and will not receive fixes, so exposure persists until deployments are removed.

Apache Pulsar 2.8.1 through 4.0.13 and 4.1.0 through 4.2.4 can grant an authenticated low-privileged user the proxy's full privilege set - including superuser and tenant-admin rights - on the broker admin REST API, the functions worker, and the binary protocol when their requests are relayed by a Pulsar proxy. Two distinct weaknesses in the proxy-to-broker principal check (CWE-863) are involved: the original principal is authorized with the proxy's authentication data, letting MultiRolesTokenAuthorizationProvider or a custom data-driven provider expand the caller's roles to every role in the proxy's token, and a separate tenant-admin check succeeds whenever the proxy role itself is an admin of the tenant, even under the default provider. No public exploit code has been identified at time of analysis; exposure is limited to deployments that use the multi-role token provider or a data-driven custom provider, or that list a proxy role as a tenant admin.

Missing authorization in Apache Pulsar's shadow topic feature allows an authenticated tenant administrator to bind a topic in their own tenant to a persistent topic in another tenant through the PULSAR.SHADOW_SOURCE property, exposing retained messages and enabling destructive retention or deletion of the source topic's ledgers. This affects shadow-topic-capable releases before the fixed 4.0.14 and 4.2.5 versions under the default authorization provider, and no public exploit was identified at time of analysis.

Session token replay in the WebFig management interface of MikroTik RouterOS (through 7.24.5) lets an attacker who already possesses a captured administrator session token bypass authentication and gain persistent administrative access, because tokens stay valid across newly negotiated ECDH sessions until the device's login store is explicitly cleared. The 9.1 CVSS v4 score reflects high confidentiality and integrity impact, but its AC:H rating is meaningful: the attacker must first obtain a valid token out-of-band, for example through the unfixed transport-layer exposure described in CVE-2025-61481, and no user interaction is needed once a token is held. No public exploit identified at time of analysis and no CISA KEV entry exists; devices whose WebFig interface is not reachable from untrusted networks are not realistically exposed.

Local privilege escalation in NoMachine allows an attacker who already has low-privileged code execution on the host to abuse predictably generated Redis database credentials and execute arbitrary code in the context of the service account. The flaw is CWE-331 insufficient entropy in the authentication mechanism for NoMachine's bundled Redis database, rated CVSS 7.8 with a local vector requiring low privileges but no user interaction. The supplied intelligence did not include a CISA KEV entry or public exploit code, so no public exploit was identified at time of analysis; risk is bounded because an initial local foothold is mandatory and no remote network vector exists.

Unauthenticated network access to D365 F&O MCP Server instances prior to version 1.11.0 exposes indexed proprietary X++ source code and metadata through the /mcp JSON-RPC endpoint. The officially documented Azure one-click deployment (infrastructure/azuredeploy.json and infrastructure/main.bicep) defaults the optional apiKey parameter to an empty string and passes it into the App Service API_KEY setting; with that value empty, src/middleware/apiKeyAuth.ts lets requests through without authentication while src/index.ts binds the listener to 0.0.0.0, so any deployer who leaves the key blank and adds no network restrictions or upstream authentication publishes the server to the internet. Attackers can then invoke read/search tools (search, get_object_info, batch_get_info, extension_info, security_info, find_references, find_event_handlers) to harvest business logic, extension and event-handler wiring, and security-role and privilege structure; the CVSS 3.1 score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) matching CWE-306, and no public exploit was identified at time of analysis.

Local command execution in Cisco Snort 3 allows an authenticated low-privileged user to run arbitrary commands as the Snort process user by connecting to the unauthenticated control channel socket. This CWE-306 missing authentication flaw is rated CVSS 7.8 (High); exploitation requires local access to the host and the control socket to be enabled, and no public exploit has been identified at time of analysis.

Local access-control bypass in Cisco Unified Communications products allows an authenticated low-privileged user or local session holder to gain high confidentiality, integrity, and availability impact, with scope change beyond the vulnerable component. The CVSS 3.1 score is 8.8, but the vector is AV:L/PR:L, so exploitation requires existing local access and valid low-privilege credentials rather than a remote unauthenticated path; no public exploit or CISA KEV active exploitation is identified. Affected products include Cisco Emergency Responder, Prime Collaboration Deployment, Unified CM, Unified CM IM&P, Unified CM SME, and Unity Connection, and Cisco hardening releases are available via advisory cisco-sa-voice-hardening-twgbH9e3.

Authentication bypass in Cisco Unified CM and related Cisco collaboration products - Emergency Responder, Unified CM IM&P, Unity Connection, Prime Collaboration Deployment, and Unified CM SME - allows remote, unauthenticated attackers with low complexity and no user interaction to defeat authentication and potentially achieve full confidentiality, integrity, and availability impact (CVSS 9.8 Critical, CWE-287). The flaws were found in an internal Cisco review and fixed through hardening releases; no public exploit code or confirmed active exploitation was identified at time of analysis. Practical risk is tempered by exposure: these telephony and collaboration servers typically sit on internal or management networks rather than the public internet.

Unauthenticated remote command execution as root affects Cisco Expressway Series (Expressway-C and Expressway-E) deployments that expose the database service. The flaw combines reusable persistent cookies with a failure to validate client certificates when clustering TLS Verify Mode is set to Enabled, so an attacker in possession of the cookies can connect to the database service and invoke RPC commands to run arbitrary OS commands as root. The CVSS 3.1 score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); no public exploit code was identified at time of analysis, and exploitation requires network reachability to the database and clustering service.

Incorrect authorization in the COM administration API of hMailServer 6.3.4 through 6.3.6 lets a credential holding the serveradmin role *with* an attached domain list - an account an administrator deliberately confined to specific domains - act as full server administrator over COM, and a parallel flaw lets a domainadmin-with-list credential administer domains its list excludes when the COM domain-administrator check is invoked with no domain argument. The result is a privilege escalation from a confined, authenticated (PR:L) administrative account to whole-server control: reading and altering every domain's accounts and mail, renaming or aliasing domains, writing server settings and secrets, and minting additional server-administrator accounts. Exploitation requires local/on-host access to the COM API (via the Control Panel or a script running on the server), only versions 6.3.4-6.3.6 are affected, and serveradmin accounts with no domain list (the intended whole-server administrator) plus help desk, auditor and custom roles are unaffected; no public exploit code was identified at time of analysis and the CVE is not in CISA KEV.

Cross-tenant configuration takeover in hMailServer 6.0.0 through 6.3.6 lets an authenticated user holding only a domain-confined credential - a domain administrator, a scoped account/API key, or a full-scope key issued for named domains - alter mail routing, aliases, and domain settings that belong to other tenants on a multi-tenant server. Missing authorization checks in the REST and COM administration APIs (CWE-862) allow creation of arbitrary domain aliases, renaming domains to unhosted names, setting rule bind-to-address/send-using-route/script-function actions, and pointing a domain's relay host at an address on the server's own network; the script-function rule action executes at delivery, and the COM domain-alias save performs no authorization check at all. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; the vendor released v6.3.7 to address it, so exploitation is a realistic post-authentication risk chiefly for genuinely multi-tenant deployments (CVSS 8.1, PR:L, integrity and confidentiality High).

Privilege escalation in Progressive Robot hMailServer 6.3.4 through 6.3.6 allows an authenticated holder of the manage_roles permission - a full-scope API key issued for named domains or a domain-scoped serveradmin account - to strip a narrowing role assignment from a server-administrator-level account and thereby restore that account to full server-admin authority. Because the credential can also reset that account's password while the narrower role is still in place, the attacker can then sign in as the server administrator and take over mail-server administration. Exploitation is conditionally gated and multi-step (CVSS AC:H) and no public exploit was identified at time of analysis, so this is a genuine but not trivially reachable escalation path.

Authorization bypass in the Nous Research Hermes Agent webhook gateway (builds up to and including 2026.8.19) allows a remote attacker who holds the valid HMAC secret for one webhook route to obtain the toolsets of a different, higher-privileged route. The flaw is conditional: it only manifests when the gateway is configured with at least two routes and the lower-privileged route's name contains a ':' whose prefix exactly matches the higher-privileged route name (for example 'build' and 'build:external'), because authorization is re-derived by splitting the session key rather than binding to the route that authenticated the request. CVSS is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), EPSS is 0.37% (29th percentile), there is no CISA KEV entry and no public exploit identified at time of analysis; the vendor fixed the issue in release v0.22.2 via PR #115285.

WarehousePG 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 permits any authenticated database role to invoke built-in cluster-expansion functions that perform no privilege check, enabling a low-privileged user to hold catalog locks cluster-wide or repeatedly force session reconnections. The result is a sustained availability outage - DDL, temporary table creation, GRANT and CREATE ROLE are blocked until a superuser terminates the offending session - rather than data disclosure or modification. No public exploit code has been identified at time of analysis, although exploitation only requires valid database credentials and network reachability to the cluster.

Unauthenticated attackers can download private ticket attachments from Trudesk through 1.2.11 because express.static serves the public/ directory ahead of the hasAuth-guarded /uploads mount, so a direct request bypasses the authentication middleware entirely. Successful retrieval requires knowing or guessing a valid ticket MongoDB ObjectId plus the matching attachment filename, which is the main bound on the risk: no credentials or user interaction are needed and default configurations are affected, but the 12-byte ObjectId is not trivially guessable, so blind mass exploitation is impractical and realistic compromise depends on IDs and filenames leaking via URLs, email notifications, or referrers, or on an instance where IDs can be enumerated. No public exploit code and no confirmed active exploitation were identified at time of analysis.

Unauthenticated remote attackers can wipe every group, tag and ticket in Trudesk 1.2.11 and earlier by calling the /debug/populatedb route, which remains registered whenever the NODE_ENV environment variable is unset - an unauthenticated, no-interaction, network-reachable action that destroys data integrity and availability (rated 8.3, CWE-1188) but is gated entirely by that deployment-configuration prerequisite rather than by any credential. The same call reseeds the database with default accounts whose password is 'password', so a successful wipe can additionally hand the attacker a working login to the emptied instance. No CISA KEV activity and no public exploit code were identified at time of analysis, and the overall signal is a credible but conditionally-gated destructive flaw rather than a top-tier emergency.

ZenTao PMS before 22.3 permits authenticated low-privilege users to bypass group-based access controls by invoking any controller method whose name contains 'ajax', potentially exposing sensitive data and administrative actions. The flaw in commonModel::isOpenMethod() treats such methods as open, enabling calls such as task.ajaxGetByID, system.ajaxDBAuthUrl, and admin.ajaxChangeTableEngine to read records, retrieve database credentials, trigger CI jobs, and alter tables. Exploitation requires a valid low-privilege session; no public exploit was identified at time of analysis, and the vendor has released 22.3 with an explicit privilege allow-list. The issue is rated CVSS 4.0 7.1 (High) with high confidentiality impact and low integrity impact.

Privilege escalation in Shopper 2.0.0 through 2.5.x allows an authenticated admin-panel user who holds only the access_dashboard permission to create new administrator accounts or grant elevated permissions by invoking CreateTeamMember::store() or Permissions::togglePermission() directly through /livewire/update. The missing server-side authorization checks make this a genuine privilege-escalation path for low-privilege back-office accounts; upgrading to 2.6.0 adds the required authorize() guards. No public exploit identified at time of analysis, and exploitation requires a valid authenticated session rather than anonymous internet access.

Authentication bypass in Apache bRPC through 1.17.0 lets a remote unauthenticated attacker reach protected non-builtin HTTP endpoints by first sending a builtin HTTP request over the same HTTP/1.1 keep-alive connection. The behavior only applies when ServerOptions.auth is enabled and builtin HTTP services are exposed on the public listener, and exploitation is tied to reuse of that socket. Version 1.18.0 and PR #3308 correct the flaw; EPSS is 0.26% (17th percentile) and no public exploit has been identified at time of analysis, while the source feed assigns an act_now priority for remediation.

Apache IoTDB 2.0.0 through 2.0.11 mishandles identity in its Legacy Pipe receiver: the handshake and sendPipeData handlers execute data loading and deletion under a hardcoded SUPER_USER (root) identity instead of the caller's own. An authenticated account holding SYSTEM-level privileges such as USE_PIPE or MAINTAIN - but deliberately lacking WRITE_DATA or DELETE_DATA on the target databases - can send crafted PipeData messages and have write/delete operations performed as root, fully bypassing the permission model. Integrity and availability of the targeted data are at risk (the assessed vector scores no confidentiality impact), exploitation requires a valid low-privilege login and a reachable Legacy Pipe interface, EPSS is low at 0.26% (16th percentile), and no public exploit has been identified at time of analysis.

Missing authentication for a critical function in Apache IoTDB 2.0.0 through 2.0.10 lets unauthenticated remote attackers reach a high-impact confidentiality, integrity, and availability compromise, reflected by a CVSS score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit has been identified at time of analysis, and EPSS is low at 0.28% (20th percentile), but the act_now priority label and critical severity make timely remediation important. The vendor-released fix is Apache IoTDB 2.0.11.

Unauthenticated remote attackers can bypass authentication in Apache IoTDB 2.0.0 through 2.0.10 through the Thrift RPC service, with high confidentiality, integrity, and availability impact (CVSS 9.8). The vendor fixed the flaw in 2.0.11; no public exploit has been identified at time of analysis and EPSS is low at 0.28%, but the issue carries an act_now priority because default deployments exposing the RPC port are reachable without credentials. The exact bypass mechanism is not described in the available sources.

Improper input validation in Node.js DNS resolution functions lets hostname or address strings containing null bytes reach dns.resolve/dns.lookup, which the 26.12.1 security release fixes by adding explicit null-byte validation of resolve inputs. Node.js 22.x through 22.23.3, 24.x through 24.22.0, and 26.x through 26.12.0 are affected, with the vendor patch shipped in Node.js 26.12.1. The assessed vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H) means unauthenticated remote reach is possible but exploitation is conditional on the target application passing attacker-influenced strings into DNS resolution, and the exact trigger mechanism is not described in the available sources; a public PoC reference exists but is not verified as working exploit code, and there is no CISA KEV listing.

Acronis Cyber Infrastructure (ACI) does not properly enforce authorization in its management/API layer, letting remote attackers disclose sensitive information and manipulate protected resources (CVSS 9.1, AV:N/AC:L/PR:N/UI:N, C:H/I:H). The vendor vector specifies PR:N, so no authentication, user interaction, or special configuration is documented as required; exposure is mainly bounded by whether the ACI management interface is reachable from untrusted networks. Affected deployments are those running builds earlier than 6.0.1-112, 6.1.1-64, and 6.2.1-71. No public exploit code and no CISA KEV entry were identified at time of analysis, so active exploitation is not confirmed.

miniOrange 2FA versions 6.2.9 to before 6.3.1 permit an attacker who already knows a victim's WordPress password to add an attacker-controlled passkey during a pending passkey login, bypassing the second factor on accounts that already have a passkey. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N, so exploitation is authenticated (PR:L) and depends on a timing/state window (AC:H), with high confidentiality and integrity impact but no availability impact; publicly available exploit code exists, while no CISA KEV entry was supplied.

Missing authorization in Backup and Staging by WP Time Capsule before 1.22.28 allows an authenticated Subscriber on a WP Time Capsule staging site to invoke the staging-to-live deployment handler and overwrite the linked live site's database and configuration, potentially taking it offline. Exploitation is conditional on the plugin's staging-to-live workflow being configured with a separate live site, and publicly available exploit code exists. The vendor-released fixed version is 1.22.28.

Improper authorization in Apache bRPC before 1.18.0 lets remote attackers reach builtin services such as brpc.vars and hotspots through the public port over protobuf-based protocols, disclosing runtime metrics, flags and profiler data that operators intended to expose only on the internal port. Only deployments that use ServerOptions.internal_port (or otherwise rely on it to gate builtin/Tabbed services), expose the public port to untrusted networks, and enable at least one protobuf-based protocol (baidu_std, hulu_pbrpc, sofa_pbrpc, public_pbrpc, nshead_mcpack, nova_pbrpc, ubrpc2pb) are affected; the HTTP/h2 dispatch path already enforced the restriction. The impact is confidentiality-only: the upstream score is 7.5 with C:H, while our assessment is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), reflecting limited information disclosure rather than full compromise. No CISA KEV entry and no public exploit identified at time of analysis; EPSS is 0.18% (7th percentile), and the internal priority label is this_week.

Apache bRPC versions before 1.18.0 skip authentication for streaming RPC traffic: frames handed to the streaming parser (ParseStreamingMessage) never traverse InputMessenger's authentication hook, so a remote unauthenticated peer can exchange streaming frames with a server that is configured with an Authenticator. A second weakness binds a server-accepted stream lazily to the first frame carrying its id, allowing a foreign connection that knows or guesses a stream id to inject frames from a different socket. Only servers that both configure an Authenticator and serve streaming RPC to an untrusted network are exposed; the assessed vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L, and no public exploit has been identified at time of analysis (EPSS 0.26%, percentile 17), although the vuln.today decision label is act_now and severity signals diverge sharply.

Authentication bypass in Apache bRPC before 1.18.0 lets remote unauthenticated attackers reach ordinary authenticated services when a server configures both ServerOptions.auth and ServerOptions.internal_port. Because the built-in-service exemption on internal_port latches the first successful check for the lifetime of a connection, a single request such as GET /status to internal_port opens the door for every later request on that same connection, which is then dispatched without any credential verification (CVSS 9.1, CWE-287, unauthenticated per the PR:N vector). Exposure is configuration-dependent: internal_port is meant as an internal management port, and servers without an Authenticator or that expose only built-in/Tabbed services there are unaffected; there is no CISA KEV entry and no public exploit identified at time of analysis, with EPSS at 0.33% (24th percentile), yet the source is prioritized act_now.

Apache bRPC before 1.18.0 allows remote attackers to bypass path-based access-control rules enforced by a front proxy, because its HTTP method dispatcher collapses paths containing empty segments (for example //flags or /flags//) to the same builtin method as /flags, and its HTTP/2 handling does not validate the :path pseudo-header. The issue is exploitable without credentials but is conditional: a front proxy or gateway must be making ACL decisions on the literal request path while forwarding HTTP or HTTP/2 traffic to the bRPC server, so standalone bRPC deployments without such a proxy ACL are not meaningfully exposed. No public exploit was identified at the time of analysis, and EPSS is low at 0.21% (11th percentile); vendor fixes are available in 1.18.0 and PR 3512.

Authentication bypass and SYSTEM-level command execution in Best Practice Software Bp Premier before 1.14.1.1128 stem from a hardcoded, installation-wide Microsoft SQL Server sysadmin password, allowing unauthenticated remote attackers with TCP access to the database to bypass application authentication and execute operating system commands as SYSTEM under the documented default SQL service configuration. The credential is shared across all installations and cannot be changed without breaking the application, so no in-product hardening is possible pending the vendor patch. No public exploit code or CISA KEV entry was identified at time of analysis, but the main constraint is database reachability: deployments exposing SQL Server port 1433 or attackers already on the clinic LAN can exploit it.

Missing authentication in the HKUDS Vibe-Trading FastAPI server (pip package vibe-trading-ai 0.1.0 through 0.1.6) lets unauthenticated remote attackers reach every endpoint guarded by Depends(require_auth), because require_auth() returns immediately when API_AUTH_KEY is unset - which is the shipped default in agent/.env.example. Attackers can POST to /sessions/{id}/messages to drive the agent's BashTool toward shell command execution, upload .py/.sh/.yaml files via /upload, read other users' session histories, and recover partial API keys via _mask_secret(); because the shipped Dockerfile has no USER directive and docker-compose publishes 0.0.0.0:8899, any command executed lands as root inside the container. Exploitation matches the assessed vector AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact; the full chained RCE demonstration additionally requires the operator to have configured a working LLM API key so the tool-call loop can complete, while the unauthenticated API surface, file upload, history read and partial key disclosure work without it. No CISA KEV listing and no public exploit code identified at time of analysis, though the vendor advisory publishes detailed reproduction steps; fix in 0.1.7.

Integrity bypass in adm-zip through 0.6.0 allows an unauthenticated attacker who supplies a crafted ZIP to a validate-then-extract application to have getEntry() approve one duplicate entry while extractAllTo() writes a different entry's bytes to disk. The flaw is conditional: the consuming application must inspect a named entry's content via getEntry() and then extract the same archive, and the archive must contain duplicate entry names with the relevant ordering; applications that only extract without a getEntry-based content check are not affected. Public proof-of-concept code is present in the upstream advisory, and no CISA KEV active-exploitation listing is associated with this CVE.

Trigger.dev's dashboard run replay endpoint lets an attacker who knows or enumerates a run friendlyId replay another organization's task run into an environment of the attacker's choosing, potentially exposing task payloads and executing the task with the victim's secrets. The vendor CVSS 4.0 score is 8.3 (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N), with an independent CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N; the CVSS PR:N designation suggests unauthenticated access, although the GHSA's 'any authenticated user' wording means authentication requirements are not definitively confirmed. Publicly available exploit code exists (a PoC POST request is included in the GHSA), but no CISA KEV entry or confirmed active exploitation appears in the supplied data.

Missing authentication in the Trigger.dev CLI MCP server (cli-v3 3.0.0 through 4.5.3) exposes the /sse and /messages endpoints to adjacent-network attackers or malicious web pages while a developer runs 'trigger dev --mcp'. An unauthenticated attacker able to reach the bound port can issue MCP tools/call requests that use the developer's locally stored access token to trigger tasks, cancel runs, list runs, and retrieve run logs; exploitation is limited to active MCP-mode development sessions, and no public exploit was identified at time of analysis.

Unauthenticated remote attackers can bypass Socket.IO authentication on self-hosted Trigger.dev webapps before 4.5.4 because the /coordinator namespace authenticates against a source-published default COORDINATOR_SECRET ('coordinator-secret') that is absent from the self-hosting docs, .env.example, and Helm values, so operators who never overrode it ship the published value. With that value an attacker can emit READY_FOR_EXECUTION to pull a run's decrypted environment variables (V1/marqs deployments, provided an internal runId is known) or send TASK_RUN_FAILED_TO_RUN, TASK_RUN_COMPLETED, CHECKPOINT_CREATED and similar events to tamper with arbitrary runs. No public exploit code or confirmed active exploitation was identified at time of analysis; exposure is confined to self-hosted deployments left on the default secret, and Trigger.dev Cloud is not implicated by this self-host default-configuration issue.

Authentication bypass in Trigger.dev self-hosted v4 deployments (npm trigger.dev <=4.5.5) allows unauthenticated attackers to forge magic-link tokens and log in as any email address when the default MAGIC_LINK_SECRET from hosting/docker/.env.example is still in use. Publicly available exploit code exists; successful exploitation can expose or modify tenant data, and may escalate to full infrastructure compromise because default Postgres, Redis, and ClickHouse credentials are reachable from runner containers on the same Docker network. The issue is limited to Docker Compose deployments that never rotated the example secrets and left WHITELISTED_EMAILS unset; the hosted SaaS and instances with regenerated secrets or an email allowlist are not affected.

Trigger.dev self-hosted and cloud deployments through version 4.7.6 expose a supervisor workload API endpoint (attempts/start) that performs no ownership check, letting a caller act on runs and snapshots belonging to other deployments. Exploitation is not anonymous: an attacker must already hold a legitimate low-privilege run/snapshot pair and must reach the supervisor over an adjacent network segment, after which they can read resolved environment variables and run JWTs or start, complete, and suspend other tenants' runs. There is no public exploit code or confirmed active exploitation (no CISA KEV), and the vendor advisory GHSA-jc26-22qp-cgqj is the authoritative reference; risk concentrates in multi-tenant or hosted installations where untrusted workloads share a supervisor, while single-tenant self-hosted setups with no third-party workloads are materially less exposed.

Trigger.dev deployments before 4.6.2 return environment-wide S2 stream credentials to any caller who presents a public token with session write access and initializes session input, letting that narrowly scoped token reach every stream in the environment. With the leaked credential, an attacker talks to the S2 storage API directly to append to, create, or trim other sessions' and runs' streams, forging job output or permanently deleting records. Integrity and availability are both assessed high while confidentiality is unaffected, and exploitation is gated on possession of a valid session-write-capable public token (authenticated, PR:L) with no public exploit code or CISA KEV entry identified at time of analysis.

Cross-organization schedule deletion and disabling in Trigger.dev before 4.5.6 allows authenticated users with their own project schedule route to target another organization's IMPERATIVE cron schedule by supplying the victim schedule's friendlyId to delete or disable actions. The flaw is a CWE-639 authorization bypass/IDOR in DeleteTaskScheduleService and SetActiveOnTaskScheduleService, which resolve the friendlyId without scoping it to the caller's organization; exploitation requires authentication and knowledge or enumeration of the victim's friendlyId, and impact is limited to schedule integrity/availability with no data disclosure. No public exploit was identified at the time of analysis, and CISA KEV does not list this CVE.

Trigger.dev before 4.6.0 fails to enforce organization scoping in the waitpoint token wait endpoint, allowing an authenticated attacker who holds any valid secret API key to supply another organization's run ID and make that run block indefinitely on a waitpoint the victim cannot complete; the same path can also inject resume data into the targeted run. This is an IDOR-class authorization flaw (CWE-639) affecting default multi-tenant deployments prior to 4.6.0, with the greatest practical impact on shared instances where keys from one organization can reference another organization's runs. No public exploit identified at time of analysis.

Improper authorization in Trigger.dev 4.5.0 through 4.6.1 lets authenticated holders of a valid public session token obtain presigned S3 write URLs and overwrite their own session's durable chat snapshot, forging the agent's conversation history. The PUT snapshot-url session endpoint lacks a secret-key-only authorization check, and the affected range ends before 4.6.2. No public exploit code has been identified at the time of analysis, and the independent assessment limits impact to the token holder's own session with no confidentiality, availability, or cross-tenant effect.

Trigger.dev prior to 4.7.0 fails to enforce ownership checks on the parentRunId supplied to batch-creation endpoints, allowing authenticated holders of unrestricted environment API keys to suspend, indefinitely block, or inject errors into runs they do not own, including cross-organization or production runs on shared deployments. The flaw is rated CVSS 7.2 and is an IDOR-style missing authorization issue (CWE-639); no public exploit code or CISA KEV entry was identified at time of analysis. Risk is concentrated in multi-tenant or shared instances where foreign run IDs are reachable, and is materially lower in isolated single-tenant deployments.

ArcadeDB deployments running any version before 26.10.1 can be coerced into executing arbitrary operating-system commands by any authenticated user who can reach the POST /api/v1/command/{database} endpoint, provided the Groovy scripting engine is enabled on the instance. The root cause is a missing authorization check in GremlinQueryEngine.command(), which means role restrictions are never enforced for Gremlin-submitted Groovy code, so even an account holding the read-only 'reader' role can elevate from query access to full server-process code execution. There is no indication of active exploitation in the wild and no public exploit code identified at time of analysis, but exploitation is straightforward for an insider or anyone holding low-privilege credentials, and the attack surface is limited only by whether the Groovy engine is turned on and the API is network-reachable.

Cache aliasing in vLLM before 0.31.0 allows authenticated users of a shared deployment to receive another request's cached processed media or reuse first-block KV cache state by supplying colliding EXIF ImageID or cache_salt values. The flaw is only exploitable when image-processing and/or prefix-KV caches are shared across distinct callers or tenants and the attacker can control the relevant cache-key inputs; single-tenant or isolated-cache deployments have no cross-request target. No public exploit identified at time of analysis; the vendor CVSS 4.0 score is 7.1, and the independent assessment rates confidentiality impact high with limited integrity impact.

Remote unauthenticated takeover of Oracle Essbase 21.8.3.0.0 is possible through the TCP-exposed Security component, with CVSS 3.1 scoring 9.8 and high confidentiality, integrity, and availability impact. Exploitation needs only network reachability to the affected service, no credentials, and no user interaction, so internet-facing or broadly reachable Essbase deployments carry the greatest risk. No public exploit code or CISA KEV entry was identified in the supplied intelligence at time of analysis.

Authenticated low-privileged attackers with network access to Oracle Essbase 21.8.3.0.0's T3/IIOP listeners can achieve full takeover of the Essbase instance, with scope change allowing significant impact on additional products. The vulnerability carries a CVSS 3.1 base score of 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) and is considered high priority; no public exploit identified at time of analysis, and no CISA KEV confirmation was provided. Exploitation is gated by reachability to the T3/IIOP management protocols and possession of a low-privileged account.

Low-privileged authenticated users of Oracle Essbase 21.8.3.0.0 can reach beyond their assigned privilege boundary through the Security component over HTTP and read critical data they should not be able to see, including data exposed in downstream products because the vulnerability crosses a security scope boundary. Oracle scores this 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N): confidentiality-only, with no integrity or availability impact, and exploitation requires a valid low-privileged account rather than being unauthenticated. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, so risk is concentrated in internet- or network-reachable Essbase deployments where low-level credentials are broadly distributed.

Remote takeover of Oracle Essbase 21.8.3.0.0 is possible for low-privileged authenticated attackers with HTTP network access, due to a security flaw in the product's Security component. Successful exploitation can fully compromise confidentiality, integrity, and availability and, because of the scope change, may extend impact to additional connected products. This is a high-priority vulnerability; no public exploit identified at time of analysis, and the CVSS 3.1 base score is 9.9.

Low-privileged authenticated users can exploit the Federated Partitions component in Oracle Essbase 21.8.3.0.0 over HTTP to obtain broad read access to critical Essbase data, limited unauthorized insert/update/delete capability, and a partial denial of service. The critical 9.1 CVSS score is driven mainly by the scope change (S:C) and high confidentiality impact (C:H), meaning successful exploitation can also affect resources in connected products beyond Essbase itself. Attack complexity is low and no user interaction is required, but the flaw is not anonymously reachable - an attacker must already hold a valid low-privileged Essbase account (PR:L). No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied with the source data.

Authenticated low-privileged attackers with HTTP network access to Oracle Essbase 21.8.3.0.0 can exploit a flaw in the Security component to read critical Essbase-accessible data, make limited unauthorized updates, inserts, or deletions, and cause a partial denial of service. The CVSS 3.1 score is 9.1 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L), with the scope change indicating that successful exploitation can significantly affect additional connected products beyond Essbase. No public exploit identified at time of analysis; exploitation requires valid low-privileged credentials and reachability to the HTTP interface.

Critical data exposure and limited data modification in Oracle Essbase 21.8.3.0.0's Web Platform are possible for an authenticated low-privileged attacker with HTTP network access. The CVSS 3.1 score is 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), with scope change extending impact to additional products; no public exploit identified at time of analysis, and the supplied 'Authentication Bypass' tag conflicts with the vector's PR:L requirement.

Full takeover of Oracle Essbase 21.8.3.0.0 is achievable by a low-privileged, authenticated attacker reaching the Essbase Web Platform over HTTP, with Oracle's scope-change rating (S:C) warning that a compromise may significantly impact additional products beyond Essbase itself. Oracle characterizes the flaw as difficult to exploit (AC:H), so success depends on conditions outside the attacker's control rather than being reliably repeatable, and the prior-authentication requirement (PR:L) is the main limiting factor. No public exploit was identified at time of analysis, and the issue is addressed through Oracle's October 2026 Critical Patch Update.

Successful exploitation of Oracle Essbase 21.8.3.0.0 could allow a remote, unauthenticated attacker with TCP network access to take over the Essbase service, with high confidentiality, integrity, and availability impact. Oracle rates the issue difficult to exploit (CVSS 8.1, AC:H), and the specific precondition is not disclosed; no public exploit was identified at time of analysis. Realistic exposure depends heavily on whether the Essbase TCP listener is reachable from untrusted networks.

Unauthenticated remote attackers can exploit an authentication bypass in the Security component of Oracle Essbase 21.8.3.0.0 over HTTP, gaining unauthorized access to critical data and limited ability to modify it, with potential impact extending to connected Oracle products due to a scope change. The vulnerability carries a CVSS 9.3 base score; no public exploit identified at time of analysis, and no CISA KEV entry confirms active exploitation. Risk is highest for instances with internet-facing or otherwise network-reachable Essbase HTTP services, while segmented or access-restricted deployments are less exposed.

Oracle Essbase 21.8.3.0.0 exposes an HTTP-reachable Security component flaw that unauthenticated remote attackers can use to read a subset of data, modify or delete some records, and partially disrupt availability. CVSS 3.1 rates it 7.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L), with no public exploit identified at time of analysis. The practical risk is highest where Essbase HTTP services are reachable from untrusted networks, because no authentication, user interaction, or special conditions are required.

Low-privileged authenticated users of Oracle Essbase 21.8.3.0.0 can exploit the Security component over HTTP to obtain unauthorized access to critical data, potentially extending beyond Essbase because of a scope change. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N: no user interaction is needed, but the attacker must already hold a valid low-privilege account and network access to the Essbase service. No public exploit was identified at time of analysis, and the 'Authentication Bypass' tag should not be read as allowing fully unauthenticated access given PR:L.

Oracle Essbase 21.8.3.0.0 (Security component) permits a low-privileged authenticated user to take full control of the Essbase deployment over HTTP, with high confidentiality, integrity, and availability impact and a scope change that can extend compromise to integrated products. Exploitation requires network reachability to the Essbase HTTP interface plus valid low-level credentials (CVSS PR:L, AC:L, UI:N), so anonymous attacks are not indicated - the attacker must already hold some account on the server. Our assessment rates this as a genuine high-priority vulnerability rather than a high-CVSS-but-low-risk paper tiger; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis. No CWE was published, so the precise root-cause class is not confirmed from available data.

Oracle Essbase 21.8.3.0.0 contains an easily exploitable flaw in its Security component that lets a low-privileged, network-positioned attacker take over the Essbase deployment over HTTP. The CVSS 3.1 base score is 9.9 with scope change (S:C), meaning a compromise is not contained to Essbase and can significantly affect other products sharing the deployment. Authentication requirements are confirmed from the vector as low-privileged (PR:L) with no user interaction (UI:N); no public exploit code or CISA KEV active exploitation is identified in the available data.

Oracle Essbase 21.8.3.0.0 exposes critical data to any holder of a valid low-privilege account, who can reach the Security component over HTTP and read information far beyond their intended authorization - up to all data the Essbase instance can access. The scope-change rating means the disclosure is not confined to Essbase itself and can extend into other connected Oracle products, making this an elevated-priority integrity-of-confidentiality issue rather than a CVSS-inflated one. Exploitation requires authenticated network access (CVSS PR:L, AV:N, AC:L, UI:N), so the practical barrier is obtaining or abusing a low-privilege account; no public exploit code has been identified at time of analysis and the flaw is not in CISA KEV.

Unauthenticated network attackers can achieve full takeover of Oracle Essbase 21.8.3.0.0 by reaching the product's WebLogic T3 and/or IIOP remoting listeners, with complete confidentiality, integrity, and availability impact (CVSS 3.1 base 8.1, C:H/I:H/A:H). The flaw sits in the Security component and is rated difficult to exploit (AC:H), meaning the attacker must satisfy conditions outside their direct control beyond simply reaching the port; no user interaction is required (PR:N/UI:N). There is no public exploit code and no confirmed active exploitation at time of analysis, but exposure is real wherever T3/IIOP is reachable from untrusted networks - the October 2026 Oracle Critical Patch Update is the only fix path identified in the available data.

Oracle Essbase 21.8.3.0.0 contains a confidentiality flaw in its Security component that lets a low-privileged, authenticated attacker reach critical data over the HTTP interface, with CVSS 3.1 scoring it 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N). Because the scope is changed, the exposure can extend past the Essbase instance to products wired into it, so stolen data may include far more than the attacker's own account should see. Our assessment rates this a genuine mid-tier priority rather than an emergency: the deciding constraint is that a valid low-privilege Essbase account is required, so no public exploit code or confirmed active exploitation was identified at time of analysis.

Unauthenticated network attackers can read critical data and make limited unauthorized changes in Oracle Agile Product Lifecycle Management for Process 6.2.4 through the Product Quality Management component. The flaw is remotely reachable over HTTP with low attack complexity, no credentials, and no user interaction, yielding high confidentiality impact and low integrity impact; availability is not affected. No public exploit code or CISA KEV entry was identified at time of analysis, so this is a high-priority patch item rather than a confirmed active exploitation event.

Oracle Agile Product Lifecycle Management for Process 6.2.4 exposes critical data to unauthenticated remote attackers through an HTTP-reachable Product Quality Management component, allowing high-impact confidentiality and integrity compromise with a CVSS 3.1 score of 9.1. The flaw is assessed as remotely exploitable with no privileges or user interaction, but no CISA KEV listing and no public exploit code were identified at time of analysis. No EPSS score or SSVC decision data was supplied, so exploitation probability is not quantified.

Oracle Agile Product Lifecycle Management for Process 6.2.4 exposes an unauthenticated HTTP attack surface in its Product Quality Management component that permits high-impact confidentiality and integrity compromise, with CVSS 3.1 scored at 7.4 (HIGH). Per Oracle's advisory, exploitation is rated difficult (AC:H) because success requires conditions outside the attacker's control, but no privileges (PR:N) or user interaction (UI:N) are needed once those conditions align, and there is no availability impact. No EPSS score, CISA KEV listing, or public exploit code was identified at time of analysis, so exposure is driven by whether the PLM HTTP interface is reachable from untrusted networks rather than by observed attack activity.

Oracle Agile Product Lifecycle Management for Process 6.2.4 contains a remotely reachable, unauthenticated weakness that lets an attacker who first persuades a legitimate user to open a crafted link or view attacker-controlled content gain unauthorized creation, deletion, and modification of critical PLM data alongside full read access to it, with impact potentially extending into connected products because the CVSS scope is changed (base 9.3). The attacker cannot complete the chain alone - the vector requires that second user's interaction (UI:R), and availability is unaffected (A:N) - so exposure is concentrated in internet- or intranet-reachable 6.2.4 deployments whose users can be socially engineered. No public exploit code was identified and the issue is not confirmed actively exploited (not in CISA KEV) at the time of analysis, so the 9.3 severity reflects theoretical impact rather than observed attacks.

Authenticated low-privileged attackers can achieve full takeover of Oracle REST Data Services in versions 24.2.0 through 26.2.2 by sending crafted HTTP requests to the ORDS interface, with high impact to confidentiality, integrity and availability (CVSS 8.8). Oracle rates the flaw easy to exploit - no user interaction, no race condition and no non-default configuration is required - so the practical barriers are simply any valid low-privilege ORDS account plus network reachability of the ORDS listener. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so active exploitation is not confirmed; realistic risk is concentrated in internet-exposed ORDS deployments that issue accounts broadly.

Oracle BI Publisher exposes sensitive data to unauthenticated network attackers through its Web Server component, affecting versions 8.2.0.0.0, 12.2.1.4.0, and 26.01.0.0.0. Successful exploitation yields complete confidentiality impact over HTTP with no user interaction, matching a CVSS 7.5 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. No public exploit code or confirmed active exploitation was identified at time of analysis.

Privilege escalation and application takeover in Oracle Agile Product Lifecycle Management for Process 6.2.4: an authenticated attacker holding only low-privileged credentials can reach the Product Quality Management component over HTTP and, if the difficult exploitation conditions are met, gain full control of the application with high confidentiality, integrity and availability impact. The flaw is rated CVSS 3.1 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), and the high attack complexity points to a narrow, condition-dependent trigger rather than a straightforward request. No public exploit code or confirmed active exploitation was identified at time of analysis, and only version 6.2.4 is listed as affected in Oracle's October 2026 Critical Patch Update.

Adjacent-network attackers can achieve takeover of Oracle Business Intelligence Enterprise Edition 8.2.0.0.0 and 26.01.0.0.0 through a high-complexity Platform Security flaw, with no authentication or user interaction required; CVSS 8.3 reflects high confidentiality, integrity, and availability impact plus scope change. Oracle rates exploitation as difficult and requires access to the physical or adjacent communication segment attached to the OBIEE host, not the open internet. No public exploit was identified at time of analysis.

Unauthenticated network attackers can access critical data and make limited unauthorized changes in Oracle Agile Product Lifecycle Management for Process 6.2.4 through the Product Quality Management component, yielding a CVSS 3.1 score of 8.2 with high confidentiality and low integrity impact. The CVSS vector indicates network reachability to the HTTP interface with no credentials, user interaction, or special configuration required, though real-world risk depends on whether the application is internet-facing or only reachable from trusted internal networks. No public exploit identified at time of analysis; this is a credible mid-to-high priority for organizations running the affected version.

Unauthenticated remote attackers can read critical data from Oracle WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 over HTTP, with the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N, base 7.5) indicating a low-complexity, no-prerequisites confidentiality breach with no integrity or availability impact. The flaw is classified by the reporter under an authentication-bypass tag, meaning access controls on a WebCenter Sites interface can be sidestepped rather than brute-forced, exposing all data the application can reach. No public exploit code was identified at time of analysis and the CVE is not in CISA KEV, so there is no confirmed active exploitation, though the combination of unauthenticated network reachability and high confidentiality impact makes this a genuine priority for internet-facing deployments rather than an inflated score.

Authenticated takeover of Oracle Agile Product Lifecycle Management for Process 6.2.4: a low-privileged attacker with HTTP network access to the Product Quality Management component can compromise confidentiality, integrity, and availability at high impact (CVSS 3.1 base 8.8, vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The PR:L authentication prerequisite is the main limiting factor - an attacker must already hold or obtain a valid low-privileged account, so this is not anonymous exploitation, but once inside no user interaction or special configuration is required. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); the intelligence signals are sparse, resting on a single Oracle CPU reference with no CWE mapping or CPE data.

Unauthenticated attackers with network reach to Oracle Business Intelligence Enterprise Edition 12.2.1.4.0 can potentially achieve full takeover of the platform through the BI Foundation component over HTTP, with high impact across confidentiality, integrity and availability (CVSS 3.1 base 8.1). The high attack complexity reflects Oracle's own 'difficult to exploit' classification, meaning success hinges on timing, state or environmental preconditions outside the attacker's direct control rather than a single reliable request. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, so practical risk is gated primarily by whether the BI HTTP interface is exposed to untrusted networks.

Oracle BI EE 8.2.0.0.0 and 12.2.1.4.0 can be taken over through a low-complexity Platform Security flaw that an unauthenticated attacker triggers after obtaining interactive logon access to the host and persuading another user to perform an action. The local attack path (AV:L) and user-interaction requirement (UI:R) keep it from being remotely wormable against default internet-facing deployments, despite high confidentiality, integrity, and availability impact and a 7.8 CVSS score. No public exploit was identified at time of analysis, and CISA KEV does not list this CVE.