Arbitrary code execution in CleanShot X for macOS occurs when the application insecurely deserializes data embedded in a .cleanshot project file, so a crafted editable-screenshot annotation file runs its payload automatically during parsing in the context of the logged-in user. The flaw affects users on release branches below the fixed builds 4.5.2, 4.6.3, 4.7.8 and 4.8.10, and exploitation is gated by mandatory user interaction: the attacker must deliver the malicious file and convince the victim to open it, with local file delivery rather than a network-exposed service. No public exploit code has been identified at time of analysis, and the CERT-PL-sourced report is tracked as a this-week priority rather than an emergency; users who have never opened a .cleanshot file from an untrusted source are explicitly out of scope.
Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 accepts SVG and EPS files for contact photo uploads and passes them to ImageMagick for resizing, allowing authenticated users to supply content that can reference external resources or invoke ImageMagick delegates; this may lead to file disclosure, SSRF, or command execution depending on the server's ImageMagick configuration. No public exploit has been identified at time of analysis, and vendor patches are available in 1.6.20 and 1.7.5.
Project isolation bypass in Incus lets an authenticated client that is confined to one project copy and read custom storage volumes belonging to any other project on the same server, including volume snapshots and configuration. The flaw affects Incus 7.0.1 (fixed in 7.0.2) and 7.2.0 through 7.4.x (fixed in 7.5.0), and is reachable only through a hand-crafted POST to /1.0/storage-pools/{pool}/volumes/custom that supplies a source volume with an attacker-chosen source.project while omitting source.type - the official Incus client always sets source.type=copy and therefore cannot trigger it. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation requires legitimate low-privilege credentials holding can_create_storage_volumes in at least one project, so impact is concentrated on multi-project servers where project isolation is the actual security boundary.
CVE-2026-79881 is a high-severity (CVSS 8.3) network-reachable flaw in an HPE product, documented only through the vendor bulletin referenced as hpesbnw05162en_us, which is the identifier format HPE uses for its networking/Aruba security bulletins; the specific product, version range and trigger are not stated in the supplied data. Per the assessed vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H), no prior authentication is needed, but successful exploitation requires the target user to perform an action and depends on high-complexity conditions that are not fully under the attacker's control, with a scope change implying impact beyond the initially vulnerable component. Intelligence tags the issue as Information Disclosure, which sits awkwardly with the vector's high confidentiality, integrity and availability impacts - that inconsistency, combined with the absence of a description or CWE, means the real-world impact cannot be verified from the available sources; no public exploit has been identified at time of analysis and there is no CISA KEV entry. The vulnerability is queued under a 'this_week' priority label rather than an emergency/act-now designation.
Information disclosure in HPE network devices, with the exact affected model and firmware not identified in the supplied data, allows attackers on an adjacent network segment to read sensitive data and cause limited integrity and availability impact without authentication or user interaction. The CVSS 3.1 score is 8.3, with the vector requiring same-segment access (AV:A) rather than internet-wide reachability, low attack complexity, no privileges, and no user interaction. No public exploit or CISA KEV entry is identified at time of analysis, and the specific triggering feature is not described in the available sources.
Information disclosure affecting an HPE product line that has not been named in the supplied data can be triggered by an attacker positioned on the adjacent network, with the assessed vector (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, 8.3) indicating high confidentiality, integrity and availability impact that crosses a security scope boundary. No authentication or user interaction is required, but high attack complexity means success depends on conditions outside the attacker's direct control, and exposure is confined to the same broadcast domain or a logically adjacent segment rather than the public Internet. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; the report originates from HPE's own security alert channel and priority guidance places remediation in this week's window, yet no CVE description, CWE mapping, CPE inventory, or fixed version has been supplied, leaving HPE bulletin hpesbnw05162en_us as the only authoritative reference.
Signals point to a real but bounded availability risk rather than a top-tier emergency: the MongoDB C# Driver's BSON library interns every BsonSymbol produced during deserialization and retains those symbols for the lifetime of the process with no cap, so an unauthenticated remote party able to get attacker-influenced BSON or JSON deserialized can drive unbounded memory growth and deny service to the host application (availability-only; assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, CNA CVSS 4.0 score 8.2). Exposure is conditional - the application must actually deserialize untrusted content through the driver and that content must carry BSON symbol values; merely having the driver installed is not a trigger, and no MongoDB server component is affected. No public exploit code or confirmed active exploitation has been identified at time of analysis; version 3.13.0 removes symbol interning as the fix.
Unauthenticated remote denial of service in the Erlang SAML library esaml (0.1.0 and later) allows an attacker to abort an Erlang node by exhausting its atom table through unsigned LogoutResponse messages posted to a Service Provider's single-logout endpoint. Because esaml_sp:validate_logout_response/2 only verifies a signature when one is present, an unsigned message reaches esaml:decode_logout_response/1, where status_code_map/1 converts each unrecognized StatusCode into a permanent atom with list_to_atom/1 - roughly one million distinct status values (the VM's default atom-table ceiling) are enough to crash the node. The CNA scored this CVSS 4.0 8.2 with the AT:P attack-requirement metric; the practical barrier is volume and time rather than skill, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in the MQTT5-to-MQTT 3.1.1 compatibility adapter of AWS aws-c-mqtt (versions 0.9.1 through 0.16.1) allows a hostile or impersonated MQTT broker to trigger an excessive memory allocation that crashes the client process, and the crash can recur if the application automatically restarts and reconnects. Exploitation requires that the application uses the compatibility adapter and either connects to an attacker-controlled broker or has its broker traffic tampered with on-path (assessed CVSS 3.1: AV:N/AC:H/PR:N/UI:N/A:H; vendor CVSS 4.0: 8.2 with AT:P). No public exploit identified at time of analysis and no CISA KEV listing; the vendor-released fix is aws-c-mqtt 0.16.2, also bundled in aws-crt-cpp v0.43.9 and AWS IoT Device SDK for C++ v2 v1.45.1.
Improper authentication in the Go event-ingestion middleware of uselotus Lotus through 0.10.2 lets unauthenticated remote attackers submit usage events to POST /api/track/ on behalf of another organization, corrupting that tenant's metered usage and billing records. The flaw is integrity-only (no data disclosure or availability impact) and exploitation hinges on knowing or obtaining a valid API key prefix, since the secret half of the key is never compared against the stored hashed_key; the sources do not explain how a prefix would be leaked or enumerated. No public exploit code was identified at time of analysis and the vulnerability is not in CISA KEV, though VulnCheck reporting and a public technical writeup give the issue a this_week remediation priority; the blast radius is narrow but the defect is a genuine authentication bypass.
HPE networking products are affected by a remotely reachable, unauthenticated flaw rated CVSS 8.2 (AV:N/AC:L/PR:N/UI:N, C:N/I:L/A:H), where the dominant risk is loss of availability with a limited integrity impact rather than the exposure of data. The single supplied source - HPE security bulletin hpesbnw05162en_us - is the only authoritative record of which platforms and firmware revisions are in scope, because no CVE description, CPE mapping, or version range was included in the intelligence feed. No public exploit code or PoC reference was identified at time of analysis, and the issue has not been added to CISA KEV; it carries a this_week priority label, so remediation should be scheduled within the current patching cycle rather than treated as an emergency.
Remote, unauthenticated attackers can cause high availability impact and limited integrity impact against an HPE networking product, per a CVSS 3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H) published with HPE bulletin hpesbnw05162en_us. No description, CWE, CPE or version data accompanied the CVE record, so the specific product line, interface, protocol and affected release range are not identified in the available sources and must be confirmed from the HPE bulletin. No public exploit code and no confirmed active exploitation are indicated at time of analysis, and the issue is prioritized as 'this_week' rather than an emergency, but the vector describes a low-complexity, no-prerequisite network attack path that warrants prompt confirmation of exposure.
Cross-origin WebSocket access in webpack-dev-server before 5.2.7 and in 6.0.0 lets a malicious web page, visited by a developer while the dev server runs, reach a proxied backend through the dev server without Host or Origin validation. The gap exists only when a devServer.proxy entry is configured with ws:true, and it bypasses the allowedHosts checks that already block the same route over plain HTTP-even if the server is bound to loopback. No public exploit identified at time of analysis; the vendor fixed the issue in 5.2.7 and 6.1.0.
Information disclosure in HPE networking devices allows unauthenticated attackers on the same adjacent network segment to obtain high-confidentiality data, with the CVSS 3.1 base score of 8.2 reflecting changed scope, no integrity impact, and low availability impact. The exact affected models, firmware versions, and trigger conditions are not described in the available sources; HPE bulletin hpesbnw05162en_us is the sole reference for scope and remediation. No public exploit code was identified at time of analysis.
Crafted HTTP requests sent to Next.js App Router applications that define at least one Server Action can drive excessive CPU consumption and block processing of further requests in the same Node.js process, producing a denial of service rated 8.2 (CWE-770, uncontrolled resource allocation). The affected ranges are 13.0.0 through 15.5.27 and 16.0.0 through 16.4.0; applications on the Pages Router, and App Router applications with no Server Actions defined, are explicitly not vulnerable, which substantially narrows the exposed population. Exploitation requires no authentication and no user interaction, and no public exploit code has been identified at time of analysis, with no CISA KEV entry and no EPSS signal supplied; the vendor states that upgrading to 15.5.28 or 16.4.1 is the only complete fix, with no workaround available.
Information disclosure in HPE networking products, tracked as CVE-2026-79891, can expose sensitive data to remote unauthenticated attackers when a high-complexity condition outside their direct control is satisfied; the CVE record is scored 8.1, while the independent assessment limits impact to confidentiality only. The affected product family, versions, feature, and exact prerequisite are not exposed in the supplied data, and the only vendor pointer is HPE security bulletin hpesbnw05162en_us. No public exploit was identified at time of analysis, and no CISA KEV status is present.
HPE has published advisory hpesbnw05162en_us for a network-reachable flaw tracked as CVE-2026-79887 that, per its CVSS 3.1 vector (8.1 High), can fully compromise confidentiality, integrity, and availability of the affected system. The specific product, version range, CWE class, and the precondition implied by the high attack complexity (AC:H) are not stated in the available input, so the exact feature or configuration an attacker must arrange remains unconfirmed and must be read from the HPE advisory. No CISA KEV listing, no public exploit code, and no EPSS score were supplied at time of analysis; the single-source tag labels the issue 'Information Disclosure', which is narrower than the total-impact vector and should be reconciled against the vendor advisory. Prioritization signal from vuln.today places this in the 'this_week' queue rather than act_now or emergency.
Information disclosure in HPE Networking products (CVE-2026-79890) has a CVSS 3.1 base score of 8.1; the assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H describes remote, unauthenticated exploitation with no user interaction, while high attack complexity means success depends on conditions outside the attacker's full control. The affected HPE product, version range, and required configuration are not described in the available sources and must be confirmed from HPE bulletin hpesbnw05162en_us, and the tag only classifies the issue as Information Disclosure. No public exploit identified at time of analysis, and the vuln.today priority label is this_week; signals are mixed and the underlying data is thin.
An 8.1-severity remote flaw (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) affects an HPE networking product identified only through HPE security bulletin hpesbnw05162en_us; the specific product and version ranges are not present in the supplied data. Scoring combines full impact on confidentiality, integrity and availability with network reachability, no privileges and no user interaction, but high attack complexity means a condition outside the attacker's control must hold before exploitation succeeds, and that prerequisite is not described in any available source. No public exploit code and no confirmed active exploitation (CISA KEV) are associated with this record, and the only cited reference is the HPE bulletin itself; the vuln.today triage label is this_week, so this should be scheduled within the current patch cycle rather than treated as an emergency. Note the supplied tag reads "Information Disclosure" while the assessed vector claims high integrity and availability impact - that discrepancy is unresolved in the available data.
High-severity network-reachable compromise of the HPE product covered by bulletin hpesbnw05162en_us can affect confidentiality, integrity, and availability, though the available data provides no public description of the flaw. The CVSS 3.1 vector rates it 8.1 with AV:N/AC:H/PR:N/UI:N, so unauthenticated remote exploitation with no user interaction is possible only when unspecified high-complexity preconditions are met. No public exploit code or CISA KEV entry is identified, and the HPE advisory is the authoritative source for affected versions and fixes.
Unauthenticated PHP local file inclusion in the Elated-Themes Academist Core plugin for WordPress (all versions through 1.4.1) lets a remote attacker steer an include/require statement toward files already present on the server, exposing their contents and, depending on what is included, influencing executed code - scored CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). The vector requires no authentication and no user interaction, but AC:H reflects conditions the attacker does not fully control (such as a resolvable local path or a particular request state), which limits reliable or automated exploitation. Reported by Patchstack and prioritized as 'this_week'; no public exploit code or CISA KEV entry was identified at time of analysis, and the specific endpoint, parameter and feature that trigger the inclusion are not described in the available sources.
Server-side request forgery in Azure AI Foundry can be exercised by an authenticated user with low privileges over the network, allowing the service to be induced to make requests that may expose sensitive information and cross a scope boundary. The affected product is Microsoft's Azure AI Foundry cloud service; no public exploit was identified at the time of analysis and no KEV designation is present in the supplied data, while Microsoft has published a vendor fix. This is a genuine but moderate-priority issue rather than a drop-everything emergency, and the exact feature, API, or request parameter that triggers the server-side request is not described in the available sources.
Local privilege escalation is possible in the affected HPE networking product, where a low-privileged local user can achieve high confidentiality, integrity, and availability impact with low attack complexity and no user interaction (CVSS 3.1: 7.8 High). The flaw cannot be triggered remotely and requires prior local access; the specific feature, protocol, or configuration that triggers it is not described in the available sources. No public exploit code has been identified at time of analysis, and there is no CISA KEV confirmation.
HAProxy 3.x releases before 3.4.6 can be driven into persistent denial of service by remote unauthenticated attackers sending a single crafted HTTP/1.1 chunked request: the H1 multiplexer's chunk parser re-processes the same bytes without advancing, pinning one worker thread at 100% CPU even after timeouts fire and the client disconnects. Repeating the request exhausts the worker pool until the process is manually restarted, so confidentiality and integrity are unaffected but availability is fully lost. Attack surface is standard HTTP/1.1 frontend traffic (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-835); no public exploit code or CISA KEV entry is associated with this CVE at time of analysis, and the upstream fix commit is published in the HAProxy git repository.
Identity impersonation in the MongoDB C#/.NET Driver allows one application user to execute database operations under another user's X.509 identity, affecting the confidentiality and integrity of everything that identity can reach. The driver's shared connection cache keys TLS client certificates only by issuer and serial number, so a user who copies a victim certificate's issuer and serial into their own certificate - without holding the victim's private key - can be handed a cached connection already authenticated as the victim. The flaw requires a specific multi-tenant architecture where one host application builds multiple clients from per-user certificates while sharing a connection pool; there is no public exploit identified at time of analysis, but the underlying patch is shipped in version 3.13.0.
A truncated HTTP/2 PING frame sent to an HAProxy frontend that accepts HTTP/2 causes the H2 multiplexer to spin in a busy loop, driving worker-thread CPU to saturation and degrading or denying service to legitimate traffic (CVSS 7.5, availability-only). Only deployments with an HTTP/2-enabled listener (h2 in the bind line / ALPN negotiation) are reachable; HTTP/1.x-only setups are unaffected, and no authentication or user interaction is required against an H2 endpoint. Sustained impact depends on the attacker holding many concurrent connections open, since each connection is eventually cleared by 'timeout http-request'; no public exploit code was identified at the time of analysis and there is no KEV confirmation of active exploitation.
Network code execution in Microsoft Exchange Online is possible for an authenticated low-privileged user through a stack-based buffer overflow (CWE-121), rated CVSS 3.1 7.5 High with AC:H. Microsoft reports a vendor fix is available; no public exploit identified at time of analysis, and the temporal metrics mark exploit code maturity as Unproven (E:U) with an official fix available (RL:O). Because Exchange Online is a Microsoft-hosted cloud service, exposure and remediation are controlled by Microsoft rather than by on-premises configuration; the vuln.today decision label is this_week.
An authorization bypass in Lotus (uselotus/lotus) through 0.10.2 lets a self-registered, authenticated user switch into a different tenant by POSTing that organization's UUID to /app/switch_organization/, after which the victim tenant's data and billing configuration become reachable. Access is not unrestricted: the attacker must obtain the target organization's random, non-guessable UUID out of band, which is the main practical barrier and the reason the vector carries AC:H/AT:P despite the low-privilege (PR:L) requirement. Exploitation status is not confirmed in the available sources - no CISA KEV entry and no verified working exploit code were provided, though a public technical writeup reference is linked; priority is 'this_week', i.e. a genuine but not drop-everything issue, and no fixed version is listed in the available data.
Unsafe reflection in the WordPress plugin Royal Elementor Addons (all versions through 1.7.1068) allows code injection: externally controlled input is used to select which class or code path the plugin executes, so a low-privileged authenticated user can push the site toward attacker-chosen code execution. The plugin must be installed and active, and the attacker needs a valid account on the site first, but no user interaction is required and the attack is network-reachable at low complexity (CVSS 3.1 base score 7.6; assessed vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit code was identified at time of analysis and the issue is not in CISA KEV; the available sources do not name the exact endpoint, parameter or configuration that supplies the attacker-controlled class value.
Denial of service in body-parser before 1.20.9 and in 2.0.0 through 2.3.x allows any remote unauthenticated client to terminate a Node.js or Express process that uses default body parsing. A request with a Content-Encoding such as gzip and trailing bytes after a valid compressed frame causes the finished decompression stream to emit an error with no error listener, resulting in an uncaught exception. The vendor has released fixes in 2.4.0 and 1.20.9; no public exploit code was identified in the supplied intelligence at time of analysis.
Unbounded memory leak in the msgpack-python C extension (msgpack._cmsgpack) allows a remote attacker to exhaust process memory by repeatedly sending malformed MessagePack maps, with approximately 4 MiB retained per failed parse and roughly 100 MiB after 25 failed parses as measured by the reporter. The flaw is triggered when strict_map_key=True (the default) rejects a map key that is neither str nor bytes: the decoded value has already been constructed and is never released, affecting both unpackb() and the streaming Unpacker API in releases up to 1.2.2. No public exploit code or active exploitation is identified in the available data, but the CVSS of 7.5 is availability-only (C:N/I:N/A:H), so impact is limited to denial of service rather than data disclosure or code execution; a public proof-of-concept reference exists in the advisory, though it is not verified as working exploit code.
Denial of service against an as-yet-unnamed HPE networking product lets remote, unauthenticated attackers degrade or halt availability, scored CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with impact confined entirely to availability. The affected feature, protocol, port and firmware branches are not described in the available sources and must be read from HPE bulletin hpesbnw05162en_us; no public exploit was identified at time of analysis and no EPSS or KEV signal was supplied. The vuln.today priority decision is this_week, reflecting a remotely reachable, low-complexity fault whose practical exposure scales with how far the device is reachable from untrusted networks.
Remote unauthenticated traffic against an HPE networking product can cause a high availability impact in CVE-2026-79893, according to the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5). No CVE description, CWE, affected model/version list, or fixed version is present in the supplied data, and the linked HPE bulletin could not be retrieved for confirmation; no public exploit was identified at time of analysis.
Remote, unauthenticated denial of service affecting HPE networking devices: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes a flaw that any network-reachable attacker can trigger with low complexity and no credentials or user interaction, degrading availability only. No CVE description, CWE mapping, or advisory text was available, so the specific feature, protocol, port, or configuration that must be exposed cannot be named, and exact affected models and firmware versions still need to be confirmed against HPE bulletin hpesbnw05162en_us. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the accompanying 'Information Disclosure' tag conflicts with the assessed C:N/I:N/A:H vector and should be reconciled with the vendor bulletin rather than treated as evidence of data exposure.
Denial of service against network-reachable HPE networking products: CVE-2026-79894 scores 7.5 on CVSS 3.1 from a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, meaning a remote attacker needs no credentials and no user interaction to degrade availability on an exposed instance. The trigger, affected version range and any required configuration are not described in the available sources and must be read from HPE advisory hpesbnw05162en_us, which is the sole reference supplied. No public exploit code or PoC reference was identified and there is no CISA KEV entry at time of analysis, so urgency derives from exposure of the affected interface rather than from observed attack activity.
Unauthenticated remote users may be able to read protected data from WordPress sites running ACF Extended through 0.9.2.7 because the plugin does not enforce an authorization check in some access-controlled functionality (CWE-862). The CVSS 3.1 score is 7.5 with confidentiality-only impact and no integrity or availability effect; the exact endpoint and configuration state required are not described in the available sources. Patchstack reported the issue, no CISA KEV entry is present, no public exploit identified at time of analysis, and vuln.today places it in the this_week priority tier.
Unauthenticated resource exhaustion in the Drupal Webform contrib module (all versions from 0.0.0 through 6.2.12, plus 6.3.0 through 6.3.1) lets remote attackers drive excessive resource allocation and degrade or deny availability of a Drupal site; confidentiality and integrity are unaffected (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). The flaw is CWE-770 (allocation without limits or throttling), and the vendor's stated remediation is to update the module per Drupal security advisory sa-contrib-2026-170. Risk signals are moderate rather than urgent: EPSS is 0.19% (8th percentile), there is no CISA KEV listing, and no public exploit has been identified at time of analysis, though the priority label places remediation in the current week.
Cross-namespace privilege escalation in OpenBao 2.3.0 through 2.6.2 allows an authenticated token holder to attach specially crafted policy names and thereby gain capabilities from policies cached in other namespaces, including the root namespace. The ACL policy cache does not keep cached policies scoped to their namespace, so the token can act across namespace boundaries; the referenced policies must already be in the in-memory LRU cache at both token creation and token use, and a referenced foreign root policy is granted only within the token's own namespace, which limits reliability and impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and multi-tenant deployments that depend on namespace isolation are the primary concern; fixed releases are 2.6.3 and 2.7.0.
Excessive CPU consumption during DNS name decompression in dnspython before 2.9.0 lets remote attackers degrade or deny service to applications that decode untrusted DNS wire-format messages. The parser function dns.name.from_wire_parser follows attacker-controlled compression pointer chains without a hop limit, so a single crafted message can force long pointer traversal; no authentication, user interaction, or non-default configuration is required once untrusted DNS data reaches the parser (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, A:H). The exposure is bounded by architecture rather than by exploit complexity: resolvers, DNS clients and any service that decodes DNS queries or responses from untrusted peers are affected, while systems that only parse trusted internal DNS data are not. No public exploit was identified at time of analysis and the issue is not in CISA KEV; the vendor-released patch is version 2.9.0, and the vendor states there are no known workarounds.
Memory exhaustion in GraphQL-core 3.2.3 through 3.2.11 and 3.3.0a3 through 3.3.0rc0 lets a remote unauthenticated attacker OOM-kill a GraphQL worker by sending a highly compressible comment-padded document that sails past the parser's max_tokens guard. The lexer still allocates and chains a Token object for every comment it skips, but those tokens were invisible to the counter, so a 38 MB payload parsed under max_tokens=5 produced roughly +92 MB of resident memory per the vendor's measurements. The vendor advisory ships a proof-of-concept that demonstrates the bypass; the flaw is not listed in CISA KEV and no in-the-wild exploitation is reported, and the vendor rates the impact as availability-only (CVSS 7.5, A:H, no confidentiality or integrity effect).
Unauthenticated memory exhaustion in LiteSpeed's lsquic HTTP/3 stack (all versions before 4.9.0) allows a remote attacker to drive a server or client into high memory use and ultimately denial of service by sending header blocks that pile up completed header sets faster than the application claims them, a technique the reporters call a QPACK amplification attack. Any lsquic-based endpoint that exposes HTTP/3 over UDP/QUIC is affected with default settings, since the library applied no cap on buffered header sets; no credentials or user interaction are needed and the vector scores 7.5 (AV:N/AC:L/PR:N/UI:N, availability-only). There is confirmed vendor activity in the form of upstream pull request 666 and the 4.9.0 release notes, and a public research write-up from FoxIO describes the attack class, but no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
Applications that configure the multer upload middleware (npm package, versions 2.0.0 through 2.4.x) with an asynchronous fileFilter can be crashed by a single aborted multipart request, taking down the entire Node.js process. When a request is aborted while one file's async fileFilter callback is still pending, that callback later resumes a parsing stream multer has already torn down, and the underlying busboy parser emits an error on a stream with no remaining error listener, which Node raises as an unhandled 'error' event and exits. The bug is unauthenticated and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), but it is conditional: uploads using a synchronous fileFilter, and the storage engine choice, do not matter. No public exploit code has been identified at time of analysis, and the issue is fixed in multer 2.5.0.
Stack-based out-of-bounds write in Silicon Labs EmberZNet 9.1.1 and earlier lets a device that has already joined a Zigbee network crash or potentially execute code on a peer node by returning a malformed Simple_Desc_req response - the attacker must wait for the victim to send the corresponding service-discovery request before replying. Exploitation requires prior network admission plus radio adjacency, so it is limited to attackers who already hold valid network credentials; no public exploit code was identified at time of analysis and the CVE is not in CISA KEV, though the potential impact (RCE on the target node) and the vendor advisory make it a this-week remediation item rather than an emergency.
Out-of-bounds write in Silicon Labs EmberZNet 9.1.1 and earlier allows a Zigbee node that has already joined the network to corrupt memory via a malformed Publish Price Matrix command, potentially achieving remote code execution on devices that implement the Smart Energy Price Cluster. The attacker must already hold network membership (a commissioned node with the network key) and be within adjacent RF range, and the target must specifically support the Price Cluster, which narrows exposure well below an internet-reachable RCE; no end-user interaction is needed. No public exploit code has been identified at time of analysis, and Silicon Labs documents the issue in advisory A-00000589.
PHP object injection in Roundcube Webmail's custom session decoder (rcube_session::unserialize()) affects releases before 1.6.20 and 1.7.x before 1.7.5, allowing an attacker who can write crafted session data to desynchronize the serialized stream and have subsequent session data interpreted as a serialized value. Exploitation is conditional rather than remote-unauthenticated against a default install: it requires the ability to influence stored session data (typically an authenticated session or a separate write primitive), high complexity to craft a valid desynchronizing payload, and a usable gadget chain in the installation or its dependencies before code execution or other impact follows. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the risk is best treated as genuine but conditional rather than a drop-everything emergency; vendor fixes are available in 1.6.20 and 1.7.5.
Goose's optional terminal integration feature captures shell command history and transmits it verbatim, with no redaction, to whichever Large Language Model provider endpoint is configured whenever a query is sent, so any secret typed into the terminal - API tokens, passwords, or environment variables carrying credentials - leaves the local trust boundary. The exposure is a confidentiality-only design flaw (CWE-497) rather than an attacker-triggered exploit: it requires the feature to be enabled and a human to enter the sensitive value (UI:R), and the recipient is the configured provider and its logs rather than an arbitrary remote party. Red Hat tracks the issue against Red Hat Enterprise Linux 9 and 10; no public exploit code has been identified at time of analysis, and the priority label is this_week.
Token forgery in the Authlib Python library before 1.9.1 lets a remote, unauthenticated attacker mint HS256, HS384 or HS512 tokens carrying arbitrary claims that Authlib accepts as genuinely signed, whenever the deploying application's HMAC verification key resolves to an empty string or empty bytes (for example an unset environment variable defaulted to '', a config column defaulting to '', or a key-resolver returning '' on a lookup miss). The exposure is strongly gated by that deployment precondition: applications that always supply a non-empty secret are not exploitable, and asymmetric RS/ES verification paths are unaffected, which is why the vector carries AC:H rather than a universally applicable rating. No public exploit code has been identified at time of analysis (the advisory supplies a prose reproduction description rather than weaponized code), CISA KEV does not list this issue, and the vendor has released 1.9.1 as the fix.
Authentication bypass in Authlib's deprecated-but-still-shipped authlib.jose module (1.3.1 through 1.8.0, fixed in 1.9.0) lets an unauthenticated remote attacker forge HS256 JSON Web Tokens with arbitrary subject and role claims using nothing but the issuer's public key, because the OctKey.import_key() guard tests for PEM armour only at byte zero while the PEM loaders skip leading whitespace, comment lines or a BOM. Two non-default deployment properties are required: the relying party uses the documented module-level jwt object (whose registry mixes HS* with RS*/ES*/PS*/EdDSA and whose decode exposes no algorithms parameter), and the verification key is stored as PEM or X.509 certificate text that does not begin at offset 0 with '-----BEGIN ' - a canonical PEM is still blocked, and pinning the algorithm (e.g. JsonWebToken(['RS256'])) is confirmed to reject the forgery. Rated CVSS 7.4 (AV:N/AC:H/PR:N/UI:N, C:H/I:H) and not listed in CISA KEV; the upstream advisory includes an end-to-end proof-of-concept reproduction against 1.8.0.
Stored cross-site scripting in OCO-Server 1.2.0 and earlier lets a crafted agent hostname execute JavaScript inside an administrator's authenticated session when the admin clicks one of the default VNC, RDP, SSH or Ping buttons on the computer details page. Reaching the sink requires three conditions to line up: the non-default 'agent-self-registration-enabled' setting must be turned on, the attacker must hold the shared 'agent-registration-key' used by all enrolled agents, and an administrator must then open the malicious 'ghost' computer's details page and activate a command button (PR:N with UI:R per the assessed vector, so no account is needed but admin interaction is). No CISA KEV entry, no confirmed public exploit code and no EPSS signal are associated with this issue at time of analysis - the GitHub advisory does include a step-by-step reproduction of the escaping bypass, making the flaw straightforward to verify, and the decision label places it in 'this_week' rather than an emergency tier.
Local non-administrative users on hosts running WatchGuard Agent can tamper with, append to, or delete the agent's security logs because the log directory is assigned incorrect permissions, and can stage further local attacks by placing executable content in a directory owned by a privileged service. The issue requires an existing local, authenticated account and the specific directory misconfiguration; there is no remote or unauthenticated path, and privilege escalation depends on a further execution mechanism that is not described in the available data. No public exploit identified at time of analysis, but the vendor has published an advisory and the issue is prioritized for this week.