Payload CMS versions prior to 3.88.0 and canary builds prior to 4.0.0-canary.27 allow unauthenticated remote attackers to infer limited information about field values they are not permitted to read, by supplying a protected field name as the sort parameter on a collection they can query. The disclosure is indirect - the attacker learns partial information from result ordering rather than reading raw values - and exploitation requires a specific alignment of conditions (readable collection, attacker-controlled sort, and a field-level-protected sort key), which is why the assessed severity is limited (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/C:L/I:N/A:N) despite the vendor-published CVSS 4.0 score of 6.9. There is no public exploit code and no confirmed active exploitation (no CISA KEV listing) at time of analysis; vendor patches are available in 3.88.0 and 4.0.0-canary.27, making this a routine low-urgency update rather than an emergency.
Missing authorization in the Mooncake Store master (through 0.3.13.post1) lets unauthenticated remote attackers inject completed LOCAL_DISK replicas via the NotifyOffloadSuccess RPC, poisoning disk-tier cache reads and forging key existence. An attacker mounts a local disk segment with a self-chosen client UUID and attaches replicas pointing at attacker-controlled endpoints, degrading integrity and availability of cached data without exposing confidentiality or compromising the host, consistent with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L. No public exploit code was identified at time of analysis, and real-world risk depends heavily on whether the master RPC endpoint is reachable beyond a trusted internal network.
Unauthenticated attackers who can reach the Mooncake Store master's coro_rpc port can hijack replication task queues in Mooncake Store master builds through 0.3.13.post1, creating, stealing, and falsely completing replication tasks on behalf of arbitrary victim clients. The affected master RPC handlers (CreateCopyTask, CreateMoveTask, FetchTasks, MarkTaskToComplete) perform no ownership or authorization checks (CWE-862), and the QueryTask RPC discloses the victim client UUIDs needed to target a specific queue, so no credentials, prior knowledge, or user interaction are required. Impact is bounded to integrity and availability (CVSS 4.0 base 6.9; independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, medium severity) - replication bookkeeping can be corrupted and real replication skipped, but confidentiality is unaffected; no public exploit code or CISA KEV listing was identified at time of analysis, and the practical limiting factor is whether the coro_rpc port is exposed beyond localhost or a trusted network boundary.
Server-side request forgery (SSRF) in Django's GeoDjango spatial lookups allows remote unauthenticated attackers to make the Django process issue outbound network requests when an application passes attacker-controlled `bytes` raster values directly into a lookup against a `RasterField`. Affected versions are Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18; older unsupported series (5.1.x, 5.0.x, 4.2.x) were not evaluated and may also be affected. The flaw is an incomplete fix for CVE-2026-15307, and exploitation requires a deployment that uses GeoDjango raster fields and forwards raw untrusted bytes into spatial lookups - not a default Django configuration. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; Django rates it 'moderate' severity (CVSS 5.3), with impact limited to attacker-directed outbound requests rather than data compromise or code execution.
Quadratic-time parsing of quoted HTTP header parameters in Django 5.2 (before 5.2.18), 6.0 (before 6.0.9), and 6.1 (before 6.1.2) allows unauthenticated remote clients to consume disproportionate CPU by supplying a header value containing many separator characters inside a quoted parameter, potentially degrading or exhausting worker capacity. The vulnerable code path is reached by default through content negotiation such as HttpRequest.accepts() and Accept/Content-Type header handling, and the existing per-call length limit does not bound the combined size of repeated headers, so an attacker can amplify the cost across many headers in a single request. Impact is availability-only (CVSS 5.3, A:L, CWE-407); vendor patches are available in Django 6.1.2, 6.0.9, and 5.2.18, and no public exploit code was identified at time of analysis.
Remote denial-of-service in the Django web framework's language-negotiation helper django.utils.translation.get_supported_language_variant(), which caches attacker-supplied language codes as keys in an in-memory LRU cache before enforcing a length limit. An unauthenticated remote attacker (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) who can influence the negotiated language - typically via the Accept-Language header, a language URL prefix, or LocaleMiddleware - can send many distinct, very long language codes so that each becomes a unique cache entry and steadily consumes process memory, degrading or exhausting the application worker. Affected are Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18; unsupported earlier series such as 5.1.x, 5.0.x, and 4.2.x were not evaluated and may also be affected. Impact is limited to availability (A:L) and requires sustained request volume rather than a single request, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Improper authentication in the Backstage @backstage/plugin-auth-node package (versions 0.3.0 through 0.6.14 and 0.7.x before 0.7.5) lets an already-admitted identity-provider user assume another catalog user's identity and inherit its access and permissions. The flaw is conditional and rated CVSS 6.8 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N): it only triggers when a deployment uses an email-based sign-in resolver that derives catalog identity from the selected profile email AND that email carries an explicit negative verification flag (profile email verified:false, a matching raw provider email_verified:false, or an ID-token-only email with email_verified:false) - an absent email_verified claim alone is not affected. Vendor-released patches exist in 0.6.15 and 0.7.5 (Backstage releases v1.49.7 and v1.54.7), and no public exploit or confirmed active exploitation was identified at time of analysis.
Access control bypass in SSSD when configured with non-default ordering that evaluates password-expiration warnings before restrictive access rules allows remote authenticated users with expired passwords to gain unauthorized access to protected systems via alternative authentication methods such as SSH public key authentication. This flaw (CWE-393) affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 deployments using LDAP access control. Exploitation requires a specific non-default configuration, an expired password, and a non-password authentication path, making it a moderate conditional risk; no public exploit identified at time of analysis.
TP-Link Tapo C500 v2.0 cameras with the ONVIF PTZ interface enabled are vulnerable to an out-of-bounds stack write (CWE-121) that can be triggered by an authenticated ONVIF client sending an excessive number of preset-related elements to the PTZ SOAP handlers, resulting in a service crash and denial-of-service. Exploitation requires valid ONVIF credentials and adjacency to the camera's network (CVSS 4.0: 6.8, AV:A/PR:H), and while the attacker cannot execute code or access data, repeated crashes can disrupt camera management and PTZ functionality until the service restarts. TP-Link has released a firmware patch, and no public exploit code has been identified at time of analysis.
Account takeover in Devolutions Server 2026.3.7.0 and earlier is possible through the Azure AD external login flow: an attacker positioned on an adjacent network segment (AV:A) can capture a login-session token that is exposed in the OAuth redirect URL and replay it to hijack the victim's account. Exploitation is limited to deployments where Azure AD external login is actually configured, and it requires intercepting a live, still-valid token during a genuine user login (AC:H), though no victim interaction with the attacker is needed (UI:N, PR:N). Independent signals are currently low - no public exploit identified at time of analysis, not listed in CISA KEV, EPSS 0.22% (11th percentile), and CISA SSVC records Exploitation: none and Automatable: no - but the vendor has released a patch and SSVC rates technical impact as total, so this is a genuine, moderate-priority issue rather than a top-tier emergency.
Heap-based buffer over-read in the HDF5 library's scale-offset filter decoder (H5Z__filter_scaleoffset) allows a local, unauthenticated attacker to cause a denial of service by supplying a crafted HDF5 file that a victim opens. The flaw occurs when the filter's stored minimum-bits parameter equals the datatype's full precision and the decoder attempts to copy d_nelmts * size bytes from a compressed chunk that is too short, triggering an out-of-bounds read and application crash. The vendor CVSS 4.0 vector (6.8 Medium) rates this as an availability-only impact with no confidentiality or integrity effect; no public exploit code has been identified, and the fix is available as an upstream pull request but not yet confirmed in a tagged release.
An out-of-bounds write in the Android kernel's Wacom HID driver (wacom_hid_set_device_mode in wacom_sys.c) lets an attacker who can physically attach or emulate a malicious Wacom HID peripheral corrupt kernel memory and escalate privileges on the affected device. No authentication or user interaction is required once the peripheral is connected, because the crafted report reaches the driver's missing bounds check directly; the CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms a physical-access-only attack path with high confidentiality, integrity, and availability impact. Only Pixel/Android kernel builds that include and exercise the Wacom HID driver are affected, and there is no public exploit identified at time of analysis; CISA SSVC rates exploitation as none and automatable as no, so the practical risk is bounded by the strict physical-access requirement and the inability to exploit this remotely or at scale.
Account takeover is possible in Devolutions Server 2026.3.7.0 and earlier through an authentication bypass in the OAuth device authorization (device code) flow, in which a captured device verification link can be replayed to bind an attacker-controlled client to a victim's account. The flaw is rated 6.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N): the attacker needs no credentials, but must first obtain a valid, still-replayable verification link and then rely on an already-authenticated victim interacting with it, which keeps attack complexity high and exploitation dependent on user behavior. Exploitation has not been observed (CISA SSVC reports Exploitation: none, Automatable: no) and no public exploit identified at time of analysis; Devolutions has released a fix in Server 2026.3.8.
A heap out-of-bounds read in the Impulse Tracker loader of libmikmod before 3.3.14 lets a crafted .it module drive the parser past its pattern buffer, crashing the host application. Any program statically or dynamically linking the vulnerable library - classic MikMod-based players, games, and media tools - is exposed when it opens an untrusted module. The trigger is an oversized pattern of more than 200 rows, which overruns the hardcoded itpat allocation (200*64 ITNOTE entries) and causes IT_ConvertTrack() to read adjacent heap memory. The assessed impact is availability only (AV:L, UI:P, A:H) with no confidentiality or integrity loss, so there is no public exploit identified at time of analysis; the practical risk is a local denial of service against applications that parse attacker-supplied tracker files.
OS command execution on Dbit WIFI4 N300 1.0.0 routers is achievable by feeding an oversized 'comment' value to the authenticated /api/addStaticDHCP endpoint, which overflows a fixed-size stack buffer in the device's web management daemon and lets the caller pivot from web administrator to a shell on the underlying operating system. The practical barrier is high: the CVSS 3.1 vector (AV:A/PR:H per the independent assessment, versus the vendor-published AV:L/PR:H base of 6.7) means an attacker must already hold valid administrator credentials and be able to reach the device from the local Wi-Fi network - there is no unauthenticated remote path, and no user interaction is required once those preconditions are met. Exploitation status is low-signal: there is no CISA KEV listing and no confirmed in-the-wild activity, though a Klogix Security (Scorpion Labs) technical blog walks through the exploitation chain end-to-end, and EPSS is only 0.22% (12th percentile), underscoring that this is a high-CVSS-but-low-real-world-priority issue.
A use-after-free (CWE-416) in Qualcomm Snapdragon's DMA buffer management allows a local attacker with low privileges to corrupt kernel memory by triggering a race condition between concurrent DMA buffer allocation and deallocation, potentially leading to code execution or privilege escalation. The vulnerability is not remotely exploitable and requires winning a timing window (AC:H). No public exploit code or active exploitation has been identified at time of analysis; the vendor rates the required privileges as high (PR:H), but independent assessment indicates low privileges (PR:L) may be sufficient.
Memory corruption in the Qualcomm Snapdragon camera driver path that handles operations during driver updates allows a locally positioned attacker who already holds high privileges to trigger an out-of-bounds write (CWE-787) and corrupt memory, with the potential for high confidentiality, integrity, and availability impact on the affected device. Rated CVSS 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), this is a moderate-severity local privilege/memory-corruption issue rather than an internet-facing emergency; there is no public exploit identified at time of analysis and no CISA KEV listing, and exploitation is gated by the strict prerequisites of local access plus pre-existing elevated privileges and a driver-update code path. Exact affected chipset families and driver configurations are not enumerated in the available data, so Qualcomm's October 2026 security bulletin should be treated as the authoritative scope statement.
Local attackers with high privileges can trigger an out-of-bounds write in the Qualcomm Snapdragon camera CRE (Camera Request Engine) driver, causing memory corruption during hardware update preparation. Tracked as CVE-2026-25272, the flaw requires local access and elevated permissions (PR:H) to invoke the vulnerable driver operation, but successful exploitation yields high confidentiality, integrity, and availability impact confined to the affected device subsystem (scope unchanged). No public exploit code or confirmed active exploitation has been identified at time of analysis.
Out-of-bounds write in the Qualcomm Snapdragon Android Camera driver allows a locally privileged process to corrupt memory by submitting command buffer requests carrying invalid length parameters, potentially achieving code execution or memory corruption within the driver's execution context on affected devices. Because the CVSS vector is AV:L/PR:H/UI:N, exploitation requires local access and an already-privileged process capable of reaching the camera driver interface, making this realistically a post-compromise privilege-escalation primitive rather than an initial-access vector; no public exploit identified at time of analysis. The CPE entry (cpe:2.3:a:qualcomm,_inc.:snapdragon:*) carries no version constraint, so the exact affected chipset and firmware coverage must be resolved from Qualcomm's October 2026 security bulletin.
Memory corruption in the Qualcomm Snapdragon camera subsystem can be triggered by processing camera requests with excessive batch and IO buffer configurations that exceed allocated memory, resulting in an out-of-bounds write (CWE-787). All versions of Qualcomm Snapdragon platforms are affected according to the vendor CPE. Exploitation requires local access with high privileges (PR:H) and cannot be triggered remotely; no public exploit code or active exploitation has been identified at time of analysis, making this a moderate-priority issue for systems where an attacker already has privileged on-device code execution.
Local privilege escalation in ClearPass OnGuard allows an authenticated local user to write arbitrary files and potentially execute code with elevated privileges, but only when unspecified preconditions outside the attacker's control are met. The vulnerability requires user interaction and is high-complexity (AC:H), limiting practical exploitability to hosts where the OnGuard agent is deployed and those environmental conditions already exist. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is assessed as moderate and defense-in-depth-tier.
Local privilege escalation in the Aruba/HPE ClearPass client software lets a low-privileged local user execute commands with elevated privileges on the affected host, but only when a specific environmental precondition that the vendor describes as being outside the attacker's control is satisfied. The assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, score 6.7) confirms that exploitation requires an interactive local session with an existing low-privileged account plus user interaction, meaning there is no remote or unauthenticated attack path and the attacker cannot deterministically force the triggering condition. There is no public exploit identified at time of analysis, no CISA KEV listing, and no evidence of active exploitation; the practical risk is moderate and bounded by these prerequisites rather than by remote reachability.
Local privilege escalation in Google Android's platform message handler lets an actor who already holds System-level execution privileges bypass a missing permission check in platform_msg_handler_init (default_msg_handlers.c) and obtain high-impact control over confidentiality, integrity, and availability on the device. Rated CVSS 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the issue requires local access and a pre-existing high privilege level, making it an authorization-boundary bypass for an already-privileged local actor rather than a path to initial device compromise. There is no public exploit identified at time of analysis and CISA's SSVC assessment records Exploitation: none and Automatable: no, while a vendor fix is published in the October 2026 Android Security Bulletin.
Command injection in the HPE Aruba ClearPass Policy Manager OnGuard agent allows an attacker holding a valid authenticated session within a ClearPass-managed environment to inject and execute arbitrary operating-system commands, which per the vulnerability description run with elevated privileges on the affected Windows endpoint. Only deployments that have installed the OnGuard posture/health agent on Windows hosts are exposed; non-Windows endpoints and environments not using OnGuard are out of scope. HPE rates this medium severity (CVSS 6.5), and our independent assessment keeps the severity in that band while noting that, once the authentication prerequisite is satisfied, the impact on the endpoint is high because the injected commands inherit elevated rights (assessed confidentiality, integrity and availability all High). No public exploit code has been identified and CISA KEV does not list this issue, so there is no confirmation of active exploitation at time of analysis.
Qualcomm Snapdragon kernel driver IOCTL handling contains a memory corruption (out-of-bounds write) that a local attacker with low-privilege code execution can trigger by supplying invalid parameters, leading to potential integrity impact and denial of service. This is a moderate-severity local issue (CVSS 6.6) rather than a drop-everything priority. No public exploit code or active exploitation has been identified at time of analysis.
Authenticated path traversal in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who already holds a valid low-privilege account or session reach files outside the intended restricted directory, exposing sensitive information hosted on or reachable from the Langflow instance (CWE-22). The flaw is network-reachable with low attack complexity and no user interaction required, but it is explicitly not unauthenticated - an attacker must first be able to log in, so internet-exposed deployments with self-service registration or shared credentials carry the greatest realistic risk. At the time of analysis no public exploit code has been identified and there is no confirmed active exploitation (not in CISA KEV); IBM has published a fix through its support advisory.
Denial of service in the WordPress plugin WPBase Cache (versions 5.5.6 and earlier) allows an authenticated user holding the Subscriber role - the lowest authenticated WordPress role - to consume server resources without limit and degrade or take the site offline. The attack is network-reachable, low complexity, requires no user interaction, and affects only availability (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5 Medium), so sites that have disabled user registration or that do not run the plugin are not exposed to anonymous attackers. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the practical exposure depends on whether the target site permits self-registration or an attacker already holds subscriber credentials. Reported by Patchstack, with no vendor-fixed version confirmed in the available advisory data.
Sensitive information disclosure in AOS-S (HPE Aruba switching platform) could let a remote attacker read confidential data from an affected device's management surface, as documented in HPE advisory hpesbnw05156en_us. The vendor description characterizes the attacker as unauthenticated, while the published CVSS 3.1 vector carries PR:L (some privilege required); our independent assessment resolves the vector to PR:N with a resulting score of 7.5, but that authentication precondition remains genuinely unresolved and materially changes exploitability, so it should be verified against the advisory before risk is finalized. Exploitation is confined to confidentiality (C:H) with no integrity or availability impact, and no public exploit code or CISA KEV entry was identified at time of analysis, placing this in a moderate, patch-and-segment priority tier.
Denial of service in Elasticsearch allows an authenticated user holding read access to just a single index to terminate a cluster node by submitting a search request whose aggregation definitions are deeply and maliciously nested. Processing the request drives unbounded recursive execution that exhausts the node's resources and crashes the affected process, which does not recover on its own and requires manual intervention to restore service. The flaw is scored CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), is availability-only, and no public exploit code or confirmed active exploitation was identified at time of analysis; the practical barrier is the authenticated read privilege prerequisite rather than remote reachability.
A buffer overflow in an affected interface of HPE Aruba AOS-S (ArubaOS-Switch) networking devices lets an authenticated remote attacker crash or destabilize the switch, producing a denial-of-service condition. Successful exploitation requires valid credentials on the device (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base score 6.5), so the realistic risk is management-plane disruption and loss of network availability rather than data compromise or code execution - the assessed impact is availability-only (A:H) with no confidentiality or integrity effect. There is no indication of confirmed active exploitation or of publicly available exploit code at the time of analysis, and the issue is rated moderate priority; specific affected firmware builds and configuration preconditions must be confirmed against HPE advisory hpesbnw05156en_us.
Improper input validation in the @backstage/plugin-techdocs-backend static content router (versions prior to 2.2.4) lets an authenticated Backstage user reach TechDocs static files outside the entity they are authorized to view when the Azure Blob Storage publisher provider is configured and entity-level permissions are enabled, resulting in high-confidentiality information disclosure. The flaw is a path traversal (CWE-22) reachable over the network by a low-privileged account, rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N); Azure-Blob-Storage-only scope and the required authenticated session keep realistic risk moderate. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor-released fix is @backstage/plugin-techdocs-backend 2.2.4, published in the Backstage monorepo release v1.54.6.
Broken access control in the Delete All Comments WordPress plugin through version 7.1 allows any authenticated subscriber-level account to invoke bulk comment-deletion functionality without the required capability check, causing high availability impact to comment data on affected sites. The assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H confirms remote, low-privilege exploitation with no user interaction, while confidentiality and integrity are unaffected; this is a moderate, not critical, priority. No CISA KEV confirmation and no public exploit identified at time of analysis are present in the supplied intelligence, and exploitation is realistic mainly where self-registration or obtainable subscriber credentials exist.
Unauthenticated settings modification in the PayPlug for WooCommerce (Official) WordPress plugin at versions up to and including 3.1.0 lets any network-reachable attacker invoke the plugin's settings-change functionality without credentials or user interaction, altering configuration data on affected WooCommerce stores (CVSS 6.5, PR:N/UI:N with limited integrity and availability impact). The root cause is a missing authorization check (CWE-862), which means the plugin exposes a settings endpoint that does not verify capability or nonce before applying changes. At time of analysis there is no public exploit code and no confirmed active exploitation (not in CISA KEV); successful abuse remains limited to sites that have this specific plugin installed, active and reachable at an affected version, and the impact is scoped to settings modification rather than full site compromise.
Unauthenticated broken access control in the Autoship Cloud for WooCommerce Subscription Products plugin through version 2.17.0 lets remote attackers reach plugin functionality that should require authorization, allowing unauthorized actions that degrade the integrity and availability of subscription-related operations (CVSS 6.5, C:N/I:L/A:L). The assessed vector (AV:N/AC:L/PR:N/UI:N) confirms the flaw is exploitable without credentials or user interaction, so the only real prerequisites are that a vulnerable plugin version be installed, active, and reachable over the network on a WordPress/WooCommerce site. No CISA KEV entry and no public exploit code were identified at time of analysis, so this is a moderate, patch-on-schedule issue rather than a top-tier emergency.
Authenticated path traversal in the Piotnet Addons for Elementor WordPress plugin (versions up to and including 7.1.71) lets a Contributor-level account read and download arbitrary files from the host, exposing wp-config.php credentials, backups, and other sensitive data (CVSS 3.1: 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). The flaw is confidentiality-only - an attacker gains no ability to write, modify, or disrupt the site - and it requires a valid Contributor login, so exposure is concentrated on sites that allow open registration or hand Contributor roles to untrusted users. There is no CISA KEV entry and no public exploit code identified at time of analysis, and Patchstack is the reporting source through its WordPress vulnerability database.
Missing authentication in the csm-authorization-tenant gRPC service (TenantService) shipped with Dell Container Storage Modules (CSM) allows an unauthenticated attacker on the adjacent network to create tenant entities, inject roles across tenant boundaries, and modify storage access-control flags on any deployment running CSM authorization prior to 1.18.0. The flaw is rated CVSS 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N) reflecting high integrity impact with no authentication and no user interaction required, though it is only reachable from an adjacent network segment rather than the public internet. There is no public exploit identified at time of analysis and no CISA KEV listing; multiple signals point to a moderate, not top-tier, priority, with exposure concentrated in clusters that actually deploy the CSM authorization module and do not segment its gRPC control plane from untrusted pods or hosts.
Use-after-release in Google Chrome's FontAccess (Local Font Access API) lets an attacker who has already compromised the renderer process bypass web origin policy by luring a victim to a crafted HTML page in Chrome versions prior to 155.0.8059.39. Successful exploitation yields no confidentiality loss but a high integrity impact, as the attacker can subvert origin boundaries from inside an already-broken renderer; the required renderer compromise is a hard prerequisite and makes this a defense-in-depth, medium-severity issue rather than a standalone remote entry point. No public exploit identified at time of analysis, EPSS is low at 0.31% (22nd percentile), and Google has released a fixed build. The CVSS vector shows PR:N/UI:R, meaning unauthenticated attackers are relevant but victim interaction (loading the page) is mandatory; our own assessment rates attack complexity as High rather than Low given the prerequisite renderer foothold.
Denial of service in Elasticsearch allows an authenticated user (CVSS vector PR:L) who holds read access to a single index to crash a node by defining a scripted runtime field whose script output builds a deeply nested geometry value; because serialization of script-generated geometry lacks the nesting-depth limit applied to text-supplied geometry, recursion exhausts the stack and the node terminates, and on some deployments it does not recover without manual intervention. The issue is availability-only (C:N/I:N/A:H, CVSS 6.5) with no data exposure, and no public exploit code was identified at time of analysis. Fixes are released in Elasticsearch 8.19.23, 9.4.8, and 9.5.5 per ESA-2026-198, so this is a moderate-priority patching item rather than an emergency, but clusters that allow untrusted users to read indices while scripting/runtime fields are enabled should treat it as more urgent.
Denial of service in Elasticsearch lets an authenticated user who holds connector management privileges exhaust node heap memory by creating a connector resource with an excessively large description field and then causing that resource to be accessed or read, crashing the affected node. The path is network-reachable but requires PR:L authorization, and the impact is limited to availability with no data confidentiality or integrity loss. No public exploit code has been identified at time of analysis, and Elastic has released fixed versions 8.19.2, 9.0.6, 9.1.4, and 9.2.1 in advisory ESA-2026-195.
Denial of service in Elasticsearch allows authenticated users holding the manage_index_templates cluster privilege to exhaust node heap by registering multiple index-template resources with metadata near the per-resource size limit and then triggering a combined retrieval that materializes all metadata in memory simultaneously. Affected versions include Elasticsearch releases prior to 9.4.7, 9.5.3, and 8.19.23, as addressed in ESA-2026-192. No public exploit code has been identified at time of analysis, and exploitation requires the specified privilege, limiting the attack to trusted operators or compromised privileged accounts.
Denial of service in Elasticsearch 9.x lets an authenticated attacker holding only low-privilege credentials terminate a node by submitting a request that drives uncontrolled recursion and excessive memory allocation, taking down cluster availability. The CVSS 6.5 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) confirms availability-only impact with no data exposure or modification, reachable over the network with no user interaction or non-default configuration - though authentication at a low privilege level is required, so exposure is limited to insiders, compromised credentials, or over-permissive accounts. Exploitation status is no public exploit identified at time of analysis (no CISA KEV listing, EPSS not available), making this a moderate, availability-only risk rather than a top-tier emergency; vendor fixes are published as Elasticsearch 9.4.8 and 9.5.5 in ESA-2026-190.
Denial of service in Elasticsearch 8.x and 9.x lets an authenticated user with only low privileges crash cluster nodes by submitting a specially crafted query that drives uncontrolled memory growth in the query processing engine, ending in an out-of-memory termination. Because the trigger can be repeated - including through queries embedded in shared resources such as saved searches or stored queries - the result can escalate from a single node restart to persistent cluster unavailability, though there is no data disclosure or modification path. The flaw is rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), and no public exploit code has been identified at time of analysis.
Directory traversal in the OpenSSH sftp client before 10.6 can cause files to be written to unintended locations when a user performs a recursive copy operation against an attacker-controlled or compromised SFTP server. Exploitation requires the victim to initiate a recursive transfer such as get -r or put -r, and the malicious server supplies crafted path/filename entries containing traversal components; this is a client-side trust issue, not a flaw in an exposed sshd service. No public exploit identified at time of analysis, and the assessed CVSS 3.1 score is 4.2 with high attack complexity and user interaction required.
Unauthenticated broken access control in the 10Web Social Photo Feed WordPress plugin (versions 1.4.35 and earlier) allows remote attackers to reach plugin functionality that should require authorization, giving limited read and write access to plugin-controlled data rather than full site compromise (CVSS 6.5, CWE-862, C:L/I:L/A:N). The CVSS vector confirms no authentication (PR:N) and no user interaction (UI:N) are needed, and the attack is network-reachable at low complexity, so any site with the vulnerable plugin active is exposed without credentials. Exploitation is bounded by the Low confidentiality and integrity impact and by the need for the specific plugin/version; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Authenticated users of Backstage TechDocs can bypass entity-scoped authorization and read documentation belonging to other entities by requesting a crafted /static/docs/... URL containing percent-encoded parent-directory (%2e%2e) segments. The issue is confined to deployments that combine the external TechDocs builder with an external storage provider (S3, GCS, etc.) and have the Backstage permission framework enabled; setups without the permission framework are unaffected because TechDocs content is intentionally readable by all authenticated users, and the default local builder/storage path is not exposed. Exploitation requires an authenticated account that already has access to at least one TechDocs site (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 6.5), exposure is therefore limited to confidentiality of docs across entity boundaries, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Filesystem path traversal in the Backstage TechDocs local publisher (@backstage/plugin-techdocs-node) can expose host files - such as /etc/passwd - to authenticated users of the documentation serving endpoint when the backend is configured with techdocs.publisher.type: 'local'. Exploitation requires a documentation source tree that already contains a symbolic link pointing outside the intended output directory, a precondition the vendor states does not arise through normal MkDocs operation, plus an authenticated user able to reach the endpoint (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.3, confidentiality-only impact). Cloud publishers (S3, GCS, Azure Blob Storage) are explicitly not affected, and no public exploit code has been identified at time of analysis; the issue is fixed in @backstage/plugin-techdocs-node 1.15.4.
Arbitrary file read in the Backstage TechDocs node plugin (@backstage/plugin-techdocs-node) prior to 1.15.4 allows an authenticated user who can register documentation sources to escape the intended documentation boundary. Because TechDocs only validated symlinks inside the docs_dir, an attacker-controlled source tree containing a symlink that resolves outside the tree (e.g. to /etc/passwd) plus an MkDocs snippets include directive ('--8<--') could pull that out-of-bounds file into the generated documentation, exposing anything readable by the build process. Exploitation requires authenticated access (PR:L), a crafted symlink/snippet chain (AC:H), and a deployment that builds docs from user-registerable sources; impact is confidentiality-only (C:H/I:N/A:N, CVSS 5.3), and no public exploit was identified at time of analysis.
Sensitive information disclosure in Kibana 9.4.x and 9.5.x allows an authenticated user with limited Fleet management privileges to read private cryptographic key material that should be restricted to Fleet settings administrators. The exposed material can include Fleet Server host-connection keys, potentially enabling impersonation of trusted Fleet infrastructure in deployments where those keys are actively used; no public exploit identified at time of analysis. Vendor fixes are available in Kibana 9.4.8 and 9.5.5 per Elastic Security Advisory ESA-2026-193.
Authenticated attackers holding a Subscriber-level account or higher can exploit a missing authorization check in the WordPress plugin App for Cloudflare (versions 1.10.1 and earlier) to modify plugin settings without proper permissions. The vulnerability has a CVSS score of 6.5, requires low-privilege credentials on a site where the plugin is active, and results in unauthorized configuration changes with no confidentiality or availability impact. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV; sites that allow user self-registration or that have existing low-privilege accounts are most at risk.
Inconsistent repository filtering in Backstage's Bitbucket Server catalog backend module allows an authenticated Bitbucket Server user to inject catalog locations for repositories that the provider's configured filters are supposed to exclude. Only deployments of @backstage/plugin-catalog-backend-module-bitbucket-server (0.4.0 up to but not including 0.5.15) that use event-driven catalog updates AND configure projectKey, repoSlug, or skipArchivedRepos filters are affected; the attacker must have push access to a filtered-out repository that the Backstage integration credentials can still read. Impact is limited to unauthorized additions to the software catalog (integrity, not confidentiality or availability), no public exploit code has been identified at time of analysis, and exploitation requires valid Bitbucket Server authentication (PR:L) - so this is a genuine but moderate-priority authorization flaw rather than an emergency.