Unauthenticated information disclosure in the WordPress Booking Package plugin before 1.7.31 exposes calendar-account configuration data, including administrator notification email addresses, to any remote attacker who can reach the site. The plugin returns these sensitive settings from a response handler without performing authorization checks, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials, interaction, or special configuration are needed. Publicly available exploit code exists and a vendor patch is available, but the impact is limited to confidentiality of configuration values with no write access or code execution, keeping overall risk moderate rather than critical.
Missing authorization in the SmartyParcel WordPress plugin before 1.23.4 allows unauthenticated remote attackers to download shipping labels belonging to arbitrary orders, exposing customer names, addresses and phone numbers. The flaw is a classic insecure direct object reference (CWE-639) affecting any site running the plugin with generated labels in place; publicly available exploit code exists, and CISA KEV status does not apply, so active exploitation in the wild is not confirmed. With a CVSS base score of 5.3 (confidentiality-only impact), EPSS-style urgency should be moderate, but the privacy and regulatory implications of leaked shipping data make timely patching worthwhile.
Booking Package WordPress plugin before 1.7.31 allows unauthenticated remote attackers to reset its premium subscription state, disabling paid features on affected sites. The issue is a missing authorization and validity check in the subscription-reset code path, requiring no credentials or user interaction, and is limited to integrity impact on the plugin’s premium status. Publicly available exploit code exists, and the vendor has released version 1.7.31 to address the flaw; risk is bounded to sites actively using the paid tier.
Unauthenticated attackers can mark bookings as paid and confirmed in the Ettrick Escape Room Booking WordPress plugin before 1.3.1 because the plugin does not verify payment status with the payment provider before changing booking state. This is a medium-severity (CVSS 5.3) missing-authorization/business-logic flaw (CWE-862) affecting sites that use the plugin's booking and payment-confirmation workflow; publicly available exploit code exists, but no CISA KEV active exploitation is recorded. Successful abuse is limited to integrity impact-fraudulent paid/confirmed bookings and possible revenue loss-without code execution, data disclosure, or site takeover.
Unauthenticated payment-state forgery in the Payment Gateway for Idram WordPress plugin before 2.1.6 lets remote attackers mark arbitrary orders as paid - or force them into a failed state - by submitting forged payment notifications. The root cause is that the merchant credentials used to compute the notification checksum are empty by default, so no meaningful signature check occurs on unconfigured installations; an attacker only needs the callback URL and a target order identifier. Publicly available exploit code exists and WPScan documented the issue, with a CVSS of 5.3 reflecting integrity-only impact (C:N/I:L/A:N) bounded to WooCommerce-style order payment status rather than data disclosure or site takeover; EPSS and KEV data were not provided, and the independent assessment rates this a moderate, not top-tier, priority.
Unauthenticated lead export in the Click n Chat (Chat Widget Integration) WordPress plugin, versions 1.0.4 up to but not including 1.1.3, allows any remote visitor to download the full set of captured contact records - names, email addresses and phone numbers - with no authentication, no user interaction and no non-default configuration required. Publicly available exploit code exists, and the issue was reported by WPScan as an information disclosure flaw (CWE-200). A vendor patch is available in version 1.1.3, which closes the missing authorization check on the lead-export handler.
Unauthenticated order manipulation in the Wava Payment Plugin for WordPress (0.3.1 through 0.3.9) allows remote attackers to forge payment-provider notifications and change WooCommerce order states, including marking unpaid orders paid and completed and cancelling other customers' orders. Versions through 0.3.7 also return billing details such as names, addresses, emails, and phone numbers to the same unauthenticated caller. Publicly available exploit code exists, and the vendor has released 0.3.10 to address the missing authorization and authenticity checks.
Broken access control in the TI WooCommerce Wishlist WordPress plugin before 2.13.0 lets unauthenticated remote attackers read the metadata and item contents of private wishlists by querying the plugin's REST API directly, bypassing the owner-only checks enforced on the front-end. No account, privilege, or user interaction is needed - only a vulnerable installation and a way to reference the target wishlist identifiers - and exposure is limited to wishlist metadata and contents rather than broader site or credential data. Publicly available exploit code exists for this CWE-284 flaw (CVSS 5.3, unauthenticated), though it is not confirmed as actively exploited in the wild.
Unauthenticated attackers can mark a pending WooCommerce order as paid by replaying a payment identifier captured from any single genuine SUMIT transaction, because the SUMIT Payment Gateway plugin before 4.0.0 fails to bind the provider payment to the target order and does not compare the payment amount to the order total. The flaw is CWE-863 incorrect authorization and is rated CVSS 5.3 (Medium) with a network vector requiring no privileges or user interaction. Publicly available exploit code exists; no CISA KEV active-exploitation confirmation was provided.
Unauthenticated attackers can retrieve other customers' order details - billing location, purchased products, and totals - from WordPress sites running Kliken: Ads + Pixel for Meta before 1.2.3 by enumerating predictable order IDs. The flaw is an authorization bypass (CWE-639) rated CVSS 5.3 with only confidentiality impact, and publicly available exploit code exists. A vendor patch is available in version 1.2.3.
Simple Shopping Cart WordPress plugin before 5.3.3 allows unauthenticated attackers to have their orders marked as paid by submitting a PayPal payment notification for a transaction sent to a PayPal account they control, because the default configuration does not verify that the receiving account belongs to the site owner. Publicly available exploit code exists for this issue, while active exploitation is not confirmed in the provided data. The flaw is rated CVSS 5.3 and affects integrity only, with no confidentiality or availability impact.
Unauthenticated payment-notification forgery in the Payment Gateway for Telcell WordPress plugin (versions before 2.0.5) allows remote attackers to mark arbitrary WooCommerce orders as paid, because the secret used to sign incoming callbacks is empty by default and therefore trivially reproducible. The same callback handler can also flip an attacker-chosen order to failed when an invalid signature is supplied, giving a second abuse path. Publicly available exploit code exists; there is no CISA KEV entry, and the impact is bounded to integrity of order/payment state (CVSS 5.3, I:L only), with risk concentrated on stores that leave the gateway at default settings.
Price tampering in the LatePoint WordPress booking plugin before 5.7.5 lets a remote unauthenticated visitor manipulate the client-supplied value that sets the booking charge, so the amount due can be resolved to zero and the visitor walks away with a confirmed appointment and a recorded order without paying. Any WordPress site running a pre-5.7.5 LatePoint installation that sells chargeable appointments through the plugin's own checkout flow is exposed; no account, special role, or non-default configuration is needed, only the ability to submit a booking (CVSS 3.1: AV:N/AC:L/PR:N/UI:N, 5.3, limited to integrity impact). Publicly available exploit code exists, and the issue is documented in the WPScan vulnerability database; the practical exposure is a direct revenue-loss and booking-fraud vector rather than a data breach. No CISA KEV entry was provided, so active exploitation is not confirmed.
Cross-site scripting (XSS) in the web interfaces of Cisco Emergency Responder, Cisco Unified CM, Unified CM IM&P, Cisco Unity Connection, Prime Collaboration Deployment, and Unified CM SME lets unauthenticated, network-positioned attackers inject script that executes when a victim interacts with crafted content. The CVSS 9.3 vector reflects network reachability, low attack complexity, no attacker authentication, required victim interaction, scope change, and high confidentiality/integrity impact, so meaningful exploitation generally depends on luring an authenticated administrative user. No public exploit code or CISA KEV entry was identified at time of analysis, and Cisco's advisory describes hardening releases rather than a single emergency patch.
Blind SQL injection in WPdreams Ajax Search Lite through version 4.14.6 allows unauthenticated remote attackers to extract sensitive data from the WordPress database by inferring query results. The plugin's public-facing search endpoint is exposed to anonymous visitors by design, so no authentication or user interaction is required. No public exploit code was identified at the time of analysis, but the vulnerability is fully automatable and high severity.
PHPOffice PHPPresentation through version 1.2.0 will pass attacker-controlled serialized data to unserialize() when IOFactory::load() is pointed at a crafted presentation file, letting remote unauthenticated attackers instantiate arbitrary PHP objects inside the hosting application. Where a usable gadget chain exists in the application or its dependencies, that object instantiation escalates to code execution or arbitrary file writes; without gadgets the realistic outcome is object injection or denial of service, which is why the assessed vector marks a present attack requirement (AT:P) rather than an unconditional network exploit. No confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis, but the library is widely embedded in document-conversion and upload pipelines, so exposure depends entirely on whether the vulnerable Serialized reader path is reachable from untrusted input.
Remote code execution in vLLM 0.7.3 through 0.30.x lets remote, unauthenticated clients run arbitrary Python inside the API server process when a multimodal request to the /tokenize endpoint supplies a crafted mm_processor_kwargs.code_revision value, which vLLM forwards to Transformers AutoProcessor.from_pretrained and uses to select which revision of the model repository's dynamic processor code gets imported. Exploitation requires two non-default preconditions: the server must be running with trust_remote_code enabled, and the attacker must control (or be able to write) a revision in the model repository being served, so default hardened deployments with remote code disabled are not exposed. No public exploit code or confirmed active exploitation was identified at time of analysis, but the impact for exposed configurations is full confidentiality, integrity and availability loss (vendor CVSS 4.0 score 9.2; our independent CVSS 3.1 assessment of 8.1 reflects the high attack complexity created by the prerequisites).
Server-side request forgery in LocalAI 4.6.0 through 4.11.0 allows unauthenticated remote attackers to make the service fetch internal resources by submitting a gallery config URL to POST /models/apply that redirects to loopback, private, link-local, or cloud metadata addresses and returns the internal response as gallery content. The issue is a redirect-based bypass of the gallery URL guard; exploitation requires the model-management API to be network-reachable and the attacker to control or influence a redirecting server, and high impact depends on reachable internal services or a metadata endpoint. No public exploit identified at time of analysis.
Authentication bypass in Trigger.dev self-hosted v4 deployments (npm trigger.dev <=4.5.5) allows unauthenticated attackers to forge magic-link tokens and log in as any email address when the default MAGIC_LINK_SECRET from hosting/docker/.env.example is still in use. Publicly available exploit code exists; successful exploitation can expose or modify tenant data, and may escalate to full infrastructure compromise because default Postgres, Redis, and ClickHouse credentials are reachable from runner containers on the same Docker network. The issue is limited to Docker Compose deployments that never rotated the example secrets and left WHITELISTED_EMAILS unset; the hosted SaaS and instances with regenerated secrets or an email allowlist are not affected.
Unauthenticated role forgery in Apache Pulsar lets a client present a forged or unsigned JSON Web Token listing arbitrary roles and have those roles honored when the broker uses MultiRolesTokenAuthorizationProvider alongside a non-empty anonymousUserRole. The flaw is reachable over the broker's HTTP surfaces, including the admin REST API and the WebSocket API, where failed credentials can fall back to the anonymous role while the original Authorization header is retained and later trusted without signature verification; an attacker who names a role configured in superUserRoles can obtain super-user access to tenants, namespaces, topics, permissions and broker configuration. Only deployments combining MultiRolesTokenAuthorizationProvider with a non-empty anonymousUserRole and the fallback conditions are exposed, while installations using the default PulsarAuthorizationProvider, another authorization provider, or an unset anonymousUserRole are unaffected. Vendor-released patch: 4.0.14 and 4.2.5; no public exploit identified at time of analysis, and exploitation also requires the specific non-default configuration described.
Response-framing desync in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0) allows a malformed 302 response that should have been rejected as a parse error to pass the rejection path through the Transfer-Encoding: chunked carve-out, so the proxy stores and serves a response that different peers interpret differently. Per the CVSS vector the issue is remote and unauthenticated (AV:N/AC:L/PR:N/UI:N, scope changed, I:H/C:L), enabling cache poisoning and response-framing desync against deployments acting as caching or forwarding proxies. No public exploit code or CISA KEV entry is associated at time of analysis; the practical precondition is that a suitable malformed upstream response actually traverses the proxy. Fixed versions 9.2.16, 10.1.5, and 10.2.1 are published by the vendor.
Authorization bypass in the Sentry Next.js SDK affects @sentry/nextjs from 9.36.0 before 9.47.2, 10.x before 10.75.2, and 11.0.0-rc.1 when the webpack integration is used with a configured tunnelRoute. An unauthenticated remote request can reach an application route that collides with the tunnel path, or resolves through a root dynamic segment, without the middleware authorization that would otherwise run; exploitation additionally requires a webpack build, a colliding route, and middleware being the sole authorization control. The flaw is fixed in 9.47.2, 10.75.2, and 11.0.0-rc.1, and no public exploit was identified at time of analysis.
Session token replay in the WebFig management interface of MikroTik RouterOS (through 7.24.5) lets an attacker who already possesses a captured administrator session token bypass authentication and gain persistent administrative access, because tokens stay valid across newly negotiated ECDH sessions until the device's login store is explicitly cleared. The 9.1 CVSS v4 score reflects high confidentiality and integrity impact, but its AC:H rating is meaningful: the attacker must first obtain a valid token out-of-band, for example through the unfixed transport-layer exposure described in CVE-2025-61481, and no user interaction is needed once a token is held. No public exploit identified at time of analysis and no CISA KEV entry exists; devices whose WebFig interface is not reachable from untrusted networks are not realistically exposed.
Request smuggling in Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0 allows remote unauthenticated attackers to have a later request read as leftover body data on a recycled origin connection, enabling access-control bypass, cross-user request disruption, and cache poisoning. The attacker must declare a body via Content-Length or Expect: 100-continue but never fully send it, then win a timing window while ATS returns the origin connection to its shared keep-alive pool. No public exploit has been identified at time of analysis, but the default configuration is affected and exploitation is probabilistic rather than guaranteed.
Acronis Cyber Infrastructure (ACI) does not properly enforce authorization in its management/API layer, letting remote attackers disclose sensitive information and manipulate protected resources (CVSS 9.1, AV:N/AC:L/PR:N/UI:N, C:H/I:H). The vendor vector specifies PR:N, so no authentication, user interaction, or special configuration is documented as required; exposure is mainly bounded by whether the ACI management interface is reachable from untrusted networks. Affected deployments are those running builds earlier than 6.0.1-112, 6.1.1-64, and 6.2.1-71. No public exploit code and no CISA KEV entry were identified at time of analysis, so active exploitation is not confirmed.
Out-of-bounds write flaws in the Cisco Snort 3 inspection engine allow remote, unauthenticated attackers to corrupt memory in any deployment where Snort 3 parses attacker-reachable network traffic, potentially leading to arbitrary code execution or a denial-of-service condition in the inspection process. The affected code ships not only as the standalone open-source Snort 3 project but also embedded in Cisco Secure Firewall Threat Defense (FTD), the Cisco UTD Snort IPS engine, and Cisco Cyber Vision, so exposure spans both Cisco appliances and third-party deployments of the open-source engine. Cisco addressed the issues through hardening releases produced during an internal security review, but the advisory groups the findings without publishing per-defect trigger details, and no public exploit code has been identified at time of analysis; CVSS AC:H reflects that an attacker must land traffic on the specific vulnerable parsing path rather than send a trivially repeatable packet.
Broken authorization in the Uncanny Toolkit for LearnDash WordPress plugin before 3.8.2 lets a subsite administrator on a multisite network flip arbitrary network users outside their own site to an 'unverified' state, locking those accounts out of the site. The flaw only manifests on WordPress multisite installs - default single-site deployments are not affected - and requires the attacker to already hold elevated subsite-admin privileges, so realistic exposure is confined to insider or compromised-admin privilege abuse rather than remote anonymous attack. Publicly available exploit code exists and a vendor fix (3.8.2) is released; there is no confidentiality exposure or code execution, only a targeted denial of login service.
Code execution can be triggered in applications that use sharp before 0.35.4 on glibc-based Linux to decode untrusted AVIF or HEIF images, because the bundled libheif dependency contains heap buffer overflow flaws (CWE-122). The CVE record rates this 8.9 under CVSS 4.0 with a local vector and PR:N, but the independent assessment emphasizes that exploitation requires sharp's VipsForeignLoadHeif path to process attacker-controlled image data and is substantially easier when the Node.js executable is not compiled as PIE; non-glibc deployments and PIE builds reduce exposure. No public exploit identified at time of analysis, and no CISA KEV confirmation was provided.
Broken access control in WPZOOM Portfolio Lite before 1.4.34 allows authenticated users with the WordPress Contributor role or higher to convert other users' posts and pages into portfolio items, altering order and removing the content from its original listings and URLs. The flaw requires only a low-privilege account and no victim interaction, so it is most impactful on multi-author sites or those with open contributor registration; publicly available exploit code exists. The vendor has released version 1.4.34 to address the missing authorization check.
Missing authorization in the AI Engine WordPress plugin before 3.8.6 allows an authenticated user holding the Editor role or higher to rewrite the title and excerpt of arbitrary objects on the site - including navigation menus, block templates, global styles and WooCommerce coupons that the caller has no capability to edit. The defect is a missing per-object capability check (CWE-862) on the title/excerpt update path and is present in default plugin behavior, requiring no special configuration to reach. Impact is bounded to those two fields rather than full content control, and publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) has been reported; this is a genuine but moderate-priority issue rather than a critical one, and the vendor has fixed it in 3.8.6.
Code execution can occur in sharp versions before 0.35.5 when an application decodes attacker-supplied SVG images through the bundled librsvg, which contains the use-after-free tracked as CVE-2026-96889. The RCE outcome is constrained to glibc-based Linux and Node.js executables that are not built as PIE, so many distribution-packaged Node.js deployments are protected from code execution even though the underlying memory corruption remains. No public exploit was identified at time of analysis; SVG decoding can be disabled with sharp.block as a workaround.
Heap-based buffer overflow in NoMachine's mDNS resource-record parsing enables unauthenticated, network-adjacent attackers to execute arbitrary code on affected installations, running in the context of the NoMachine service account. Exploitation requires the attacker to be on the same local link/multicast domain as the target (AV:A), with NoMachine's mDNS service discovery active and reachable; no authentication (PR:N) or user interaction (UI:N) is required, and complexity is low (AC:L), giving a CVSS 8.8 impact of high confidentiality, integrity, and availability. Originally reported through Trend Micro ZDI as ZDI-CAN-30982 (advisory ZDI-26-710), the flaw is a classic CWE-122 length-validation failure; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the practical risk is gated by the adjacency precondition rather than internet-wide reachability.
PHP object injection in Duplicator and Duplicator Pro allows unauthenticated attackers to plant a serialized object in public site content that is later deserialized when an administrator builds a package and then runs a migration or import with database search-and-replace. In Duplicator through 1.5.17 the bundled Requests 1.7 POP chain can escalate this to operating-system command execution; in Duplicator Pro through 4.6.10 the IndexList destructor gadget is limited to deleting an attacker-selected file when the containing directory is writable by the installer PHP process, with site takeover possible only through the additional wp-config.php deletion, race, and attacker-controlled database steps. This is a high-priority but heavily gated issue, and no public exploit identified at time of analysis.
PHP object injection in the GS Plugins WordPress Team Members plugin through version 2.8.2 lets an authenticated low-privilege user submit crafted serialized data to a plugin feature that invokes PHP unserialize(), enabling object injection that can lead to high confidentiality, integrity, and availability impact if a usable POP gadget chain exists. The issue is network-reachable, requires no user interaction, and is scored CVSS 3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); no public exploit identified at time of analysis and no CISA KEV active exploitation was reported.
PHP object injection in GS Pins for Pinterest 1.9.2 and earlier allows an authenticated low-privilege WordPress user to pass crafted serialized data into PHP unserialize(), potentially enabling object injection and, if a usable POP gadget chain exists, code execution or other high-impact actions. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit was identified at time of analysis. Sites running the plugin should treat low-privilege accounts as an attack prerequisite and remove or mitigate the plugin until a fix is confirmed.
Privilege escalation in pfSense-pkg-RESTAPI before 2.9.0 lets an authenticated account holding the scoped settings-sync permission modify REST API configuration secrets through the HA sync endpoint, elevating that non-administrative user to full administrator. The issue is confined to installations of the unofficial pfSense REST API package and is not exploitable against a default configuration with no scoped-permission accounts; no public exploit code was identified at time of analysis. CVSS scores it 8.8, but practical risk is bounded by the deliberately assigned sync privilege and any REST API ACL or firewall restrictions on API endpoints.
Authorization bypass in Jupyter Server gateway mode (2.0.0 through 2.6.0) allows a restricted authenticated user to open an upstream kernel channel and execute code even when the configured Authorizer explicitly denies the kernel execute action, exposing kernel data and credentials and permitting environment modification or disruption. Exploitation requires a non-default GatewayClient.url configuration (or, in 2.6.0 and later, manual registration of the deprecated jupyter_server.gateway.handlers module) plus a valid low-privileged account whose policy denies execute; the default gateway configuration in 2.6.0 and later is fixed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the CVSS 8.8 score reflects high confidentiality, integrity, and availability impact under that gated configuration.
SQL injection in Cisco Unified CM and related Cisco collaboration products (Emergency Responder, Unified CM IM&P, Unified CM SME, and Unity Connection) allows authenticated remote attackers with low privileges to execute arbitrary SQL against the underlying database, with high impact to confidentiality, integrity, and availability (CVSS 8.8). The flaw is network-reachable, low-complexity, and requires no user interaction, but exploitation requires a valid low-privilege account on an affected web or administrative interface. No public exploit was identified at time of analysis.
Cisco Unified CM and related Cisco UC products contain improper input validation that can let authenticated low-privilege attackers with network access affect confidentiality, integrity, and availability. Exploitation requires valid low-privilege credentials and reachability to the affected management/application interface, with no user interaction needed; the assessed CVSS 3.1 vector is 8.8 HIGH with high confidentiality, integrity, and availability impact. No public exploit was identified at time of analysis, and no CISA KEV status is indicated in the supplied data.
Unauthenticated remote attackers can retrieve a signed Biscuit identity token belonging to any approved, bootstrap-enrolled peer from the Google OSS Agent Mesh (SAM) control plane in versions 0.1.0-alpha.1 through 0.1.0-alpha.8, then replay it as a bearer credential to read mesh authorization policies via /policies and to overwrite advertised router multiaddrs via /routers/lease. The chain requires only the peer_id that the unauthenticated GET /info endpoint discloses, so no credentials or user interaction are needed; a related POST /enroll flaw let any bootstrap-token holder re-fetch another peer's credential. Vendor-released patch: 0.1.0-alpha.9, which enforces cryptographic proof of possession of the enrollment private key on credential-releasing endpoints, adds rate limiting, and validates router lease addresses; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated Splunk Enterprise users whose roles include the schedule_search capability can use the scheduled search workflow to run risky SPL commands that the platform would normally block, resulting in disclosure or alteration of Splunk data or disruption of Splunk availability. The issue affects Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and is fixed in those releases. The assessed vector requires low privileges (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact; no public exploit identified at time of analysis.
Prototype pollution in toml-node before 5.0.1 lets an attacker who controls TOML input passed to toml.parse() inject properties into Object.prototype by combining colliding quoted dotted-key bookkeeping with a table-array declaration. The flaw can corrupt objects created elsewhere in the same Node.js or browser process, producing high integrity and availability impact with no confidentiality impact; no public exploit identified at time of analysis.
Path traversal in Jupyter nbconvert 5.4.0 through 7.17.1 allows a remote unauthenticated attacker to write attacker-controlled output data to arbitrary filesystem locations writable by the victim's user account. Exploitation requires the victim to convert an attacker-supplied notebook using the markdown, LaTeX, reStructuredText, or AsciiDoc exporter, not the default HTML exporter; the assessed impact is high integrity and low availability with no confidentiality impact. No public exploit was identified at time of analysis, and version 7.17.2 contains the vendor fix.
Authenticated low-privileged Splunk Enterprise users can escalate to arbitrary OS command execution on search head cluster members by reconstructing the PostgreSQL sidecar superuser password. The password is deterministically derived from the search head cluster identifier, which surfaces in search job logs readable by users who do not hold the 'admin' or 'power' roles. Deployments below 10.4.4 and below 10.2.8 are affected where a search head cluster runs the PostgreSQL sidecar service; no public exploit code has been identified at time of analysis, but the flaw carries a CVSS score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and warrants prompt patching in SHC environments.
Node.js startup snapshots can carry a stale crypto random cache into restored processes, so processes restored from a snapshot may emit repeated or predictable random values (CVE-2026-106074, CWE-330). Only applications that build or run using the snapshot feature - --build-snapshot / --snapshot-blob workflows or single-executable applications - are in scope, and the affected builds are Node.js 26.12.0, 24.22.0 and 22.23.3; impact is capped at low confidentiality and low integrity with no availability effect. No confirmed active exploitation (not in CISA KEV) has been reported, and while a public PoC reference exists, it is not verified as working exploit code.
Unauthenticated remote attackers can drive HTTP transactions to completion against Apache Traffic Server instances that have loaded the experimental WebAssembly plugin and trigger a use-after-free in the plugin's transaction-close handler, producing memory corruption that primarily threatens availability (high) with a limited integrity impact. The same plugin also passes unvalidated guest-supplied metric IDs straight into ATS's internal stats API, a path that requires the attacker to control or supply the wasm guest module. Exposure is limited to deployments that explicitly enable this non-default experimental plugin on versions 10.0.0 through 10.1.4 or 10.2.0; no public exploit identified at time of analysis.
Cisco/Splunk has shipped a software hardening release for Splunk SOAR that fixes multiple internally discovered flaws, one of which is tracked as CVE-2026-76526, an improper-neutralization (CWE-707) weakness rated 8.8. Splunk SOAR deployments below version 8.7.0 are affected, and exploitation requires a valid low-privilege authenticated account (CVSS PR:L, AV:N) - there is no anonymous path, but no user interaction is needed, and successful abuse can fully compromise confidentiality, integrity and availability of the SOAR instance. No public exploit code has been identified at time of analysis and EPSS is low (0.17%, 6th percentile), so this is a this-week patch item rather than an emergency, though the appliance's role as an automation and credential hub raises the value of compromising it.
Splunk Enterprise releases 10.2 before 10.2.8, 10.0 before 10.0.11, 9.4 before 9.4.16 and 10.4 before 10.4.4 carry multiple internally discovered resource-lifetime flaws (CWE-664) that a remote attacker holding low-privileged credentials can use to gain high confidentiality, integrity and availability impact, with low attack complexity and no user interaction (CVSS 3.1 base 8.8, PR:L). Cisco/Splunk shipped the fixes in a consolidated hardening release rather than a single-feature advisory, so the specific triggering component is not described in the available sources; the only confirmed limiting factor is the need for valid low-privileged access. There is no CISA KEV entry and no confirmed working exploit code, and EPSS is low at 0.17% (6th percentile), though the vendor's this-week prioritisation and the breadth of the hardening release justify prompt upgrading.
Arbitrary file write in Dulwich before 1.2.9 on Windows can be escalated to remote code execution when an unauthenticated remote attacker convinces a victim or an automated Windows CI runner to clone or check out a malicious repository. A crafted Git tree entry whose name is a DOS drive-letter prefix such as 'C:' passes NTFS validation and causes os.path.join to discard the intended worktree root, allowing writes to locations like the user's .gitconfig or Startup folder. A proof-of-concept generator is described in the vendor advisory, so publicly available exploit code exists.
Trigger.dev self-hosted and cloud deployments through version 4.7.6 expose a supervisor workload API endpoint (attempts/start) that performs no ownership check, letting a caller act on runs and snapshots belonging to other deployments. Exploitation is not anonymous: an attacker must already hold a legitimate low-privilege run/snapshot pair and must reach the supervisor over an adjacent network segment, after which they can read resolved environment variables and run JWTs or start, complete, and suspend other tenants' runs. There is no public exploit code or confirmed active exploitation (no CISA KEV), and the vendor advisory GHSA-jc26-22qp-cgqj is the authoritative reference; risk concentrates in multi-tenant or hosted installations where untrusted workloads share a supervisor, while single-tenant self-hosted setups with no third-party workloads are materially less exposed.