Information disclosure in iTerm2 for macOS before 3.6.12 allows a local, unprivileged attacker to man-in-the-middle the terminal's mono-server session-restoration handshake and obtain sensitive session data (CVSS 3.1 base 5.5, CWE-200). The flaw lives in iTermFileDescriptorClientConnect(), which connects to a predictably named rendezvous socket (iTerm2.socket.<pid>) inside the world-writable, sticky shared temp directory (/var/tmp); an attacker who pre-creates that socket and wins a timing race can pass an attacker-controlled pty master back to the client via SCM_RIGHTS and read/interpose the restored session. Exploitation requires a local account on the same host, session restoration to be triggered, pid prediction and a race to be won, which is why this is a low-to-moderate priority rather than an urgent one; no public exploit has been identified at time of analysis and CISA SSVC records Exploitation: none, Automatable: no, Technical Impact: partial (the flaw is not in CISA KEV). The vendor fix is included in iTerm2 3.6.12.
Cross-namespace privilege escalation in HashiCorp Vault Enterprise allows an authenticated token holding a specially crafted policy name containing path-traversal constructs to have its policy resolved against a different namespace - including the root namespace - thereby gaining capabilities granted by policies it should never reach. Only Vault Enterprise deployments with namespaces actually configured are exposed; Vault Community Edition does not implement namespaces and is explicitly not affected. Exploitation requires a valid token (CVSS PR:L, authenticated) and the resulting privilege gain is bounded by whatever policies exist in the traversed namespace, making this a moderate-priority privilege-escalation issue rather than a mass-exploitation threat - no public exploit code has been identified at time of analysis and no EPSS or KEV data was supplied.
Stored cross-site scripting (CWE-79) in the Apache Impala Web UI query-plan view allows an authenticated SQL user holding only SELECT permission to embed JavaScript in a table alias, which then executes in the browser of any other user who opens that query plan. All Impala releases from 2.7.0 through 4.5.2 are affected; the vendor-released fix is version 4.5.3. Exploitation requires a valid Impala account plus a second user opening the crafted plan (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), and no public exploit identified at time of analysis. Risk is concentrated in multi-tenant clusters where low-trust analysts share an environment with administrators, since the injected script runs in the victim's browser origin rather than against the Impala backend.
Authenticated attackers holding only Subscriber-level access can tamper with the personal records of arbitrary LatePoint customers on WordPress sites running the Appointment Booking & Reservation plugin through version 5.6.9. The process_step_customer() handler merges attacker-supplied POST data into an existing customer record while checking only is_user_logged_in(), so any logged-in account can rewrite another customer's first name, last name, email, phone, and notes; where the non-default contact_merge setting is 'phone', this escalates to overwriting the victim's email and enabling account takeover via password reset. Exploitation requires a valid low-privilege session (PR:L), which is trivial on sites with open registration, and there is no public exploit identified at time of analysis, though the EPSS-style risk is moderate rather than critical.
wger before 2.6 contains a CSRF bypass (CWE-352) that lets an attacker-controlled web page silently rebind an authenticated trainer's session to an arbitrary user account. Because the trainer_login view (wger/core/views/user.py, ~lines 161-210) accepts GET and calls django_login() directly, it falls outside Django's CsrfViewMiddleware enforcement, which only checks unsafe methods; a single <img> tag pointing at /en/user/<user_pk>/trainer-login forces the victim's browser to issue the request with the session cookie attached. Exploitation is authenticated (CVSS PR:L) and requires user interaction (UI:R) - the trainer must hold trainer privileges and be lured onto the malicious page - and, per the assessed vector, it depends on a non-trivial SameSite=Lax bypass via the view's ?next= 302 redirect chain, which raises attack complexity to AC:H and makes this a targeted rather than opportunistic or wormable issue. No CISA KEV listing or independent public exploit code was identified at time of analysis, though the vendor advisory documents a Playwright-verified reproduction in Chromium 147.
Uncontrolled recursion in ImageMagick's CALS decoder lets a crafted CALS image exhaust the call stack and terminate the decoding process, giving remote unauthenticated attackers a low-impact denial of service (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). All ImageMagick releases prior to 7.1.2-30 (7.x branch) and prior to 6.9.13-55 (6.x branch) are affected; the vulnerable code path is coders/cals.c (ReadCALSImage). No public exploit code or confirmed active exploitation has been identified at time of analysis, and the practical reach is limited because the target must actually accept and decode the niche CALS Type 1 raster format rather than common JPEG/PNG inputs.
Denial of service in ImageMagick's Adobe Swatch Exchange (ASE) decoder allows a crafted ASE file to crash the process or trigger a long-running, resource-draining operation in all builds prior to 7.1.2-32. The flaw is reachable by unauthenticated remote attackers (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) wherever an application passes untrusted image data to ImageMagick with the ASE coder enabled, but impact is limited to availability (C:N/I:N/A:L) with no confidentiality or integrity effect. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; a vendor patch exists in 7.1.2-32, so the practical risk is moderate and primarily relevant to image-processing services, upload pipelines, and thumbnailers that accept arbitrary files.
Denial of service in ImageMagick caused by an infinite loop when parsing XMP metadata: a crafted XMP profile embedded in an image drives the internal XML entity parser into a non-terminating loop, so the image processing operation never completes and the worker thread or process burns CPU indefinitely. All builds prior to 7.1.2-32 (7.x line) and 6.9.13-57 (6.x line) are affected, including the many applications and language bindings that embed ImageMagick for thumbnail generation, upload validation, or media pipelines. The flaw is remotely triggerable and unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, score 5.3) wherever an attacker-supplied image reaches an automated parser; impact is limited to availability (hang/resource exhaustion) with no memory corruption, data disclosure, or code execution, and no public exploit code was identified at time of analysis.
Repeated processing of crafted Magick scripts in ImageMagick versions prior to 7.1.2-31 leaks a file descriptor on each invocation, allowing unauthenticated remote attackers to exhaust a process's open-file-descriptor table and deny service to applications that exercise the MagickWand script-token (MSL/conjure) path. The issue is rated CVSS 5.3 with availability-only impact (C:N/I:N/A:L) and requires sustained or repeated request volume to be effective, since a single invocation is harmless and the leak is cleared by a process restart. No public exploit identified at time of analysis, and the vendor-released patch is version 7.1.2-31.
Denial of service in ImageMagick versions prior to 7.1.2-32 allows remote, unauthenticated attackers to crash the process by supplying a crafted EXR image that triggers a heap buffer overflow in the EXR decoder. The vulnerability requires an ImageMagick build with EXR/OpenEXR delegate support enabled and an application that passes attacker-controlled EXR files to it; the impact is limited to a single-process crash (low availability). No public exploit code has been identified at time of analysis, and the vendor has released a patch in version 7.1.2-32.
An authenticated remote attacker with a valid SSH session can trigger a one-byte out-of-bounds stack write in wolfSSH v1.4.11 through v1.5.0 on non-Windows platforms by sending a crafted SFTP path, which can corrupt an adjacent stack value and crash the server process. The flaw is an unsigned integer underflow (CWE-191) in which the pointer/length math in wolfSSH_RealPath() and wstrncat() wraps once the accumulated path reaches roughly half the output buffer, causing a terminating null byte to be written one byte past the end of the stack buffer. The impact is limited to a single-byte corruption causing denial of service rather than arbitrary write or code execution, and no public exploit has been identified at time of analysis; a separate, more severe unbounded-copy condition exists only for third-party applications that call the public wolfSSH_RealPath() API with an output buffer smaller than the input path.
Resource exhaustion in ImageMagick's MAT image decoder (coders/mat.c) lets a crafted, highly compressed MAT file inflate far beyond the configured security-policy resource limit, writing an oversized temporary file to disk and consuming excessive storage until the host runs out of temp space. All ImageMagick releases before 7.1.2-30 (7.x line) and before 6.9.13-55 (6.x line) are affected, and the flaw is unauthenticated and remotely reachable per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, base 5.3) wherever untrusted image input is accepted, such as upload, conversion, or thumbnailing services; deployments that only process trusted local images face a much narrower exposure. Impact is confined to availability - there is no code execution, data disclosure, or integrity loss - and the vendor has shipped fixes in 7.1.2-30 and 6.9.13-55; no public exploit has been identified at time of analysis.
Denial-of-service in ImageMagick versions before 7.1.2-30 and 6.9.13-55 allows remote unauthenticated attackers to terminate an image-processing process by supplying a crafted image containing a deeply recursive XMP profile. The flaw only affects availability of the single ImageMagick task or worker-CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L-because the recursion limit is treated as a fatal error rather than a recoverable exception; there is no disclosure, corruption, or code execution. At time of analysis, no public exploit code or active exploitation was identified.
Formula evaluation in the Excelize Go library (versions 2.10.1 through 2.11.0) can be crashed by a spreadsheet whose cells contain a RIGHT() formula applied to supplementary-plane (non-BMP) text, because the function validates the requested length in UTF-16 code units but then slices a rune array using code-point counts, producing a negative slice index and a Go panic. This is a denial-of-service (availability-only) issue: per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, there is no confidentiality or integrity impact, and remote unauthenticated attackers can trigger it only if the host application calls Excelize's CalcCellValue on attacker-controlled workbook content. No public exploit code was identified at time of analysis, and although an upstream fix commit and pull request exist, no released patched version has been confirmed.
Splunk MCP Server versions below 1.2.1 transmit the Splunk platform authentication token of the user who executes a custom API tool to whatever URL that tool is configured to call, so an attacker who can author a custom tool pointing at a server they control can capture the victim's token and then act as that user. Exploitation is authenticated and requires user interaction: the attacker needs privileges to create or configure a custom API tool, and a separate victim holding a role with the mcp_tool_execute capability must actively run that tool (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:L). Real-world risk is moderate - it does not affect default deployments that make no use of custom API tools, and no public exploit has been identified at time of analysis. A vendor patch is available in Splunk MCP Server 1.2.1.
Improper access control in Splunk Enterprise (versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15) lets unauthenticated, network-positioned attackers reach functionality or data that should be restricted, exposing limited sensitive information with no integrity or availability impact (CVSS 3.1 base 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). The flaw is tracked as CWE-284 and was fixed by Splunk as part of a set of internally identified issues grouped by weakness class, each receiving its own CVE; no public exploit code has been identified at time of analysis, EPSS is a low 0.15% (3rd percentile), and CISA's SSVC assessment rates exploitation as none with partial technical impact. Because exploitation requires only network reachability of the affected interface and no credentials or user interaction, the practical exposure is driven mainly by whether a Splunk web/management interface is exposed beyond a trusted network segment.
Residual-data disclosure in the PostgreSQL JDBC Driver (pgjdbc) 42.7.4 through 42.7.13 allows an authenticated attacker who can influence how an application writes a value to recover SQL text and parameter values belonging to earlier statements on the same connection. When an application declares a value length larger than the bytes it actually supplies through PreparedStatement.setObject with a ByteStreamWriter, CopyIn.writeToCopy, PGCopyOutputStream.write, LargeObject.write, or Blob.setBytes, the driver pads the shortfall with whatever bytes remain in its send buffer instead of zeros, exposing up to 8192 bytes of recent traffic per value (16320 bytes when GSS encryption is in use); on a pooled connection those bytes may belong to other tenants or requests. Exploitation is conditional rather than trivial: the affected application must both store and read back such a padded value, its declared lengths must not always match its data, and any cross-request leakage depends on connection pooling, which is why the vendor rates this 5.3 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N). No public exploit code was identified at time of analysis, and there is no confirmed active exploitation (not in CISA KEV).
Silent threat-intelligence data loss occurs in MISP deployments that federate objects: when a user with object-creation privileges saves a MISP Object with an empty description, the originating instance accepts it, but the receiving instance during synchronization rejects it and silently drops the object together with all of its associated attributes. The flaw affects versions below 2.5.48 and requires an authenticated object creator (CVSS 4.0 PR:L) in a multi-instance sync topology, so it is a low-urgency data-integrity defect rather than an externally exploitable breach; no public exploit identified at time of analysis, and the root cause is fixed upstream by the validation change in MISP commit 6b1776f07.
MISP installations prior to 2.5.48 fail to refresh event correlations after an authenticated user with write access changes an event's distribution level or sharing group, because the before-save hook recorded the incoming (new) values instead of the already-persisted ones and the subsequent after-save comparison therefore found no change to act on. The practical effect is unintended information disclosure: correlations computed under a broader sharing scope can remain visible to members of the previously wider group even after the event has been moved into a more restrictive one, while distribution widening can conversely leave newly eligible correlations missing. Exploitation requires an authenticated user (CVSS PR:L) who can edit at least one existing event and who touches one of those two fields; no public exploit code has been identified at time of analysis and no CISA KEV entry exists, so this is a genuine-but-low-priority access control defect rather than an actively exploited flaw.
Authorization bypass in Obot 0.26.0 through 0.26.1 lets an authenticated user who matches any configured vMCP (virtual MCP) profile selector read prompts, resources, and resource templates belonging to components that profile never granted them, because profile enforcement in those releases was applied only to tools. Attackers abuse the vMCP owner's shared component connection to reach the ungranted prompt/resource endpoints over the network, yielding limited confidentiality impact with no integrity or availability effect (CVSS 5.3, CWE-863, PR:L, so valid authentication and a profile-segmented vMCP deployment are prerequisites). There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); vendor-released patch v0.26.2 closes the gap.
WP Rentals theme through 3.14.2 contains a missing authorization flaw (CWE-862) that lets unauthenticated remote attackers trigger unauthorized state-changing actions through incorrectly configured access controls. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N indicates no authentication, no user interaction, and only low integrity impact, with no confidentiality or availability impact, making this a moderate-priority issue rather than a top-tier emergency. No public exploit identified at time of analysis, and default installations running affected versions are exposed.
Unauthenticated information disclosure in the WP Chill Modula Image Gallery WordPress plugin (modula-best-grid-gallery) through version 3.0.11 lets remote attackers retrieve embedded sensitive data from a site without logging in or triggering any user interaction. The missing authorization check (CWE-862) affects an exposed plugin route, but impact is limited to low-confidentiality read access - there is no ability to modify content or execute code. No public exploit code has been identified at time of analysis and there is no indication of active exploitation, so this is a moderate, not high, priority; any network-reachable WordPress site running the vulnerable plugin build is exposed, while sites on a patched release or without the plugin active are unaffected.
Multiple memory-safety defects in X.Org X server prior to xorg-server-21.1.25 and Xwayland prior to xwayland-24.1.14 let an authenticated X client corrupt server heap and stack memory through crafted XKB, Present, XInput2, GLX and XFixes protocol requests, causing crashes or potentially arbitrary code execution inside the X server process. The flaws include a double free in XKB SetGeometry TextDoodad handling, use-after-frees in the Present cross-window notify path and in XInput passive grabs after XIRemoveMaster, heap overflows in GLX RenderLarge and XkbResizeKeyType, an XFixes pointer-barrier event buffer overflow, and an incomplete-fix out-of-bounds write in the XKB ChangeKeycodeRange path. Exploitation requires a connection already authorized to the X server (typically a local user session, an X11-forwarded session, or a multi-seat/shared-display host); no public exploit code and no confirmed in-the-wild exploitation have been identified at time of analysis, and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Pure-Wayland deployments that do not run Xwayland are not exposed.
Path traversal in Cisco Jabber for Android (com.cisco.im) before 15.3.1.311364 lets a locally installed malicious app with no requested permissions write attacker-controlled files into Jabber's private application data directories. The attacker sends a crafted shared content:// URI to Jabber's exported crosslaunch.share activity whose unsanitized ContentProvider display name contains '../' sequences; because that display name is used directly in file-path construction, files can be planted in databases/, shared_prefs/, no_backup/, and files/ with no user interaction. Impact is integrity-only and confined to Jabber's own sandbox (CVSS v4.0 5.1, AV:L/PR:N/UI:N/VC:N/VI:L/VA:N); no public exploit code and no confirmed active exploitation were identified at time of analysis, and the attack surface is local - the adversary must already have code executing on the device.
Path traversal in pulp-rpm's distribution tree publishing allows an authenticated user with sync or upload privileges to write files outside the intended task work area on the Pulp server. Crafted addon or variant ids in a .treeinfo file are used as directory names without sanitization, enabling the creation of new directories and writing of repository metadata and packages as the Pulp worker user. This is an integrity-only issue with no data disclosure or service disruption; no public exploit has been identified, and the practical risk is lower than the base CVSS 5.0 suggests due to the required privileges and the create-only constraint.
Sensitive information disclosure in the @backstage/plugin-kubernetes-backend package before version 0.21.9 allows an authenticated Backstage user who holds the standard Kubernetes resource read permission to retrieve Kubernetes Secret values that the plugin is designed to mask. The flaw is specifically reachable through the custom resources query path, where both the `data` and `stringData` fields of Secrets were returned unmasked, potentially exposing credentials and other confidential material held in connected clusters. Exposure is bounded by the Backstage service account's RBAC scope and by the targeted catalog entity's namespace and label selector, so deployments whose cluster credentials cannot read those resources are unaffected; there is no public exploit code identified at time of analysis and the issue carries a moderate CVSS of 5.0.
OS command injection in the web-based management interface of Cisco License On-Prem (formerly Cisco Smart Software Manager On-Prem) allows an authenticated remote attacker holding system administrator credentials to submit a crafted configuration update that is executed as root on the underlying operating system. Scored CVSS 4.9 (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H), the flaw is heavily constrained by its PR:H authentication prerequisite: because the attacker must already be a full administrator, the marginal capability gained is limited to shutting down or disrupting the host (availability impact only), which the assessed vector reflects with C:N/I:N/A:H. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; no EPSS score was supplied in the source data.
Authenticated SQL injection in the web-based management interface of Cisco License On-Prem (formerly Cisco Smart Software Manager On-Prem) lets an attacker who already holds valid administrative credentials send a crafted request that reads internal database contents normally hidden from administrative users, impacting confidentiality only. The flaw is rated CVSS 3.1 4.9 (Medium) with the vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, confirming it is remotely reachable but gated behind high privileges, with no integrity or availability impact and no user interaction required. There is no KEV listing and no public exploit identified at time of analysis, so the realistic risk is concentrated among insiders or anyone who has obtained administrator credentials for the license management portal rather than anonymous internet attackers.
Admission control bypass in Apache YuniKorn 1.9.0 and earlier allows an authenticated user who can already submit pod specs to the Kubernetes cluster to set the label 'app=yunikorn' on a pod, which causes the admission controller to skip its content checks on the 'user info' annotation. The attacker can therefore inject an arbitrary user identity, gaining access to queues they would not normally be permitted to use and distorting the user-based quota accounting that YuniKorn relies on for fair-share enforcement. Impact is confined to queue access and quota tracking (no data disclosure or denial of service), no public exploit code was identified at time of analysis, and the issue is fixed in 1.10.0 (tracked as YUNIKORN-3472).
Cross-site scripting in Veeam Backup Enterprise Manager lets an attacker run arbitrary script in the browser of a portal user who opens a crafted link, potentially exposing session data or allowing actions in the victim's authenticated context. Exploitation is not autonomous: the attacker must already be able to reach the portal with a valid low-privileged account (CVSS PR:L) and must then persuade a logged-in portal user to open the crafted link (UI:A), which is why this is rated a genuinely moderate, not high-priority, issue at 4.8. No public exploit code has been observed and the vulnerability is not in CISA KEV; no EPSS score was supplied with the source data, so likelihood should be treated as bounded by the social-engineering and authentication prerequisites rather than as an opportunistic mass-exploitation risk.
wger before 2.6 fails to revoke bearer-style API credentials on logout or password change, allowing an attacker who already holds a stolen DRF authtoken or JWT refresh token to continue accessing protected /api/v2/* endpoints. The assessed CVSS is 4.8 with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, reflecting a moderate defense-in-depth authentication weakness rather than a high-urgency flaw. Publicly available exploit code exists in the form of proof-of-concept replay steps, but exploitation requires prior token theft and the vulnerability provides no means to obtain the token; active exploitation is not confirmed.
UNIX symlink-following in ImageMagick's delegate cleanup path allows a local, already-privileged workflow to overwrite a target file with random data. Affected are ImageMagick versions prior to 7.1.2-32 and the ImageMagick6 branch prior to 6.9.13-57; the flaw (CWE-61) causes the shred/cleanup routine to ignore the MAGICK_SHRED_PASSES setting, so it follows attacker-planted symbolic links instead of honoring the configured shred behavior. The attack surface is narrow - CVSS 3.1 scores this 4.0 (AV:L/AC:H/PR:H/UI:R) with integrity-only impact - and no public exploit has been identified at time of analysis; there is no CISA KEV designation.
Python sandbox escape in Cisco NX-OS allows an authenticated, local attacker with low privileges to break out of the on-box Python interpreter sandbox and run arbitrary commands on the underlying operating system with that user's privileges. The issue arises from insufficient validation of user-supplied input in specific interpreter functions, affecting NX-OS software per the vendor CPE, and requires local access plus a valid low-privilege account rather than remote or unauthenticated access. No public exploit identified at time of analysis; CVSS 4.4 reflects limited confidentiality and integrity impact, and Cisco has published advisory cisco-sa-nxos-mppe-dhKZAFgb for affected platforms and versions.
Authenticated users of IBM Langflow OSS 1.0.0 through 1.12.2 can exhaust server resources by supplying a crafted ZIP archive to a code path that performs extraction, degrading or halting availability of the affected instance (CVSS 3.1 base 4.3, CWE-400). The flaw is reachable over the network by a low-privilege authenticated attacker (AV:N/PR:L/UI:N) and is limited to availability impact (C:N/I:N/A:L), with no data exposure, integrity loss, or code execution demonstrated. This is a low-to-moderate priority issue, not an urgent one: it is not confirmed as actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, though the mandatory credential requirement means exposure is confined to deployments with reachable ZIP-extraction functionality.
Splunk Enterprise deployments below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 leak other users' search activity to any authenticated user who does not hold the admin or power role, exposing search query text, job identifiers, dispatch parameters, result counts, and execution metadata through the REST API endpoint that lists search jobs. The flaw is an authorization enforcement gap: the listing API does not fully apply per-user checks before including job information belonging to other accounts, so an attacker with any low-privileged credentials can read searches they should never see. Scored CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), it is a low-severity confidentiality issue with no public exploit identified at time of analysis; because a valid account with PR:L is required, the practical exposure is an insider or post-credential-compromise scenario rather than a remote-unauthenticated attack.
Permission-filtered search in Backstage deployments that use an Elasticsearch or OpenSearch backend can return documents that a DENY policy should have withheld, because an empty list of permitted document types causes the engine to issue an unfiltered query across all indices instead of returning zero results. Only authenticated Backstage users (CVSS PR:L) are positioned to trigger this, and only when permission.enabled is set to true, the search backend is Elasticsearch/OpenSearch rather than the default in-memory engine, and the user is actually governed by a DENY policy for one or more search document types; the impact is limited to confidentiality (C:L) with no integrity or availability effect. The vendor has released fixes in @backstage/plugin-search-backend 2.1.6 and @backstage/plugin-search-backend-module-elasticsearch 1.8.7 (Backstage release v1.54.1), and there is no public exploit identified at time of analysis. Consistent with our independent assessment, this is a genuine but low-urgency information-disclosure issue rather than a high-priority emergency.
Low-privileged Splunk Enterprise users can retrieve the original source code of the Discover Splunk Observability Cloud app because production JavaScript bundles shipped with the app retain embedded source maps. The issue affects Splunk Enterprise below 10.4.3, below 10.2.7, and below 10.0.10 (10.0.x, 10.2.x, and 10.4.x branches); the 9.4.x line is explicitly not affected. Exploitation requires an authenticated account that does not hold the 'admin' or 'power' roles plus access to Splunk Web and the presence of the affected app, and the resulting disclosure is confined to the app's own source code with no integrity or availability impact; no public exploit has been identified at time of analysis, and vendor fixes are available.
Improper authorization in Splunk Enterprise (CWE-863) allows an authenticated user who does not hold the 'admin' or 'power' role to create or edit scripted lookup definitions through the raw transforms configuration write paths, which save those settings without applying the external lookup capability check that the standard lookup management UI enforces. Deployments running versions below 10.4.2, 10.2.6, 10.0.10, or 9.4.15 are affected, and exploitation requires a valid low-privilege account plus network access to the Splunk management/REST interface. The assessed CVSS 3.1 base score is 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), a moderate integrity-only authorization flaw; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Splunk Secure Gateway (an app bundled with Splunk Enterprise) fails to verify that a requesting user is authorized to ask for a payload signature, so any authenticated Splunk user who does not hold the 'admin' or 'power' roles can coerce the gateway into signing attacker-controlled content. Affected builds are Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, together with Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, as catalogued under CPE cpe:2.3:a:splunk:splunk_secure_gateway and cpe:2.3:a:splunk:splunk_enterprise. The impact is integrity-only (CVSS 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N): no confidentiality or availability effect, authenticated access and network reachability to the gateway are required, and there is no public exploit identified at time of analysis. Exploitation is confirmed as not appearing in CISA KEV, so the practical risk is confined to deployments where platform-signed payloads are subsequently trusted by downstream consumers.
Authenticated Splunk Enterprise users whose role holds the run_collect capability can bypass their role's configured index-access restrictions and write events into internal indexes they are not permitted to modify, because Splunk does not normalize whitespace in an index name before enforcing per-role index access. The flaw affects Splunk Enterprise releases below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and carries a CVSS 3.1 score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) - an integrity-only, low-severity impact with no disclosure of data and no service disruption; no public exploit identified at time of analysis.
Authenticated Splunk Enterprise users whose roles carry the run_collect capability can inject attacker-controlled content into system-level messages on the affected instance because the collect Search Processing Language (SPL) command fails to validate the index name before processing it. The flaw affects Splunk Enterprise 10.4 before 10.4.3, 10.2 before 10.2.7, 10.0 before 10.0.10, and 9.4 before 9.4.15, and is limited to a low integrity impact (CVSS 4.3, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) with no confidentiality or availability loss and no user interaction required. Exploitation requires valid credentials plus a role granting run_collect - a non-default prerequisite that standard or restricted roles lack - and no public exploit has been identified at time of analysis; vendor patches are available, and this is a low-priority issue despite being network-reachable.
Authenticated log injection in Splunk Enterprise allows a user whose role carries the read_o11y_content capability to forge entries in the app log through the REST API, but only on deployments where the Splunk App for Splunk O11y Cloud is present and enabled. The root cause is CWE-117 - the app writes user-supplied SignalFlow content into the app log without neutralizing it - producing a low-impact integrity-only result (CVSS 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) with no confidentiality or availability effect, and no public exploit identified at time of analysis. Only Splunk Enterprise releases below 10.4.3, 10.2.7 and 10.0.10 are affected; 9.4.x is explicitly not affected.
An authenticated user with the edit_spl2_module_permissions capability in Splunk Enterprise 10.0.x before 10.0.10, 10.2.x before 10.2.7, and 10.4.x before 10.4.3 can bypass an app-read authorization check via the REST management API to retrieve SPL2 module permission grants for apps they are not permitted to view. This low-severity authorization flaw (CVSS 4.3, CWE-639) results only in limited disclosure of permission-grant metadata, with no write or availability impact, and no public exploit has been identified at time of analysis. Splunk Enterprise 9.4.x is not affected.
Missing authorization in the Booktics WordPress plugin (versions up to and including 1.0.27) allows authenticated low-privilege users to access restricted data, resulting in limited confidentiality exposure. The flaw requires a valid account on the target site but no administrative rights and no user interaction, affecting only sites with the plugin installed and activated. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the CVSS score is 4.3 (moderate).
Missing authorization checks in the WPMU DEV Hustle WordPress plugin (wordpress-popup) through version 7.8.14.2 allow an authenticated user holding only a low-privileged account to read data exposed by an access-control-protected feature that should be restricted to higher-privileged roles. The exposure is read-only - confidentiality is the only impacted property (CVSS 3.1 score 4.3, vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) - and requires no user interaction and no administrative rights, so the practical barrier is simply having any valid account on the target site. There is no public exploit code identified at time of analysis and the issue is not flagged as actively exploited, so this should be handled as a routine patch item rather than an emergency; sites that permit open user registration face the greatest exposure.
Values written through the PostgreSQL JDBC Driver (pgjdbc) 42.7.4 and 42.7.5 over a GSS/Kerberos-encrypted connection can be silently stored by the server with bytes from the driver's previous GSS send buffer spliced into the front of them, so the persisted value holds earlier SQL text, other bind parameters, or earlier rows of the same batch instead of what the application supplied. Only connections where gssEncMode is set to prefer or require are affected - the default gssEncMode=allow and all non-GSS-encrypted connections are not - and the write must be at least as long as the driver's 16320-byte GSS buffer (with MIT Kerberos) and issued via setString, setBytes, a ByteStreamWriter, CopyIn.writeToCopy, or LargeObject.write. The CVSS vector (PR:L) indicates an authenticated database session is required, most qualifying writes fail outright with an ArrayIndexOutOfBoundsException rather than leaking, no public exploit is identified at time of analysis, and the upstream project rates this as a genuine but low-priority defect (CVSS 4.2) rather than a high-urgency threat.
Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 fails to reject native usernames that end with a trailing period, allowing an authenticated user who holds a role with the edit_user capability to create such an account. Because the trailing period is stripped or normalized when deriving the per-user directory path, two distinct native usernames can resolve to the same per-user configuration data, so user-management operations may act on the wrong account or fail outright. The practical exposure is bounded: exploitation requires a high-privilege administrative capability (edit_user) on native Splunk authentication, and the outcome is configuration-data collision and misdirected administrative actions rather than code execution or bulk data theft. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV; vendor-released fixes are available. This is a low-priority, low-real-risk issue despite affecting a widely deployed enterprise product.
Local arbitrary file write in Veeam Agent for Microsoft Windows allows an authenticated low-privileged local user to escalate integrity impact when an administrator installs or runs the agent. The vulnerability requires a privileged install/run action during the attack window and a non-trivial precondition such as controlling a target filesystem path (e.g., junction/symlink), making exploitation gated and low-to-moderate priority. No public exploit was identified at time of analysis.
AsyncHttpClient (AHC), a Java library for asynchronous HTTP requests, contains an incomplete cookie Domain validation flaw in its ThreadSafeCookieStore: from 2.16.0 through 2.16.1 and from 3.0.11 through 3.0.13, the store fails to apply private-section and default public-suffix rules, A-label (IDN) normalization, locale-independent lowercasing, and proper host-only and numeric/IP host checks, so a cookie set by one origin can be stored and later replayed to a different origin. Applications that share a single client instance across distinct trust domains can therefore receive attacker-injected cookies and may be exposed to session fixation; the assessed impact is integrity-only (CVSS 3.1 4.0, AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N) with no data disclosure. Exploitation is constrained by a non-default deployment pattern (per-origin or per-trust-boundary clients are not affected) and by the attacker needing to control or inject a Set-Cookie response from one of the shared origins; no public exploit code was identified at time of analysis, and the vendor has released a fix in version 3.0.14.