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.
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.
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.
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.
High-severity network-reachable flaw in HPE networking products can let attackers who already hold high-level privileges affect confidentiality, integrity, and availability. The exact affected models, firmware versions, and triggering feature are not described in the available sources; HPE bulletin hpesbnw05162en_us is the authoritative reference. No public exploit identified at time of analysis.
High-privilege attackers can achieve full confidentiality, integrity, and availability impact on affected HPE networking devices over the network, according to the CVSS 3.1 vector (7.2) with PR:H, AC:L, and UI:N. The high-privilege prerequisite excludes unauthenticated and low-privilege actors, but an already-authenticated administrator can reach the flaw without user interaction. No public exploit has been identified at time of analysis, and the exact product, versions, and trigger are not described in the supplied sources; HPE bulletin hpesbnw05162en_us should be consulted for scope.
Privileged network users can compromise the confidentiality, integrity, and availability of affected HPE products through a low-complexity, no-user-interaction flaw rated CVSS 3.1 base 7.2 HIGH. The specific HPE product, affected versions, and triggering feature are not described in the supplied sources; HPE advisory hpesbnw05162en_us is the only reference and must be consulted for scope. No public exploit code or CISA KEV entry is identified in the supplied data, and the PR:H requirement confines realistic exploitation to insiders or attackers using stolen high-privilege credentials.
Unauthenticated network reachability combined with existing high privileges on an affected HPE networking product can be leveraged to fully compromise confidentiality, integrity and availability (CVSS 7.2, AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). The high-privilege prerequisite (PR:H) is the primary limiting factor, so exposure is confined to administrators and to attackers who have already obtained privileged credentials; no user interaction is required and attack complexity is low once that access exists. The dataset is thin - no CVE description, no CWE and no CPE data were supplied, the trigger condition is not described in the available sources, and no public exploit has been identified at time of analysis (no KEV listing, no PoC reference). Priority is 'this_week' per the vuln.today decision label.
An attacker who already holds high administrative privileges on an affected, network-exposed HPE product can achieve high confidentiality, integrity, and availability impact (CVSS 7.2) through a low-complexity path that requires no user interaction. The supplied intelligence contains no CISA KEV confirmation and no public exploit identified at time of analysis, and it does not name the vulnerable component or describe the trigger; HPE bulletin hpesbnw05162en_us must be consulted for the affected product and version.
An authenticated administrator of an HPE networking product can reach a low-complexity, network-exposed flaw and achieve full confidentiality, integrity and availability impact on the affected component, according to an HPE security bulletin (document HPESBNW05162) scored at CVSS 3.1 base 7.2. The vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H confirms the issue is remotely reachable with no user interaction, but the high-privilege prerequisite (PR:H) means only an attacker who already holds an administrative or otherwise privileged account on the device can exploit it, so the realistic exposure is an insider, a compromised administrative credential, or a post-exploitation step, not anonymous internet attack. No public exploit code or proof-of-concept is referenced in the supplied sources, and the specific affected product, version, feature and protocol are not described in the available data.
Administrative users of an HPE networking product can abuse existing high privileges over the network to achieve full confidentiality, integrity, and availability impact under CVE-2026-79956 (CVSS 7.2). The flaw is remotely reachable with low complexity and no user interaction, but the PR:H vector means only attackers who already hold administrative access can exploit it, making insider or post-compromise abuse the realistic path. No public exploit was identified at time of analysis, and the HPE advisory is the primary source because no description or CWE was supplied.
NoSQL injection in MongoDB C# Driver before 3.13.0 lets an authenticated application user redirect LINQ-generated field paths by supplying dictionary keys, field names, or array-filter identifiers that contain dot or dollar characters. This can expose other users' documents, widen update operations beyond intended data, or write malformed fields that leave stored documents unreadable until repaired. The issue is a moderate-priority concern limited to applications that pass attacker-controllable input into field-name positions; no public exploit was identified at time of analysis, and it is fixed in driver 3.13.0.
Server-side request forgery filter bypass in Roundcube Webmail 1.6.14-1.6.19 and 1.7.0-1.7.4 allows an authenticated webmail user (authoritative assessment: PR:L; the supplied CVSS vector lists PR:N) to submit URLs containing NAT64 prefixes 64:ff9b::/96 or 64:ff9b:1::/48, or the unspecified address ::/128, that evade rcube_utils::is_local_url() and reach loopback, link-local, or cloud metadata services. The supplied CVSS score is 7.2 with changed scope and partial confidentiality/integrity impact; real-world impact depends on the server being able to route the NAT64-mapped addresses to live internal services. No public exploit identified at time of analysis.
IMAP command injection in Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 allows an authenticated remote user to inject CRLF sequences through the _flag parameter of the mail/mark action and execute arbitrary IMAP commands in their mail session. The CVSS 3.1 score is 7.1 (High) with PR:L, and default installations are vulnerable because mail/mark is available to normal logged-in users, so risk centers on compromised accounts, malicious insiders, or credentialed attackers rather than anonymous scanning. Vendor fixes are available in 1.6.20 and 1.7.5; no public exploit identified at time of analysis and no CISA KEV confirmation was provided.
Authentication bypass in Silicon Labs Connect SDK 4.3.1 and earlier, plus Flex SDK 3.7.7 and earlier, allows an attacker positioned within radio range of the device to send a protocol message carrying invalid security settings that the stack fails to verify, causing the message to be processed as though it came from a trusted source. Successful exploitation disrupts network operation (high integrity and availability impact) but cannot recover the Network Key or decrypt traffic, so confidentiality is explicitly unaffected. The trigger is unauthenticated, low complexity, and requires no user interaction, though the attacker must be within adjacent-network/radio range and cannot reach the device over the internet; no public exploit code or active exploitation is identified in the available data, and patch is available from the vendor.
Arbitrary local file read in Mistune's opt-in Include directive (all versions before 3.3.0, with 3.2.0 confirmed) lets an attacker who controls Markdown that an application renders through Markdown.read(path) disclose files readable by the rendering process - the advisory demonstrates reading /etc/passwd - and, when the included non-Markdown file contains markup, smuggle unescaped HTML or script into the rendered page. Exploitation requires two non-default conditions in the host application: the Include directive must be enabled via RSTDirective([Include()]), and the untrusted Markdown must be loaded from disk with Markdown.read(path); passing Markdown as a plain string does not trigger the flaw, and no public exploit is confirmed beyond the PoC reference published in the GHSA advisory. Confidentiality impact is the primary concern (assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N), and the vendor fix is Mistune 3.3.0.
Authenticated clients of the Crawl4AI Docker API server (0.9.0 through 0.9.4) can freeze the entire service, including the /health endpoint, by submitting a catastrophic-backtracking regular expression in a /crawl request body through RegexExtractionStrategy.custom, RegexChunking.patterns, or a schema field of type 'regex' in the JSON extraction strategies. Python's re engine does not release the GIL while matching, so a single crafted pattern combined with an attacker-influenced page blocks the event loop and the crawl deadline cannot interrupt it. Exploitation requires a valid API bearer token and a crawl target whose text triggers the backtracking; a public proof-of-concept request is published in the vendor advisory, no active exploitation has been reported, and the vendor fixed the issue in 0.9.5. The library imported directly is not exposed unless the host application itself feeds untrusted regexes into these strategies.
Integrity-only NoSQL injection in the MongoDB C# Driver update-statement builder allows an authenticated application user with ordinary read-write access to influence update logic, potentially modifying or deleting stored data the application did not intend to change. The flaw is tracked as CSHARP-6168 and affects releases before 3.13.0; exploitation depends on the application passing attacker-influenced values directly into the affected update builder surface, so it is not reachable against a hardened application that does not do so. No public exploit was identified in the provided intelligence at time of analysis, and the primary remediation is upgrading to MongoDB .NET/C# Driver 3.13.0.
Authorization bypass in the Grav Flex Objects plugin 1.4.0 through 1.4.16 lets authenticated, non-super users holding api.access plus either admin.pages or admin.configuration.pages read page source and frontmatter, modify content, and delete pages they are explicitly denied, because the generic /api/v1/flex-objects/pages routes enforce only directory-level admin.pages checks instead of the Pages API's api.pages.read/write and page-level permission rules. Scored 7.1 with an independent assessment of high confidentiality and high integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), the flaw is a privilege-escalation problem past intended per-page restrictions rather than an anonymous compromise path - the attacker must already hold a valid restricted admin or editor account, and super-user accounts are unaffected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate-priority remediation item rather than a drop-everything emergency.
Authorization bypass (CWE-639) in the MarcosCamara01 Ecommerce Template lets any authenticated shopper delete or change the cart and wishlist rows that belong to other accounts on the same installation, because the Drizzle repository calls match rows on the primary key alone and the per-user PostgreSQL row level security policies never take effect for the application's connection. Affected deployments are those using the template's default single-DATABASE_URL setup, where the migration role that creates the tables is also the runtime role, so PostgreSQL does not apply RLS to the table owner; cart_items.id and wishlist.id are sequential bigserial values, making other users' row identifiers enumerable, and the update path returns the modified row including its owning user_id. A valid low-privileged account on the target is required and no user interaction is needed; no public exploit identified at time of analysis, and vendor-side code addressing both the RLS enforcement gap and the missing ownership predicates is available in the referenced commit.
Price substitution in the MarcosCamara01 Ecommerce Template cart and checkout flow lets any authenticated customer pay a cheap Stripe price while ordering a more expensive variant, producing paid orders and order records that do not match. The flaw exists because /api/user/cart stores client-supplied variantId and stripeId independently, and /api/stripe/payment charges the stored stripeId while the checkout.session.completed webhook records the variantId. The vendor commit e6b364cd668f2ba875cfa7f6d55c63e771715df7 removes stripeId from client input and resolves pricing server-side; a public PoC reference exists in the vendor regression test and is not verified as working exploit code, and no CISA KEV active exploitation is reported in the supplied data.
Authenticated restricted TLS clients on Incus can retrieve S3 access and secret keys for storage buckets in the default project, enabling them to read, modify, or delete bucket objects directly through the S3 endpoint. The issue affects Incus 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 when the TLS authorizer is in use; OpenFGA deployments are not affected. No public exploit identified at time of analysis.
Canonical Juju 4.0 through 4.0.15 leaves the model unit-resources download route without an authorization check, so any principal already authenticated to the controller - a unit agent, or a human user holding only 'login' permission with no access to the target model - can request an arbitrary unit in an arbitrary model and read that application's charm resources, including container-registry credentials. The fix in Juju 4.0.16 binds the unit named in the request URL to the authenticated identity, refusing cross-unit and cross-model access. No public exploit code was identified at time of analysis, and the flaw requires a valid controller credential, though one at the lowest privilege tier and against default deployments.
Client-side field-level encryption (CSFLE) in the MongoDB C# / .NET Driver before 3.13.0 can silently fail to encrypt fields that an application designated for protection, so data intended to be ciphertext is stored and returned in cleartext. The flaw sits in the schema-construction component that turns caller-supplied field identifiers into pattern expressions, so it only affects applications that build automatic-encryption schemas through the affected PatternProperty overload; the same defect can also make a rule apply more broadly than intended. Discovery requires no user interaction, and the party reading the unprotected values only needs ordinary authenticated read access to the stored data (PR:L in the assessed vector) - not the encryption keys - though it is not a default configuration and no public exploit was identified at time of analysis; the driver fixes it in 3.13.0.
Denial of service with a limited information-disclosure component affects HPE networking devices, where an attacker positioned on an adjacent network segment can degrade availability severely (A:H) and potentially read a small amount of data (C:L) without authentication (PR:N) or user interaction (UI:N). The 7.1 severity is moderated in practice by the adjacency precondition (AV:A), which confines realistic exposure to insiders, on-path attackers, or hosts on an already-compromised Layer-2 segment rather than arbitrary internet clients. No CVE description was supplied and no public exploit code has been identified at time of analysis, so the specific vulnerable feature, protocol and affected models must be confirmed against HPE bulletin hpesbnw05162en_us.
Adjacent-network attackers can cause high availability impact and minor integrity changes on HPE networking devices through CVE-2026-95710, which carries a CVSS 3.1 base score of 7.1. The vector (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H) means an attacker on the same Layer-2 segment or a logically adjacent network needs no credentials and no user interaction, and the flaw is not reachable from the open internet without first reaching that segment. No public exploit code or CISA KEV entry was identified at time of analysis, and the trigger itself is not described in the available sources.
Information disclosure in HPE networking products (CVSS 7.1) could let an unauthenticated attacker with adjacent-network access expose or affect sensitive data when a legitimate user is induced to perform an action, though a high-complexity precondition limits reliable exploitation. The affected models, firmware branches, and vulnerable feature are not specified in the available data; HPE bulletin hpesbnw05162en_us is the authoritative reference for scope and fixes. No public exploit code is identified at time of analysis, and the assessed vector rates confidentiality, integrity, and availability impact as High.
Presigned S3 upload URLs issued by Incus's built-in in-process S3 server can be abused to read other objects in the same bucket, because the server validates SigV4 signatures only over the headers the client lists in X-Amz-SignedHeaders and never rejects additional unsigned x-amz-* headers (the SigV2 presigned path omits CanonicalizedAmzHeaders entirely). Anyone holding a presigned PUT URL for one key - no bucket credentials required - can attach an unsigned X-Amz-Copy-Source header and have the server copy an arbitrary object in that bucket onto the granted key under the signer's credentials, leaking the source object's ETag and, where the attacker can also read the granted key (for example via a matching presigned download URL), its full contents. Incus 7.0.0 through 7.0.1 and 7.1.0 through 7.4.x are affected when a storage bucket on a local storage pool is served by the built-in S3 server and the bucket listener (core.storage_buckets_address) is enabled, which is not the default; Ceph radosgw buckets are unaffected. Authentication is required in the sense that a valid presigned grant must already be held, and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the WP Mailster WordPress plugin (all versions through 1.9.1.0) lets an attacker who can place content into the plugin's stored data have script execute in a different security context when a victim loads a page that renders that content. The published score is CVSS 7.1, while the assessed vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, so exploitation requires victim interaction (a page load) and the outcome is scope change with low confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis and there is no CISA KEV entry; the available data lists no fixed plugin version.
Stored cross-site scripting in CodePeople's Contact Form Email WordPress plugin through 1.3.68 lets an attacker persist script payloads through form submission fields or form configuration and execute them when a victim, most plausibly an administrator reviewing submissions in wp-admin, views the stored content. The CVSS vector carries PR:N and UI:R, so the reported path is unauthenticated but requires victim interaction; the independent assessment notes the privilege needed to persist the payload is unconfirmed, and practical risk is lower if authentication is required. No public exploit code or CISA KEV confirmation is provided, and the plugin must be installed and active for exposure.