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.
Path traversal in the FileArtifactService of Google ADK TypeScript (@google/adk) 0.4.0 through 0.5.x allows remote unauthenticated attackers to read files outside the configured artifact storage root by supplying crafted relative or percent-encoded sequences (../, ..%2F) in the userId or sessionId parameters, with a write primitive available when an agent tool path invokes saveArtifact. Exploitation is contingent on the operator explicitly enabling the non-default FileArtifactService and exposing the ADK API server to attacker-reachable traffic; applications using the default InMemoryArtifactService are unaffected. No public exploit code has been identified at time of analysis, and the issue is fixed in @google/adk 0.6.0; the assessed CVSS 3.1 score is 9.1-adjacent in impact (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:N) because the service must first be misconfigured into the file-backed mode.
SuggestArr deployments running in 'local_bypass' authentication mode can be tricked into granting a full administrative session without any credentials by spoofing the X-Forwarded-For header. Because api_service/app.py applies ProxyFix(x_for=1) and enforce_authentication() in api_service/auth/middleware.py trusts the resulting request.remote_addr, a remote attacker who can reach the instance can set X-Forwarded-For to a trusted CIDR value such as 127.0.0.1 and be automatically logged in as an admin via _load_bypass_user_context(), exposing endpoints like /api/users and /api/jobs. The CVSS 4.0 vector is unauthenticated (PR:N) with high confidentiality and integrity impact; exploitation is conditional on the non-default combination of local_bypass being enabled and the app sitting behind a reverse proxy, and no public exploit code or CISA KEV entry was identified at time of analysis.
Apache Tomcat 11.0.0-M25 through 11.0.26 can split the body of a large non-blocking (NIO) response across the current request and the next request received on the same reused keep-alive connection, most likely causing the second request to fail and potentially leaking fragments of the first response to a different client. Remote, unauthenticated attackers can trigger the condition (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H, 9.1 as published; our assessment raises attack complexity to High because the target must both perform large non-blocking writes and reuse the connection, and the corruption outcome is non-deterministic), so reliable attacker control over which or how much data leaks is not established. No public exploit code and no CISA KEV entry were identified at time of analysis, and 11.0.27 resolves the flaw.
Apache Tomcat 11.0.22-11.0.26, 10.1.55-10.1.60, and 9.0.118-9.0.122 contain an object-recycling race in HTTP/2 processing of asynchronous servlets that can mix up requests or responses between users. The issue is network-reachable and unauthenticated, but exploitation requires both HTTP/2 and asynchronous servlet use on the same deployment and depends on concurrent in-flight requests, so impact is probabilistic rather than deterministic. No public exploit code was identified at time of analysis and no CISA KEV confirmation was provided; fixed versions are 11.0.27, 10.1.61, and 9.0.123.
Authentication bypass in Apache Tomcat's JNDI realm allows unauthenticated remote attackers to log in without a valid password when the realm is configured with a non-GSSAPI SASL mechanism. The flaw affects 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, and 9.0.0.M1 through 9.0.122, plus EOL 8.5.x and 7.0.x branches, and Apache has released fixes in 11.0.27, 10.1.61, and 9.0.123. No public exploit has been identified at time of analysis, and exploitation requires the non-default JNDIRealm/non-GSSAPI SASL configuration.
Kiro Crew before version 0.7.2 contains a missing authorization flaw in its WhatsApp group channel integration that lets a remote attacker who is a member of an operator-configured WhatsApp group control the operator's other agent sessions and execute arbitrary commands on the host. The attacker must already belong to the specific group (low privileges, PR:L), but no operator interaction is required; deployments that do not enable the WhatsApp channel are not exposed. The vendor has released version 0.7.2 to fix the issue, and no public exploit code has been identified at the time of analysis.