Candlepin, the entitlement and subscription management engine behind Red Hat Satellite 6, contains an authorization-logic flaw in its central access control filter: when an API operation verifies multiple @Verify-annotated parameters, access is granted if any one of them is permitted rather than requiring permission on all of them. An authenticated attacker with a low-privilege account who legitimately can reach the first referenced object can therefore pass authorization checks on later parameters and, provided they know the victim resource identifiers, read consumer information or modify entitlements and subscription resources - including objects belonging to other organizations (CVSS 3.1: 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Exploitation requires a valid account and prior knowledge of target consumer UUIDs, entitlement IDs, or subscription resource IDs, and is limited to endpoints that evaluate more than one verified parameter; no public exploit code was identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
An integer underflow in Zephyr's IEEE 802.15.4 link-layer security receive path lets any attacker within radio range drive an out-of-bounds read and in-place write of up to roughly 240 bytes into the network buffer pool. When CONFIG_NET_L2_IEEE802154_SECURITY is enabled and a security session at a level other than IEEE802154_SECURITY_LEVEL_NONE is established, a single crafted data frame whose payload is shorter than the configured authentication tag makes payload_len wrap to as large as 255, so CCM decryption reads several hundred bytes past the end of the exactly-sized receive buffer - and this happens before the tag is ever verified, so no key material, association, authentication, or user interaction is needed (CVSS 8.1, AV:A/AC:L/PR:N/UI:N). The primary impact is memory corruption and denial of service rather than information disclosure, since the out-of-bounds bytes are not attacker-chosen and the frame is dropped when tag verification fails; no public exploit code was identified at time of analysis, and exposure is limited to builds that enable this non-default, experimental security feature.
VMware Workstation and Fusion (25H2 and 26H1) carry a stack-based buffer overflow in the HGFS Host-Guest File System component used for shared folders, letting an attacker who already holds administrative privileges inside a guest VM execute code as the VMX process on the host and thereby break the guest-to-host isolation boundary. This is a VMware guest-to-host escape, a genuinely high-value class of flaw because it defeats the primary security boundary of virtualization, though the realities of exploitation are gated: the attacker needs a pre-existing local admin foothold in the guest, HGFS must be reachable, and the CVSS vector's AC:H signals that the overflow must be shaped to bypass host memory protections. Vendor-released patch is available in Workstation/Fusion 26H1u1; no CISA KEV listing and no public exploit code was identified at time of analysis, and no EPSS score was supplied in the source data, so the practical risk concentrates on multi-tenant, untrusted-guest, or shared-lab deployments rather than single-user desktops.
Arbitrary code execution on the Vault host is achievable in HashiCorp Vault and Vault Enterprise when a privileged operator restores a crafted Integrated Storage (Raft) snapshot in a deployment configured with Shamir seals and an external plugin directory, because stored plugin catalog entries are not consistently verified to reference binaries inside that configured directory (CWE-22 path traversal). The attacker must already hold the high privileges needed to restore a Raft snapshot (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H), and exploitation also depends on the non-default Shamir-seal-plus-external-plugin-directory configuration, so this is a genuinely serious but condition-gated vulnerability rather than a mass-exploitation threat; clusters using auto-unseal or without an external plugin directory are not affected by this path. No public exploit identified at time of analysis, and vendor-released fixes are available in Vault Community Edition 2.1.2 and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.
Command injection in the OpenSSH ssh client before version 10.6 occurs when a username supplied on the command line contains a '$' or '\' character, which is not correctly escaped or quoted and can be interpreted as shell syntax. The flaw is assessed as CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and requires the victim to invoke ssh with an attacker-controlled username - for example from a crafted ssh:// URI, a shared connection string, or a script or alias - so it is not remotely triggerable against a default server. No public exploit was identified at time of analysis, EPSS is 0.13% (2nd percentile), and the issue does not appear on CISA KEV; this is a genuine but not emergency-grade issue, and patched clients (10.6 and later) are unaffected.
Post-authentication OS command injection in SonicWall SMA1000 firmware (12.5.0-02952 and 12.4.3-03526 platform-hotfixes and older) allows an attacker with administrator credentials to execute arbitrary OS commands, leading to remote code execution. The independent assessment rates this as a moderate priority due to the requirement for valid administrator credentials and undisclosed 'specific conditions'; no public exploit code has been identified at time of analysis. The vendor CVSS vector (AV:L) differs from the assessed network vector, and exploitability may be further limited by configuration-specific factors.
Buffer overflow in X.Org X Server's XFixes extension (and Xwayland) allows an authenticated local X client to trigger a stack or heap overflow by creating more than 100 pointer barriers and generating pointer motion events, potentially leading to arbitrary code execution or denial of service. The flaw, tracked as CVE-2026-93519, affects X.Org X server versions prior to 21.1.25 and Xwayland versions prior to 24.1.14. No public exploit code or active exploitation has been identified at time of analysis; independent assessment assigns a CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Heap buffer overflow in the glamor acceleration path of the X.Org X server (and Xwayland) allows an authenticated local X client to corrupt the server's heap, with the potential for code execution or a server crash, although reliable exploitation is assessed as high-complexity. The flaw is addressed in the October 2026 X.Org security release, which fixes a bundle of XKB, Present, XInput, GLX and XFixes issues in xorg-server 21.1.25 and xwayland 24.1.14. No public exploit code and no CISA KEV entry were identified at time of analysis; no CVSS vector or EPSS score was supplied for this CVE, and the input itself does not contain a CVE-2026-93523 advisory entry, so the mapping of this identifier to the glamor size-calculation overflow is inferred from an associated upstream commit rather than confirmed by vendor text.
Heap buffer overflow in X.Org X Server before 21.1.15 and XWayland before 24.1.14 allows an authenticated X client to crash the display server or potentially execute code in the X server context by exercising the CopyArea CPU-to-FBO path where a size mismatch overflows a heap buffer. The flaw is CWE-122 with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting local, low-complexity access requiring an authenticated X client connection and high confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis, and vendor patches are available in the fixed releases and referenced Red Hat errata.
An integer overflow in the glamor rendering upload path of the X.Org X server (and Xwayland) can produce an undersized heap allocation and subsequent out-of-bounds memory writes, and is one of the issues bundled into the October 2026 X.Org security advisory tracked as CVE-2026-93521. The affected code is in builds of X.Org X server prior to xorg-server-21.1.25 and Xwayland prior to xwayland-24.1.14; exploitation requires an authenticated local X client able to reach a depth-24 drawable uploaded into a depth-32 pixmap while glamor GL acceleration is active, with the byte_stride * height computation in glamor_upload_boxes overflowing before XNFalloc is called. No public exploit code, EPSS score, CWE assignment, or CISA KEV entry was present in the input, so there is no public exploit identified at time of analysis, and because the per-CVE description for CVE-2026-93521 is absent from the truncated advisory these conditions are inferred from the associated commit and should be verified against the vendor's per-CVE entry.
Heap buffer overflow in X.Org X Server versions prior to 21.1.25 and in Xwayland prior to 24.1.14 stems from an integer truncation inside XkbResizeKeyType(), where the computed key-symbol count is stored in an unsigned short and wraps for sufficiently large nTotal values, yielding an undersized allocation that subsequent writes overflow. The X.Org advisory of October 2026 states the trigger is an X client sending crafted XKB requests that resize a key type with a large nTotal; because no CVSS vector was supplied, authentication requirements are not confirmed from available data, and the advisory's own phrasing describes the actor as an authenticated X client. No CVSS score, EPSS estimate, CISA KEV listing, or public exploit code was available at time of analysis, so no public exploit identified at time of analysis; the vendor assesses the impact as heap corruption that can lead to arbitrary code execution or denial of service. This CVE is one of seven flaws disclosed together in the same X.Org security advisory.
A double free in the X.Org X server's XKB SetGeometry request handler (CVE-2026-88812) lets an authenticated X client that is already able to connect to the target display corrupt heap memory by sending a crafted XkbSetGeometry request containing a malformed TextDoodad entry, with outcomes ranging from a server crash to potential arbitrary code execution. Only builds of xorg-server prior to 21.1.25 and Xwayland prior to 24.1.14 are affected, and the XKB extension required for the trigger is standard and enabled by default. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning exploitation presupposes an existing local/same-session X connection rather than remote or unauthenticated access, and no public exploit code, EPSS score, or CISA KEV entry appears in the supplied data, so reliable code execution additionally depends on defeating heap allocator hardening.
Heap buffer overflow in X.Org X Server before 2.1.25 and XWayland before 24.1.14 allows an authenticated X client to crash the display server or potentially execute code in the X server context. The flaw is a local, low-privilege issue (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N) triggered when XKB ChangeKeycodeRange requests use a keycode range that mismatches XkbAllocNames buffer size calculations. No CISA KEV listing, EPSS score, or public exploit was identified at time of analysis; vendor patches are available.
Remote code execution on TechDocs build hosts affects Backstage deployments running the @backstage/plugin-techdocs-node mkdocs generator prior to 1.14.6 (and 1.15.x prior to 1.15.4). An authenticated user holding the privilege to register or update catalog entities can commit a crafted mkdocs.yml whose markdown_extensions entries point at dangerous Python callables such as subprocess:Popen, os:system, or plantuml_markdown's plantuml_cmd, which mkdocs instantiates and executes while building the docs; the flaw requires authentication and an entity-registration permission rather than anonymous access, and deployments that publish pre-built docs or build in isolated disposable runners have a much smaller blast radius. The upstream fix, which extends MkDocs configuration sanitization to cover nested configuration keys, hyphenated extension names, and theme options, is available in vendor-released versions 1.14.6 and 1.15.4, and no public exploit code tied to this CVE was identified at time of analysis beyond the payload fixtures included in the upstream fix commit.
Windows logon token reuse in wolfSSHd versions 1.4.15 through 1.5.0 allows an authenticated low-privilege user to impersonate a higher-privileged user by exploiting a failure to release the Windows logon token between authenticated connections. Only the Windows port is affected; non-Windows builds are explicitly unaffected. Exploitation depends on a timing overlap with a privileged user's login (assessed as a race condition, AT:P in CVSS 4.0 and AC:H in the independent CVSS 3.1 assessment), and no public exploit identified at time of analysis. Upstream fix commits are available and the vendor advisory is published; severity is assessed as High (CVSS 4.0 7.7).
Improper validation of MkDocs Markdown extension configuration in Backstage's TechDocs Node package (@backstage/plugin-techdocs-node) lets an authenticated user who can register or modify documentation sources make a TechDocs build read files or fetch URLs outside the documentation boundary, potentially exposing backend-host data or internal network resources (path traversal, CWE-22). Affected versions are those before 1.14.6 on the 1.14 line and before 1.15.4 on the 1.15 line; the impact is changed-scope with high confidentiality loss and no integrity or availability impact, and it applies to deployments where the Backstage backend generates TechDocs from those sources rather than relying on externally sandboxed CI. Exploitation requires an authenticated principal with documentation-source registration or modification rights (PR:L), and no public exploit code has been identified at time of analysis; this is assessed as a credible, patch-worthy issue rather than an emergency, with vendor fixes released in @backstage/plugin-techdocs-node 1.14.6 and 1.15.4 plus pymdown-extensions 10.21.3 or newer.
Command injection in Backstage's TechDocs build pipeline allows an authenticated user who can register or modify a documentation source to run arbitrary commands inside the TechDocs backend or its build container by supplying a crafted mkdocs.yml. Exploitation requires write access to a catalog entity or docs source that is processed by local or docker-based TechDocs generation, and the impact is confined to resources reachable by the backend or its build container; deployments that only publish externally pre-built documentation are not exposed. The issue is fixed in @backstage/plugin-techdocs-node 1.14.6 and 1.15.4, is rated CVSS 7.7 with high attack complexity, low privileges, and scope change, and there is no public exploit identified at time of analysis.
Derivation of IFTTT pairing tokens in the ASUS RT-BE57 router allows an unauthenticated attacker within adjacent wireless range to read or modify router settings, provided they can observe a live administrator-initiated IFTTT pairing exchange. The root cause is a predictable seed in the pairing-token PRNG (CWE-337), which lets the attacker reconstruct the token from values emitted during that session; the assessed CVSS 3.1 vector (AV:A/AC:H/PR:N/UI:N, C:H/I:H/A:H) reflects full impact to router confidentiality, integrity, and availability but heavily conditioned on adjacency, high attack complexity, and a present attack requirement. Exploitation is therefore opportunistic rather than on-demand and only affects deployments where IFTTT integration is actually used; no public exploit code has been identified at time of analysis.
Local privilege escalation in Splunk Enterprise on Linux (versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15) allows an attacker who can already run commands as the OS account running Splunk Enterprise to inject operating-system commands into installation content that a subsequent root-privileged Linux package upgrade will execute as root. The flaw is conditional: the attacker must modify the installation and then a privileged package upgrade must occur, so there is no at-will escalation. No public exploit or confirmed active exploitation was identified at time of analysis.
A time-of-check to time-of-use (TOCTOU) race condition in Anthropic's Claude Code CLI allows an attacker who already has write access to a shared project workspace to atomically replace a project file with a symlink after the agent has validated the path but before it writes, causing Claude Code to follow the link and write to an arbitrary file outside the sandbox - for example a shell configuration file that will later be sourced by a higher-privileged session. Exploitation is bounded: it requires local write access to a workspace shared with a more privileged Claude Code session, requires winning a narrow timing race rather than triggering deterministically, and requires the privileged session to actually perform a write to the targeted path; single-user installations with no shared workspace are not exposed. There is no indication of active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis, though Anthropic has already shipped the fix through the standard auto-update channel, leaving only manual-update holdouts at risk.
OS command injection in GitAhead through 2.7.1 lets a malicious repository execute arbitrary shell commands on the victim's machine during a routine checkout or staging operation, because crafted filenames are substituted unescaped into Git clean/smudge filter commands that GitAhead runs through 'bash -c'. The attack is remote and unauthenticated from the attacker's side (CVSS 4.0 vector PR:N) but high in complexity and gated on user interaction: the victim must clone or open an untrusted repository and then perform a checkout or stage, making it a conditional code-execution risk rather than a mass-exploitation event. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though the 7.7 base score and full confidentiality/integrity/availability impact justify prompt attention for anyone using the client with repositories of uncertain provenance.
OS command injection in Rundeck before 6.2.0 allows an authenticated user who holds job-run permission to execute arbitrary commands on Windows target nodes by injecting cmd.exe metacharacters (such as &&, |, >, and ;) into free-text job option values. The flaw is in CLIUtils.quoteWindowsCMDArg, which wraps arguments in single quotes - characters that have no quoting semantics in cmd.exe - so the injected command is interpreted rather than treated as literal text, and it executes with the privileges of the node executor's credentials. Exploitation requires a valid account with job-run authorization, a job that targets Windows nodes through the cmd.exe-based executor, and a job definition that exposes a free-text option passed as a command argument; there is no public exploit identified at time of analysis, and the independent assessment rates this a moderate-priority authenticated RCE rather than a drive-by critical issue.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, low-privilege authenticated attacker to retrieve objects belonging to other users by manipulating a user-controlled identifier that the application fails to scope to the requesting principal (CWE-639, IDOR-style authorization bypass). The flaw is network-reachable with low attack complexity and no user interaction, but it is gated on the attacker already holding valid credentials for a low-privilege account (CVSS PR:L); the assessed impact is a high-confidentiality, read-only exposure with no demonstrated integrity or availability effect, so realistic risk concentrates in multi-user or multi-tenant Langflow deployments where a low-trust account can reach another tenant's or user's data. Patch available per vendor advisory (IBM support node 7290694); no public exploit identified at time of analysis.
Authentication bypass in Express Gateway through 1.16.11 (CWE-287) allows an attacker holding any valid registered OAuth 2.0 client credentials and the identifier portion of another user's refresh token to exchange it for that user's access token, impersonating the victim against OAuth2-protected APIs. The flaw is in the refresh_token grant handler, which never validates the refresh token's secret component or confirms that the presenting client is the client the token was issued to, producing high confidentiality and integrity impact with no availability impact (CVSS 4.0 base 7.6). Exploitation requires low-privileged access plus prior knowledge of the victim's token identifier (PR:L, AC:H), making this a targeted impersonation primitive rather than a mass-exploitable bug; no public exploit identified at time of analysis.
Certificate validation in OpenSSL-based OpenVPN builds can be subverted by a peer that presents an X.509 certificate whose subject contains an embedded NULL byte, because subject-name parsing truncates at the NUL and the crafted certificate is then accepted as valid (CVE-2026-84790, CWE-158). Deployments at risk are OpenSSL-linked OpenVPN builds older than v2.7.8 that use certificate-based authentication; mbedTLS builds are not affected because they always rejected such certificates. The independent assessment scores this as CVSS:3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (attack complexity high, some position/privilege assumed, and a purpose-built certificate required), which is consistent with the vendor's CVSS 4.0 score of 7.6 High; no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
Connection-pool reuse in the AsyncHttpClient (AHC) Java library, versions prior to 3.0.13 and 2.16.1, lets an authenticated principal inherit an HTTP/1.1 socket that was authenticated by a different principal under NTLM, Kerberos, or SPNEGO/Negotiate, causing the backend to execute the second request as the first identity - a full read/act-as impersonation (VC:H/VI:H). The flaw is that the connection-pool partition key omits the authenticated principal for connection-oriented authentication schemes, while Basic and Digest, which authenticate every request, are not affected. Exploitation requires an authenticated user (PR:L) on a deployment that shares one client/pool across multiple identities, and it is timing-dependent (AC:H, AT:P) because a suitably authenticated pooled socket must exist and be handed to the mismatched request; no public exploit code was identified at time of analysis and there is no KEV entry, though EPSS data was not provided. The vendor-released patch is AsyncHttpClient 3.0.13 (3.x line) or 2.16.1 (2.x line).
Authenticated information disclosure in Splunk Enterprise allows a low-privileged account to bypass an intended security control and access data it should not be able to reach, affecting versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15. Rated CVSS 7.6 (AV:N/AC:L/PR:L/UI:N, with high confidentiality impact but only low integrity and availability impact), the issue is classified as CWE-693, Protection Mechanism Failure, and requires only a valid Splunk account with network reachability to the instance - no user interaction is needed, but a fully unauthenticated outsider cannot exploit it. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the vendor has released fixed builds for all four affected release trains for this internally discovered flaw.
Blind SQL injection in the WP Post Author WordPress plugin through version 4.0.0 allows an authenticated high-privilege (administrator-level) attacker to read sensitive data from the underlying WordPress database, with assessed high confidentiality impact, limited integrity impact, and no availability impact. Exploitation requires a high-privilege account (CVSS PR:H) and no victim user interaction, so direct external exploitation against a default install is limited, though risk increases in multi-author or delegated-admin environments or if an admin account is already compromised. Multiple signals point to a moderate, not critical, real-world priority; no public exploit identified at time of analysis and no CISA KEV confirmation of active exploitation.
Blind SQL injection in the Slider by 10Web WordPress plugin through version 1.2.63 allows an authenticated high-privilege user (CVSS PR:H, typically administrator-level) with network access to the vulnerable request handler to inferentially extract database contents, with confidentiality-only impact per the independent assessment. The input CVSS 3.1 vector describes a network-reachable, low-complexity flaw, but the high-privilege requirement is a critical mitigating factor because anonymous or unprivileged users cannot reach the vulnerable code path. No public exploit identified at time of analysis, and no CISA KEV entry or EPSS data was provided; patch availability is not confirmed from the supplied data.
Blind SQL injection in the Gopiplus 'Post title marquee scroll' WordPress plugin (all versions through 9.9) allows an authenticated user with administrator-level privileges to inject arbitrary SQL into backend database queries and infer data through boolean- or time-based responses. The highest realistic impact is full disclosure of data stored in the WordPress database (CVSS:C:H), with the attacker population sharply constrained by the PR:H prerequisite - anonymous visitors and ordinary subscribers cannot reach the vulnerable functionality. As of analysis there is no CISA KEV listing and no public exploit code identified, and because the injection is blind, successful exploitation requires iterative inference rather than direct retrieval of results; the vendor has not published a fixed version, so the plugin should be removed or disabled until an update appears.
Blind SQL injection in the WordPress/WooCommerce plugin Pix por Piggly (para WooCommerce) through version 2.1.2 allows an authenticated user holding high privileges on the site - such as a WordPress administrator or a WooCommerce shop manager - to inject arbitrary SQL into backend queries and extract database contents through inference-based techniques. The flaw is CWE-89 (improper neutralization of special elements in an SQL command), reported by Patchstack, and carries a disclosed CVSS 3.1 base score of 7.6 (AV:N/AC:L/PR:H/UI:N, with the reporter's vector claiming scope change, high confidentiality impact, no integrity impact and low availability impact); our own assessed vector narrows this to S:U/C:H/I:N/A:N, keeping the practical severity essentially the same. The high-privilege prerequisite (PR:H) is the decisive constraint: anonymous visitors and ordinary subscribers cannot reach the vulnerable path, so risk is concentrated in sites where lower-trust staff accounts exist, where shop-manager credentials are shared, or where a privileged account has already been compromised. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Blind SQL injection in the Sarah Giles 'Dynamic User Directory' WordPress plugin, affecting all versions up to and including 2.4, lets an attacker with an existing high-privilege account on the target WordPress site inject arbitrary SQL into a plugin query and exfiltrate database contents by observing boolean or timing differences in responses, since the query results are not returned directly. The flaw is remotely reachable with low attack complexity and no user interaction, but the CVSS:3.1/AV:N/AC:L/PR:H/UI:N vector means it is only exploitable by an authenticated, high-privilege user - a significant limiting factor that narrows the realistic attacker set to trusted administrators or attackers who have already compromised a privileged account. Our independent assessment scores the issue 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N), lower than the 7.6 reported by the finder, because scope is unchanged and integrity and availability impact are limited; there is no CISA KEV listing and no public exploit identified at time of analysis, although a Patchstack advisory documents the issue.
Blind SQL injection in the WordPress plugin affiliate-toolkit (a.k.a. affiliate-toolkit-starter) through version 3.9.1 lets an attacker with an authenticated, high-privilege (administrator-level) account inject arbitrary SQL into plugin queries and exfiltrate database contents through inference-based techniques. The attack is remote, low complexity, and requires no victim interaction once that privileged session exists, but the administrator-level prerequisite (PR:H) sharply limits the realistic attacker pool, and because the injection is blind, exploitation is slower and noisier than a direct-output SQLi. Per our independent assessment this is a moderate-priority issue rather than an emergency; no public exploit identified at time of analysis, and no CISA KEV listing applies.
Unbounded WebSocket permessage-deflate decompression in the AsyncHttpClient (AHC) Java library versions 2.2.0 through 3.0.13 allows a malicious or compromised WebSocket peer to exhaust the JVM heap of the connecting application by sending a small compressed message that inflates into a very large Netty buffer. The flaw is remote, requires no authentication or user interaction from the peer side (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), but it only triggers when the client application itself opens an outbound WebSocket connection with permessage-deflate compression negotiated - meaning the victim must connect to an attacker-controlled endpoint or be exposed to a man-in-the-middle. Impact is availability-only: no confidentiality or integrity loss, and no public exploit code has been identified at time of analysis. The issue is fixed in version 3.0.14.
Deserialization of untrusted cache data in IBM Langflow OSS 1.0.0 through 1.12.2 can execute attacker-controlled code with the privileges of the Langflow service process, but only for an attacker who has already obtained two things: the Langflow server secret and write access to the backing Redis instance used as the application cache. Because both prerequisites are effectively gated - the server secret is a trusted signing/trust value and Redis is normally bound to localhost or a private, authenticated network - this is not exploitable by an anonymous remote attacker against a default deployment, which is why the practical risk is lower than the 7.5 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
ImageMagick builds prior to 7.1.2-31 and 6.9.13-56 contain an invalid memory free in the MVG (Magick Vector Graphics) decoder that aborts or crashes the process when a crafted image is parsed. Attackers reach it by supplying an image carrying malicious MVG drawing primitives to any application that renders, converts, or thumbnails untrusted images; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H scores 7.5 with availability-only impact and no confidentiality or integrity loss. No public exploit identified at time of analysis, CISA SSVC records Exploitation 'none' and Automatable 'no', and EPSS sits at 0.40% (32nd percentile), so the flaw is primarily a realistic denial-of-service risk for image-processing pipelines rather than an imminent attack vector.
A crafted PSD file can drive the ImageMagick PSD decoder into an infinite loop, consuming CPU indefinitely and denying service to any application that processes untrusted images. The flaw is an unvalidated image-resource-block offset in ParseImageResourceBlocks (CWE-196 integer conversion, escalating to CWE-835 infinite loop) that only manifests on 32-bit builds: ImageMagick 7.x before 7.1.2-32 and 6.x before 6.9.13-57, while 64-bit builds are not affected. Exploitation requires no authentication or user interaction wherever PSD parsing is exposed (upload, conversion, or thumbnail pipelines), but SSVC records Exploitation: none and Automatable: no, no public exploit is identified at time of analysis, and EPSS is modest at 0.40% (32nd percentile); availability-only impact drives the 7.5 CVSS score.
Denial of service in ImageMagick's bzip2 decompression path lets a crafted bzip2-compressed image stream drive the reader into an infinite loop, consuming CPU indefinitely on the affected process. Versions prior to 7.1.2-32 in the 7.x line (from 7.0.0) and prior to 6.9.13-57 in the 6.x line are affected; the flaw is reachable by remote, unauthenticated attackers who can get an image decoded (upload, conversion, or thumbnail service) with no user interaction beyond supplying the file, and there is no confidentiality, integrity, or code-execution impact. No public exploit code has been identified at time of analysis and CISA SSVC records no known exploitation; EPSS is 0.40% (32nd percentile), so the practical risk is concentrated in deployments that decode untrusted images without per-request CPU or wall-clock limits.
CPU and time exhaustion in ImageMagick can be triggered by a crafted MVG image because the MVG decoder in versions prior to 7.1.2-31 (7.x) and 6.9.13-56 (6.x) lacks a limit on macro expansion during drawing. The result is an availability-only denial of service (CWE-400) with no confidentiality or integrity impact; the assessed vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. No public exploit was identified at time of analysis, SSVC exploitation is none, and EPSS is 0.38% (30th percentile); vendor fixes are available in 7.1.2-31 and 6.9.13-56.
Denial of service in ImageMagick versions prior to 7.1.2-31 allows unauthenticated remote attackers to exhaust CPU resources by supplying an image whose embedded XMP profile contains a crafted rational value, causing the parser to perform excessive work. Impact is availability-only, with no code execution or data exposure, and exploitation requires an application to process untrusted images with XMP metadata. No public exploit was identified at time of analysis, CISA KEV does not list this issue, and EPSS is low at 0.37% (29th percentile); the vendor-released fix is version 7.1.2-31.
Denial of service in the Excelize Go library (versions 2.3.1 through 2.11.0) allows unauthenticated remote attackers to pin a CPU core by supplying a crafted agile-encrypted .xlsx workbook whose OLE encryption header declares an excessively large spinCount, which the library feeds unbounded into its password-key derivation loop. Opening such a file with decryption attempted (OpenFile with a password) makes agileDecrypt run attacker-selected iterations before any verifier validation, and the work cannot be cancelled. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but the impact per malicious file is bounded to one CPU core rather than a full host outage. An upstream fix exists in PR #2389 / commit 2badfcd, but no tagged patched release is confirmed.
Denial of service in the Excelize Go spreadsheet library (github.com/xuri/excelize/v2 2.0.0-2.11.0 and github.com/xuri/excelize 1.1.0-1.4.1) lets an unauthenticated remote attacker terminate the calling process by supplying a crafted workbook. The ColumnNameToNumber function converts bijective base-26 column names into int64 without overflow detection, so an over-long name such as VGWQHXLSDVIKWV wraps to zero and is later used as a slice index by checkSheetR0 and xlsxWorksheet.checkRow, producing a negative index panic during worksheet normalization. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), meaning availability-only impact; there is no evidence of confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, though the upstream fix commit and PR are public. This is a moderate-severity denial-of-service condition rather than a high-priority emergency, and it is only reachable when an application built on the vulnerable versions parses an untrusted spreadsheet.
Denial of service in ImageMagick's RSVG delegate reachable through crafted SVG images: when ImageMagick is compiled without Cairo support, a malicious RSVG file that hits an internal resource limit causes the decoder to free image state twice and then touch freed memory, terminating the process. Affected builds are ImageMagick 7.x before 7.1.2-30 and 6.x before 6.9.13-55; the non-Cairo configuration is not the default for most mainstream distributions, and impact is limited to availability (no confidentiality or integrity effect). No public exploit code was identified at time of analysis and the issue is not in CISA KEV; EPSS is low at 0.32% (22nd percentile), and SSVC rates exploitation as none and automatable as no, so real-world priority is LOW despite the 7.5 CVSS base score.
Uncontrolled recursion in the Excelize Go library (versions 2.8.1 through 2.11.0) allows a fatal Go stack overflow that aborts the host process when mutually referencing dynamic-array formulas using _xlfn.ANCHORARRAY are evaluated, resulting in a pure availability impact (CVSS:3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Reachability depends entirely on the host application: it is exploitable only when an application feeds attacker-controlled spreadsheet content into CalcCellValue or another formula-evaluating API, while applications that merely read raw cell values are unaffected. No public exploit code has been identified at time of analysis, and although an upstream fix commit exists, no released patched version has been confirmed (the advisory states no fixed version is available as of its review).
Denial of service in Excelize versions 2.3.1 through 2.11.0 allows unauthenticated remote attackers to terminate the calling Go process by supplying a malformed OLE compound file with a version-valid EncryptionInfo stream to the library's Decrypt function. The decryption dispatch lacks structural and parameter validation, causing nine malformed-input classes to trigger unrecovered Go runtime panics instead of returning documented errors. Exploitation requires the host application to process attacker-supplied encrypted spreadsheets, no fixed version is available as of this review, and no public exploit code has been identified.
A bundled Cisco software-hardening release resolves multiple internally discovered resource-lifecycle flaws (CWE-664) affecting Cisco Meraki MX security appliances, MR wireless access points, MV camera firmware, and Cisco Campus Gateway Software. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), the impact is availability-only - an unauthenticated remote attacker who can reach the affected service can trigger resource mismanagement that crashes or degrades the device, with no confidentiality or integrity loss. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Cisco has not published a specific patched firmware version in the CVE metadata, so administrators should consult the linked advisory to map the hardening release to their exact hardware and firmware train.
Cyrus SASL clients that use the DIGEST-MD5 authentication mechanism can be crashed by a malicious or on-path server that supplies a crafted challenge field (such as realm or nonce), because the add_to_challenge() function computes a buffer size before DIGEST-MD5 quoting and fails to account for escaping that lengthens the value, resulting in a heap-based out-of-bounds write. This is a client-side denial-of-service flaw affecting Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H, meaning unauthenticated remote attackers must control or intercept the server endpoint and the victim must initiate authentication. No public exploit code or confirmed active exploitation is identified at time of analysis.
Memory exhaustion and runtime panic in the Excelize Go library (versions 2.3.1 through 2.11.0) let unauthenticated remote attackers crash or drive out-of-memory conditions in any service that decrypts attacker-supplied, password-protected OLE compound (CFB) Excel workbooks. The assessed CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) confirms no privileges or user interaction are needed and that impact is confined to availability, with no code execution or data exposure. No vendor-tagged fixed release was available as of this review, though an upstream fix exists as PR #2396 / commit 5f636f9; no public exploit code was identified at time of analysis and there is no KEV listing.
Cleartext credential disclosure in AsyncHttpClient (AHC) before 3.0.12 on the 3.x line and before 2.16.1 on the 2.x line causes a client configured to use an HTTP proxy to write the origin request and its Authorization credentials onto a still-plaintext proxy connection when the proxy rejects the CONNECT with anything other than 200, because the client infers an established tunnel from the last request method rather than the CONNECT result. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5 HIGH), this is an unauthenticated, confidentiality-only issue: Basic credentials can be recovered directly, while NTLM responses may be cracked or relayed. Exploitation is limited to environments where the victim application routes through an HTTP proxy and the attacker controls or can man-in-the-middle the client-to-proxy hop; no public exploit identified at time of analysis.
Missing authorization in the WPMU DEV Forminator WordPress plugin (all versions through 1.57.2) allows unauthenticated remote attackers to perform privileged actions that should require an access-control check, altering site data with a high integrity impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N). Because the vector carries PR:N and UI:N, exploitation requires only that a vulnerable Forminator installation be network-reachable; no credentials or victim interaction are needed, though the impact is confined to integrity with no confidentiality or availability loss. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (not in CISA KEV), making this a moderate-priority, broadly-reachable issue rather than an emergency.