Denial of service in IBM DataPower Gateway 11.0.0.0 through 11.0.0.2 allows an attacker who already holds a valid low-privileged account to trigger improper memory allocation during key derivation, corrupting memory and rendering the gateway unavailable (CVSS 7.7, AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H). Because the vector requires PR:L, the flaw is not exploitable pre-authentication, and its scope-changed rating reflects that the availability impact can extend past the initially compromised security boundary; there is no confidentiality or integrity impact. Patch available per vendor advisory and no public exploit identified at time of analysis, so risk is concentrated in unpatched appliances where an attacker can obtain even limited authenticated access.
Path traversal in Brocade Active Support Connectivity Gateway (ASCG) before 3.5.0 lets an unauthenticated attacker write arbitrary files to restricted host locations by embedding traversal sequences in entries of a support-bundle archive that ASCG ingests from remote endpoints, with the potential for follow-on remote code execution if a written path is later executed or loaded. The attack is not internet-facing: exploitation is scored AV:A (adjacent network) with the CVSS 4.0 AT:P precondition, meaning the attacker must already control or be able to man-in-the-middle support bundles originating from a compromised or spoofed ingesting endpoint. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so the practical risk is a moderate, conditional one that depends on an attacker holding a management-network position and a compromised ingestion source rather than an urgent, broadly exploitable issue.
Red Hat OpenShift Container Platform 4 ships by default with an insights-operator-gather ClusterRole that grants the operator's 'gather' service account cluster-wide get/list access to core-group secrets, with no namespace or resourceNames scoping. An authenticated actor who can create or influence a pod specification in any namespace - and set 'serviceAccountName: gather' on it - can mount that service account and read every secret in every namespace, making this a privilege-escalation and cluster-wide credential-disclosure primitive (CWE-269, CVSS 7.7, scope-changed confidentiality-only). Exploitation requires a pre-existing foothold with pod-create or service-account-binding rights (PR:L), so it is not remotely exploitable by an unauthenticated user; no public exploit code has been identified at time of analysis, and the over-broad grant exists out of the box rather than behind a non-default feature flag.
Authentication bypass in Brocade Fabric OS versions before 9.2.2d running on the MXG610 extension switch lets a network-adjacent attacker reach an unprotected endpoint in the web management interface's Single Sign-On workflow and obtain administrative access to the device. No credentials or user interaction are required (PR:N/UI:N), although High attack complexity (AC:H) means conditions outside the attacker's control must line up for reliable exploitation, and exposure is confined to MXG610 deployments with a reachable management interface. No public exploit code has been identified at the time of analysis, and there is no confirmation of active exploitation.
Local privilege escalation in IBM Guardium Data Protection 12.2 lets an already-authenticated, high-privileged user gain root-level command execution by feeding attacker-controlled arguments to the SUID-root ssh_config_wrapper component. Because the component runs with effective UID 0, successful argument injection converts a privileged-but-limited foothold into full root control of the appliance, with high impact to confidentiality, integrity, and availability. This is a moderate-severity escalation issue rather than a remote-takeover emergency: the attacker must already hold a high-privileged account and be able to invoke the vulnerable binary locally, and no public exploit code has been identified at time of analysis. A vendor patch is available, though the specific fixed build is not enumerated in the supplied data.
Cross-site request forgery in Pydantic AI's development web chat UI allows any website a developer happens to visit while `Agent.to_web()` or `clai web` is running to fire forged chat requests at the loopback-hosted server, causing the served agent to start a run and execute its tools with the privileges and credentials of the local process. The pre-patch `/api/chat` endpoint performed no Content-Type validation, so a malicious page can deliver a JSON body cross-origin using a CORS-safelisted content type (text/plain, multipart/form-data, application/x-www-form-urlencoded, or none at all) without triggering a preflight; binding the server to localhost - the default - provides no protection because a browser page can reach 127.0.0.1. Realized damage is bounded by the tools the agent exposes, and `requires_approval=True` does not help because the endpoint trusts approval decisions relayed by the client; exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L, 7.6) but requires the developer to browse an attacker-controlled page while the dev UI is running, and there is no public exploit code identified at time of analysis. Vendor-released patches are available in 1.107.4 and 2.28.0.
Unauthenticated attackers with adjacent-network reachability can push an unauthorized Certificate Authority certificate into the TLS client trust store of Brocade ASCG (all versions before 3.5.0), because the product's management interface accepts CA certificates without authentication. A successful injection lets an on-path adversary Man-in-the-Middle the outbound TLS connections ASCG establishes to the managed Fibre Channel switches and peer nodes it administers, producing high confidentiality and integrity impact (CVSS 7.6; CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N; independent CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). Because the vector is PR:N the certificate submission is unauthenticated, but exploitation still requires the attacker to be logically adjacent to the management plane (AV:A) and, for the MITM payoff, to hold an on-path position between ASCG and its outbound peers (AT:P) - no public exploit code and no CISA KEV entry were identified at time of analysis, so this is a genuine but moderate-priority issue rather than an urgent emergency.
Stored cross-site scripting can occur in applications generated by JHipster before generator-jhipster 9.4.0 and react-jhipster 1.1.0 when an authenticated user stores attacker-controlled Blob content and a companion ContentType in a Blob-bearing entity and a privileged user later opens it through the generated UI. The assessed CVSS is 7.6 with vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N, reflecting authenticated write access, required victim interaction, and conditional exploitability that depends on the generated application's CSP and target-browser Blob handling. No public exploit identified at time of analysis; vendor-released patches are generator-jhipster 9.4.0 and react-jhipster 1.1.0.
Two-factor authentication bypass in pH7Builder (pH7 Social Dating CMS) before 18.5.0 lets attackers who already know a valid account password brute-force the 6-digit TOTP code submitted to VerificationCodeFormProcess.php without any attempt throttling, ultimately taking over member, affiliate, or administrator accounts. Exploitation is second-order: it requires prior credential compromise (PR:L) plus 2FA enabled on the target account, and success depends on racing the OTP rotation window (AT:P), but when those conditions hold nothing stops unlimited guesses. No public exploit code or confirmed active exploitation has been identified at time of analysis; the vendor has shipped a fix in version 18.5.0 that reuses the existing per-IP login-attempt lockout.
Blind SQL injection in the Appsbd Vitepos / vitepos-lite WordPress plugin, affecting versions through 3.6.1, allows an attacker who already holds a high-privilege account on the WordPress site to inject SQL through an improperly neutralized plugin input and extract database contents one inference at a time. The primary barrier is the authentication prerequisite (CVSS PR:H) - exploitation is remote over the network with low complexity and no user interaction, but anonymous internet attackers are excluded, and the attacker must first compromise or legitimately hold an administrative-level session. Patchstack reported the issue with a CVSS 3.1 score of 7.6; the independent assessment narrows the realized impact to loss of confidentiality (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Concurrency slot exhaustion in Pydantic AI 2.10.0 through 2.52.x lets streamed model requests permanently occupy slots in a shared ConcurrencyLimiter, progressively starving later requests until a service that reuses one long-lived limiter can no longer make model calls - an availability-only denial of service (C:N/I:N/A:H) with no confidentiality or integrity impact. The issue is remotely reachable and unauthenticated (PR:N), but our independent assessment rates it AC:H rather than GitHub's AC:L because exploitation requires a specific deployment pattern: model requests wrapped in ConcurrencyLimitedModel (or covered by limit_model_concurrency) that share a single long-lived limiter across streamed responses; agent-level max_concurrency and all non-streaming model requests are explicitly unaffected, and a short-lived or per-request limiter never accumulates enough leaked slots to deadlock. Slots are leaked by early stream termination, cancellation, consumer exceptions, or even full stream_text() consumption with debounce_by=0.1, and the vendor-released fix in 2.53.0 is available; no public exploit code identified at time of analysis.
Stack-exhaustion denial of service in msgpack5, the MessagePack v5 implementation for Node.js and browsers, affects all versions prior to 6.1.0. When an application uses msgpack5's streaming decoder and feeds it a single chunk containing many small, individually valid MessagePack values, the decoder recursively re-invokes itself once per remaining value, so recursion depth grows with the value count and eventually overflows the JavaScript call stack - crashing or stalling the process or stream. The flaw is remotely reachable without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), though it is confined to services that expose the streaming decoder to untrusted input; the fix is the vendor-released version 6.1.0, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Decoding a truncated map32 MessagePack value in msgpack5 (npm) before 6.1.0 causes the decoder to read the four-byte length field of a five-byte header that has not fully arrived, producing an out-of-bounds buffer read that throws RangeError instead of IncompleteBufferError; the unauthenticated network-vector flaw (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) can abort a request, stream, or worker in applications that use IncompleteBufferError to decide whether to wait for more bytes. Impact is denial of service only - the underlying buffer implementation bounds-checks the read, so there is no adjacent-memory disclosure and no path to code execution. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fixed version (6.1.0).
A heap buffer overflow in IBM DataPower Gateway (affected firmware levels 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows remote attackers to crash the service and cause a denial of service; the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, privileges, or user interaction are required, so any reachable affected gateway is a candidate target. Impact is confined to availability - the vendor reports no confidentiality or integrity loss and no code execution. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); this is a genuine availability risk but not a top-tier emergency, with practical exposure limited by how broadly the gateway's data-plane and management interfaces are reachable.
Malformed GeoJSON Polygon or MultiPolygon values cause MariaDB Connector/Node.js - every release before 3.2.5, 3.3.4, 3.4.7 and 3.5.4 - to write uninitialized Node.js heap memory into database values. When a calling application passes a non-array 'ring' (an object exposing a numeric length, a string, or a number) through the binary-protocol execute() or batch() APIs, the encoder sizes a Buffer.allocUnsafe() allocation from that ring's length but the writing loop skips the reserved bytes, so the entire buffer is sent and persisted in the database, potentially carrying other users' content, session material, database credentials or TLS key material that can then spread to backups and replicas. The published CVSS 3.1 vector (7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) treats this as a trivially reachable unauthenticated disclosure, but independent review rates attack complexity High because exploitation additionally requires the attacker to influence the geometry value the application passes to the connector, the application to actually use binary-protocol prepared statements or batches with geometry rather than the unaffected text-protocol query() path, and the ability to read the persisted value back; no public exploit code has been identified at time of analysis and there is no CISA KEV entry.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or degrade an affected gateway by sending crafted input that the product fails to validate correctly, resulting in an out-of-bounds write in memory. All four supported release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms the attack is launched over the network with no authentication and no user interaction, and that the sole impact is availability - there is no confidentiality or integrity loss, so the risk is bounded to service outage on gateways whose vulnerable interface is reachable from untrusted networks. No public exploit code has been identified at time of analysis, no EPSS score was supplied, and CISA KEV does not list this CVE.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or exhaust the message-processing service by sending crafted messages whose length field is mishandled during memory reallocation. All firmware levels in the ranges 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 are affected; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) indicates no authentication, user interaction, or non-default configuration is needed, and the only impact is loss of availability. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but because exploitation only requires network reachability to the gateway's message interface, internet- or partner-facing appliances should be treated as the highest-priority remediation targets.
Unauthenticated remote attackers can exhaust system resources on IBM DataPower Gateway firmware releases 11.0.0.0 through 11.0.0.2, degrading or halting availability of the gateway's traffic and management services. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials, user interaction, or special positioning are required once the affected interface is reachable, but impact is confined to availability - there is no data disclosure, tampering, or code execution component. No public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV); the practical risk is therefore a bounded denial-of-service exposure that is highest where DataPower interfaces are internet-facing or unsegmented, and much lower where they sit behind network controls and rate limiting.
Authentication bypass in IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, allows a remote, unauthenticated attacker to defeat security restrictions and gain unauthorized access to functionality that should be protected. With a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N, C:N/I:H/A:N), the flaw is network-reachable, low complexity, and requires no credentials or user interaction; the impact is rated as high on integrity, meaning an attacker can alter protected data or configuration through the bypass. The only practical precondition is that the affected authentication or management interface be reachable by the attacker. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV); a vendor patch is available per IBM advisory node 7291628.
Authentication bypass in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the container editions) allows a remote, unauthenticated attacker to defeat the product's authentication control entirely, with no user interaction required. The 7.5 CVSS score reflects a high integrity impact only - the vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) assigns no confidentiality or availability impact - so the practical effect is that an attacker can perform authenticated actions with the privileges of a legitimate session while exposing no data directly. IBM has published a vendor fix via support node 7291628, and no public exploit code has been identified at time of analysis; this is a credible operational priority but not a confirmed emergency.
Path traversal (CWE-22) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote, unauthenticated attacker to write arbitrary files on the affected appliance or container by supplying crafted path components. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5) exploitation is network-reachable, low-complexity and unauthenticated, with high integrity impact and no confirmed confidentiality or availability impact - a file-write primitive rather than a file-read or denial-of-service bug. No public exploit identified at time of analysis and the CVE is not listed in CISA KEV; the vendor has released a patch and the sole reference is IBM's advisory at https://www.ibm.com/support/pages/node/7291628. Exposure is bounded by network reachability: instances sitting behind reverse proxies or confined to internal/DMZ segments that attackers cannot reach are not directly exploitable.
Unauthenticated path traversal in IBM Guardium Data Protection 12.2 allows a remote attacker who can reach the GIM (Guardium Installation Manager) file-upload interface to escape the intended upload directory and write arbitrary files onto a Collector host. The assessed vector (AV:N/AC:L/PR:N/UI:N, integrity impact) confirms that no credentials or user interaction are required against that endpoint, so any 12.2 Collector whose GIM upload service is reachable is exposed until patched; the practical attack surface is driven almost entirely by network segmentation of GIM. No public exploit code has been identified at time of analysis, and exploitation has not been confirmed as active - impact is file-system write access on the Collector, scoring CVSS 7.5.
Denial of service in IBM DataPower Gateway affects releases 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, where crafted network input reaching the vulnerable parsing path overflows a buffer and can crash the affected service. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), exploitation requires no authentication and no user interaction, so any internet- or partner-facing listener that processes malformed input is exposed; impact is availability-only - a crash/restart condition rather than data exposure or code execution. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV), so this is a genuine but bounded operational risk that depends primarily on whether affected listeners are reachable from untrusted networks.
Denial of service in IBM Guardium Data Protection 12.2.2 allows an unauthenticated remote attacker with network reachability to the edge-controller gRPC service to terminate the edge-controller process by supplying malformed task data that trips an unchecked type assertion. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms no authentication, no user interaction, and no special timing are required once the port is exposed, and impact is confined to availability - the process crashes unexpectedly with no data disclosure or modification. There is no public exploit identified at time of analysis and no confirmed active exploitation (the CVE is not in CISA KEV), so the practical exposure is governed by reachability: deployments that keep the edge-controller gRPC endpoint on isolated management networks are not exposed to arbitrary remote attackers, while internet- or broad-LAN-accessible instances are at meaningful disruption risk. The primary limiting factor is that the gRPC port must be reachable, making this a genuine but bounded-impact availability issue.
IBM DataPower Gateway can be driven into a denial-of-service condition by a remote, unauthenticated attacker who supplies input that reaches a flawed sorting comparator, causing the comparator to violate strict-weak-ordering and triggering an out-of-bounds memory access (CWE-787) that can crash or destabilize the affected service. All builds in the 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2 ranges are affected; the impact is confined to availability (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity effect and no privilege gain. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, and IBM has published a fix via its support advisory, so this should be treated as a patching-priority availability risk rather than an emergency.
Unauthenticated remote attackers can drive IBM DataPower Gateway into resource exhaustion and denial of service by sending crafted GraphQL queries that abuse improper memoization of fragment spreads. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, and per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H vector no authentication or user interaction is required once a reachable GraphQL-processing endpoint exists. Impact is confined to availability (no confidentiality or integrity loss), and there is no public exploit identified at time of analysis; exposure depends entirely on whether the gateway has been configured to accept and process GraphQL requests.
Denial of service in IBM DataPower Gateway lets unauthenticated remote attackers send crafted network traffic that triggers an out-of-bounds write (CWE-787), degrading or halting the gateway's availability. The flaw affects version lines 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, scoring CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with availability-only impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but IBM has published a vendor fix, so internet-facing gateways should be treated as the highest-priority upgrade target.
A heap buffer underwrite in IBM DataPower Gateway allows unauthenticated remote attackers to crash the gateway service, producing a denial-of-service condition on affected appliances. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), the flaw is reachable over the network with no privileges or user interaction required, and impact is confined to availability (C:N/I:N/A:H). Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
IBM DataPower Gateway is vulnerable to a remote, unauthenticated denial of service (CVSS 3.1 base 7.5) in which a crafted request triggers an out-of-bounds read, degrading or crashing the affected gateway service. All supported firmware streams in the affected ranges are exposed: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6 (the 10.6 CD stream), and 11.0.0.0 through 11.0.0.2. The vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms exploitable over the network with no authentication, privileges, or user interaction, but restricts impact to availability - no confidentiality or integrity loss is assessed - so exploitation results in service disruption rather than compromise; there is no public exploit identified at time of analysis, and a vendor patch is available.
Unauthenticated remote attackers can crash IBM DataPower Gateway by sending a crafted request that triggers a null pointer dereference, resulting in a denial of service that takes the affected service interface offline. All four maintained release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, user interaction, or privileged position is needed - only network reachability to a vulnerable, unpatched gateway - and the sole impact is availability (C:N/I:N/A:H), with no data exposure or code execution. No public exploit code or confirmed active exploitation was identified at time of analysis, so this is a credible but bounded availability risk that is governed primarily by how exposed the gateway's service interfaces are to untrusted networks.
IBM Guardium Data Protection 12.0, 12.1, and 12.2 ship with hard-coded credentials that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can abuse to read sensitive information from the affected appliance service, yielding a high confidentiality impact with no integrity or availability loss (C:H/I:N/A:N, base 7.5). Exploitation is not trivial in practice: the attacker must first know or recover the static credential value and must be able to reach the Guardium management or data service over the network, which is typically an internal, segmented appliance rather than an internet-facing endpoint. There is no confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and EPSS is only 0.30% (21st percentile), so this rates as a genuine but moderate-priority exposure that should be scheduled rather than emergency-patched.
A type confusion flaw (CWE-843) in IBM DataPower Gateway lets a remote, unauthenticated attacker crash a reachable gateway service, producing a denial-of-service condition. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms a network-reachable, low-complexity, unauthenticated trigger with availability-only impact. IBM has published a vendor fix via its support advisory, and no public exploit code has been identified at time of analysis (no CISA KEV listing).
PHP object injection in the WordPress plugin Uncanny Automator - AI + Automation for WordPress (all versions up to and including 7.6.1.1) lets an authenticated attacker with Subscriber-level access or above pass attacker-controlled data into an unserialize() sink via recipe trigger meta, and a POP chain present in Uncanny Automator itself escalates that into deletion of arbitrary files on the server. Exploitation is conditional rather than trivial: it additionally requires at least one supported third-party integration plugin (PeepSo, MailPoet, WPForms, and similar) to be co-installed and a recipe to be configured so that attacker-supplied input is stored as trigger meta - a combination of prerequisites that is why the assessed vector is AC:H and the plugin's real-world exposure is best characterized as a genuine but conditional risk rather than a mass-exploitation emergency. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Privilege escalation in Brocade Fabric OS (versions before 10.0.1) allows a low-privilege authenticated account to obtain root-equivalent chassis administrative access when the switch is configured to use an external AAA identity source. The switch fails to constrain crafted Vendor-Specific Attributes or directory claims returned by RADIUS, LDAP, TACACS+, or a Federated IdP against its administrative role restrictions during session establishment, so an attacker who can influence those returned attributes is granted full control. Exploitation is conditional rather than mass-scale: it requires external AAA integration to be configured (deployments using only local authentication are unaffected), a valid low-privilege account (CVSS PR:L), management-network adjacency (AV:A), and attacker influence over IdP-returned attributes (AT:P); no public exploit code was identified at time of analysis, and vendor-released patch version 10.0.1 is available.
Denial of service in the npm package music-metadata before 11.15.0: parsing a crafted .dsf (DSF) file causes an unhandled promise rejection that terminates the Node.js process, and because the rejection is detached from the parse promise the crash occurs after parseBuffer() has already resolved, so a caller's per-file try/catch catches nothing and the process still dies. Publicly available exploit code exists - a PoC targeting 11.14.0 ships in the advisory's repro/ directory and confirms the crash on Node's default unhandled-rejection behavior - but there is no evidence of active exploitation and the CVE is not in CISA KEV. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5, availability-only), EPSS is low at 0.20% (9th percentile), and CISA SSVC records Exploitation: poc with Technical Impact: partial.
Authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers forge JSON Web Signatures and present themselves as a trusted, already-verified identity on gateways that use JWS/JWT signature verification for access control. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) exploitation requires no credentials or user interaction and the impact is integrity-only, meaning the payoff is forged trust and unauthorized access rather than direct data disclosure. No public exploit identified at time of analysis, EPSS is low at 0.20% (9th percentile), and the CISA SSVC assessment records exploitation as none with automation not feasible, so this is a genuine but moderate-priority issue rather than a top-tier emergency; vendor patches are nonetheless available.
Improper authorization enforcement in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can allow unauthenticated remote attackers (PR:N, UI:N) to bypass access controls and alter protected content or state (I:H, C:N, A:N) when the product is deployed in front of certain web servers. The flaw, however, is configuration-dependent: as reflected by the AV:N/AC:H vector and IBM's scoping to 'some' web servers, only specific protected web-server integrations are exposed, and default or unaffected setups are not exploitable. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM rates the issue 5.9 (moderate); the affected deployments also include the containerized editions of both products.
Response smuggling is possible in Go's HTTP/2 implementation (net/http and golang.org/x/net/http2) when a program acts as a reverse proxy that receives an HTTP/2 upstream response and forwards it to a downstream HTTP/1 client. Because Go has historically not rejected malformed framing-related headers such as connection-specific or length-related headers that RFC 7540 requires to be treated as malformed, those headers can be relayed verbatim; if the downstream HTTP/1 client is also lenient in parsing, the attacker can desynchronize the response stream and smuggle content. The issue is unauthenticated from the network perspective (CVSS PR:N) but exploitation is constrained to that specific proxy topology and requires attacker influence over the upstream response plus a non-strict HTTP/1 client; there is no public exploit identified at time of analysis, EPSS is low at 0.19% (8th percentile), and CISA SSVC records no exploitation with partial technical impact.
Stored cross-site scripting in the GPTranslate WordPress plugin (versions below 2.34.14) lets unauthenticated attackers submit translation strings that the plugin stores without proper authorization checks and later renders without output escaping, so malicious JavaScript executes in the browser of any user who views a poisoned translated page. The flaw is only reachable when the plugin's server-side translations feature is enabled, meaning sites relying on client-side translation are not exposed, and successful abuse still depends on a victim subsequently loading the affected page (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; a vendor patch is available in version 2.34.14.
Request smuggling in the Go net/http standard library occurs when an application handler answers an HTTP/1 CONNECT request with a 2xx status and then returns without hijacking the connection, causing the server to keep parsing HTTP requests on a connection that an intermediate proxy now treats as an opaque tunnel. Affected builds are net/http before 1.26.9 and the 1.27.x line before 1.27.2 (CWE-444, parser disagreement between proxy and origin server). Exploitation requires a non-default handler pattern plus a fronting proxy, so despite the published CVSS base of 7.5 the assessed real-world priority is moderate-to-low; no public exploit code has been identified at time of analysis, EPSS is 0.18% (7th percentile), and CISA SSVC records Exploitation: none with Technical Impact: partial.
Unauthenticated remote attackers can exhaust server memory in applications built on the Go standard library by submitting crafted multipart/form-data requests, because the mime/multipart parser reads an arbitrarily long line into memory whenever the remaining memory limit at the start of a part drops below 400 bytes. Affected runtimes are Go releases prior to 1.27.2 and prior to 1.26.9, including the mime/multipart and net/textproto packages; any service that parses attacker-supplied multipart forms - for example via net/http Request.ParseMultipartForm or Request.FormFile - is reachable, while internal or non-multipart endpoints are not. This is a denial-of-service (CWE-770) issue with no confirmed active exploitation and no public exploit code identified at time of analysis; EPSS is 0.18% (7th percentile), CISA SSVC rates exploitation as none with partial technical impact, and the vendor has shipped patched releases.
Denial of service in libming through 0.4.8 occurs when a libming-based tool parses an attacker-supplied malformed SWF file through the readtag_file() code path in src/blocks/fromswf.c, causing the parsing process to crash or exhaust resources. The assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) shows this requires user interaction and carries only availability impact, so remote exploitation applies only where a network service actually feeds untrusted SWF input into libming, while a standalone CLI run needs a user or process to open the crafted file. No public exploit code was identified at time of analysis and EPSS is 0.18% (7th percentile), so despite NVD's 7.5 base score the real-world priority is low.
Remote memory exhaustion in the Go standard library's crypto/tls package lets a client that sends a crafted ClientHello containing multiple ECH outer extension references - a construction prohibited by RFC 9849 - force disproportionate memory allocation in TLS servers with Encrypted Client Hello enabled. Only Go releases before 1.27.2 and before 1.26.9 are affected, and the flaw is fixed in those two releases; no public exploit code exists and there is no CISA KEV listing at time of analysis. The practical attack surface is narrow because ECH is opt-in and not active in a default Go TLS server configuration, but where enabled the attacker needs no authentication or user interaction (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5).
CPU exhaustion in the Go standard library's net/http file-serving handlers (FileServer, ServeContent, and ServeFile(FS)) lets remote unauthenticated attackers degrade or deny service by sending a single HTTP request whose Range header enumerates a large number of small ranges. The flaw affects net/http in Go releases before 1.26.9 and 1.27.0-0 before 1.27.2, but only on servers that actually expose those file-serving handlers; default configurations that use them are affected with no authentication or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Impact is availability-only, exploitation is not confirmed and no public exploit has been identified at time of analysis, EPSS is low at 0.17% (6th percentile), and patched releases are available from the vendor.
HTTP/1 connection desynchronization in Go's net/http Transport allows response poisoning for other users of a shared, pooled connection pool. When an outbound HTTP/1 CONNECT request carries a non-empty Request.Body, Transport writes those bytes to the wire unframed after the request headers; if the upstream server rejects the CONNECT with a non-2xx but connection-reusing (keep-alive) response, Transport returns the still-contaminated socket to the idle pool, and the backend may parse the trailing bytes as a pipelined follow-up request. The primary exposure is reverse proxies (including httputil.ReverseProxy) that forward CONNECT through a shared Transport, where the next caller to reuse the desynchronized connection reads the response to the injected request - an unauthenticated remote scenario per the CVSS vector (PR:N), though exploitation requires a specific chain rather than a default single request. No public exploit identified at time of analysis; EPSS is low at 0.17% (5th percentile).
Information disclosure in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the Security Verify Access Container and Verify Identity Access Container editions) allows unauthenticated remote attackers to read sensitive data from a network-reachable instance, per the CVSS vector AV:N/AC:L/PR:N/UI:N with confidentiality impact rated High and no integrity or availability effect. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, with the attack classified as not automatable and only partial technical impact, indicating targeted rather than mass-scannable abuse. Vendor-released fixes are available from IBM, so exposure is primarily a function of how reachable the identity appliance or container endpoints are from untrusted networks.
Denial of service in music-metadata versions prior to 11.16.0 lets remote attackers crash or exhaust memory in any application that parses an attacker-supplied MP4-family file. The MP4 atom parser trusts an attacker-controlled 64-bit extended atom size, converts it to a JavaScript Number, and passes the oversized length into atom-specific readToken payload parsing (mvhd, stsd, stsz, or date) before confirming the atom fits within its parent or the remaining input, so a tiny crafted file can force a large allocation attempt or process failure. The flaw is remotely triggerable without authentication and without user interaction beyond the file being processed (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5); publicly available exploit code exists, but there is no evidence of active exploitation, no KEV listing, and EPSS is low at 0.13% (2nd percentile), with impact confined to availability.
Unbounded synchronous looping in the unreleased music-metadata master-branch MP4 'stsd' sample-description parser lets a crafted 48-byte MP4-family file pin the Node.js event loop at ~100% CPU while an in-memory sample-description table grows until the process is killed externally or exhausts memory. The regression was introduced after 11.14.0 by commit d2a7d6f (PR #2693, which changed the cursor advance to 'off += size - 4' without guarding for small sizes) and exists only on the public master branch - no published npm release, including 11.14.0 and earlier, contains the vulnerable change, and 11.16.0 ships the fix. Exploitation requires an application that parses attacker-supplied MP4-family input through parseBuffer, parseFile, parseStream, parseBlob, or parseWebStream; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (no authentication, no user interaction, availability-only impact), no public exploit targeting released versions was identified at time of analysis, and the practical limiting factor for defenders is install method (git/master build versus npm release) rather than configuration.
Unauthenticated remote attackers can render IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, unavailable by driving the software into uncontrolled recursion - a stack-exhausting condition with availability-only impact (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H). Because the vector specifies PR:N/UI:N, no credentials, user interaction, or special configuration are prerequisites, so any network-reachable, unpatched instance is a candidate and exposure management is the primary limiting factor; attacks against non-internet-facing deployments placed behind rate-limiting proxies are substantially harder to sustain. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no with partial technical impact, so this should be treated as a high-availability-risk but not currently exploited issue.
Authentication bypass in Jacamar CI before v0.30.0 allows authenticated CI users to generate arbitrary account names and impersonate other service accounts. The flaw (CWE-290) requires valid low-privilege CI credentials and a runner configured for service-account provisioning; no public exploit has been identified at time of analysis, and signals are mixed, pointing to a moderate rather than urgent priority. A vendor fix is available in v0.30.0.