Cross-site request forgery in ConvertX versions prior to 0.18.0 lets an attacker permanently delete an authenticated user's conversion jobs by luring that user into loading attacker-controlled content that silently requests /delete/{id} over HTTP GET. Because the deletion route performs a state-changing action without a CSRF token and job identifiers are simple sequential integers, an <img> or <iframe> src pointing at a guessed id is enough to trigger deletion with the victim's session cookie attached, with no click required. Exploitation requires an active victim session and the victim viewing attacker-controlled content; impact is confined to the victim's own job history (the provider scores this 8.1 with I:H/A:H, while our assessment rates the impact as limited, I:L/A:L), no public exploit code has been identified, and CISA KEV does not list this issue. The flaw is fixed in version 0.18.0, which converts the endpoint to POST and switches the UI to form-based submission.
Nginx UI versions prior to 2.4.1 let an authenticated, OTP-enabled user holding only an ordinary JWT - without the X-Secure-Session-ID step-up header - create or modify Nginx configuration and trigger reload behavior by calling the nginx_config_add and nginx_config_modify tools through the /mcp and /mcp_message endpoints, which were protected by ordinary authentication alone. The equivalent HTTP configuration mutation routes correctly enforced the RequireSecureSession middleware, so the MCP channel constituted an alternate path around that control (CWE-288). Per the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, impact is limited to integrity and availability with high severity driven by unconstrained config writes; exploitation requires an existing low-privilege authenticated session on a pre-2.4.1 instance, and no public exploit code or confirmed active exploitation was identified at time of analysis. The issue is fixed in version 2.4.1, and the upstream commit additionally hardened backup-related routes with RequireSecureSession.
Cross-site request forgery in the Patreon WordPress plugin (slug patreon-connect) through version 1.9.17 allows an attacker to craft a request that a logged-in WordPress administrator may submit without intent, because the affected functionality lacks anti-CSRF nonce validation. The independent assessment rates this as integrity-only impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N), lower than the 8.1 score reported elsewhere, and notes that the signals are thin and partly conflicting; exploitation requires a logged-in privileged user (typically an administrator) to visit attacker-controlled content or click a crafted link. No public exploit code and no CISA KEV entry were identified at time of analysis, and the attacker gains only the privileges of the victimized session.
Memory corruption through a use-after-free (CWE-416) in the JavaScript engine integration of Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 can lead to controlled process failure, server instability, or corrupted memory state. Exploitation is not anonymous: the assessed vector (AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H) requires a high-privileged account that can already execute server-side JavaScript, and the high attack complexity indicates the defect depends on specific timing or state conditions that are not reliably achievable on demand - so realistic abuse is confined to trusted, insider, or post-compromise contexts. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released fixed versions 12.1.0 (12.x track) and 11.3.7 (11.x track).
OS command injection in the Ministry of Justice General Directorate of Information Technology's UYAP Document Editor before version 5.4.20 allows an attacker to execute arbitrary operating-system commands on a victim's machine when a crafted document is opened in the application. The issue is local in nature (AV:L) and requires user interaction (UI:R) - the victim must open a malicious file - but no authentication or privileges are needed (PR:N), and successful exploitation yields high confidentiality, integrity, and availability impact, giving a base score of 7.8 (HIGH) on the CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The flaw was reported by TR-CERT; no public exploit code has been identified and the issue is not listed in CISA KEV, so the practical risk is driven by phishing-style delivery of weaponized-looking documents rather than by remote scanning or automated mass exploitation.
Use-after-free in the Linux kernel sched/cache LLC grouping code can let a local attacker crash the kernel or potentially corrupt memory by racing a task mm switch against account_mm_sched() accessing the old mm's scheduling statistics. Only recent 7.2+ kernels that include the sched/cache feature are affected; the flaw is fixed in Linux 7.2.9 and 7.3-rc5. Exploitation requires local code execution and a tight cross-CPU timing window, EPSS is 0.14% (3rd percentile), and no public exploit has been identified at time of analysis.
Use-after-free in GNOME Mutter's Wayland color-management (wp_image_description_v1) path allows a local, authenticated attacker who can run a malicious Wayland client to destroy the image-description resource while an asynchronous ICC file read is still in flight, after which the compositor writes into freed memory and frees a pointer derived from it - typically crashing the GNOME session and potentially enabling code execution inside the compositor process. The flaw is local-only and timing-dependent (it requires winning a race window), only applies to Wayland sessions where the color-management/ICC path is exposed (not X11-only sessions or builds without that code path), and no public exploit code or CISA KEV entry has been identified at time of analysis; in practice the more likely outcome is a session crash rather than reliable code execution. This is a credible local privilege/code-execution risk but not an urgent internet-facing emergency.
Local privilege escalation in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 stems from a misconfigured PATH environment variable (CWE-426) that lets a local attacker place a malicious executable in a directory searched before trusted system paths. Exploitation requires an existing low-privileged foothold on the host and a writable directory on the PATH, yielding high confidentiality, integrity and availability impact (CVSS 7.8, AV:L/PR:L/UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor has published a fix.
Privilege escalation in containerd's CRI checkpoint-restore path allows an authenticated local attacker who can submit an attacker-controlled checkpoint archive via CRI CreateContainer to have the restored process run with restored credentials (including root), full capabilities, and restored no_new_privs and seccomp state, while CRI status continues to report the requested ContainerConfig. The flaw affects containerd 2.1.0 through 2.2.6 and 2.3.0 through 2.3.3, and only where CRI checkpoint restore via CreateContainer is actually used; systems that never use this experimental feature are not affected. Rated CVSS 7.8 (High) with a local, low-complexity, authenticated (PR:L) vector, and no public exploit identified at time of analysis. Fixed in 2.2.7 and 2.3.4, where the restore-via-CreateContainer behavior is additionally disabled by default.
Remote code execution in Project MONAI 0.4.0 through 1.6.0 requires an on-path attacker to tamper with SENet pretrained weights fetched over plaintext HTTP, causing construction of SEResNet50 or another SENet model with pretrained=True to unpickle a crafted .pth file because load_state_dict_from_url is used without weights_only=True. The issue is unauthenticated but requires user interaction and a man-in-the-middle position; no public exploit identified at time of analysis. The CVE record rates it CVSS 7.7, though the assessed precondition set makes real-world urgency conditional rather than broadly exploitable.
Authenticated users of IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (including DB2 Connect Server) can obtain sensitive information they are not authorized to see by issuing the CREATE WRAPPER command, which is improperly authorized. The vulnerability is rated CVSS 3.1 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), so it requires a remote attacker to already hold valid Db2 credentials and the privilege to invoke CREATE WRAPPER; there is no integrity or availability impact, making this primarily an insider or compromised-credential risk rather than an unauthenticated breach vector. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, but fixed code is available from IBM and should be applied, particularly in environments where federation features are enabled.
Continue CLI through 1.5.47 can be tricked into executing commands outside its approved Bash prefix rules when an unauthenticated attacker injects instructions into repository files or fetched web pages that the agent processes; the agent then chains an unapproved command after ;, &&, or |, resulting in code execution as the user. Exploitation requires that the operator has configured at least one permissive Bash allow rule, that the agent is pointed at attacker-controlled content, and that the victim runs the agent against that content, so default installations without Bash approval rules are not exposed. No public exploit identified at time of analysis; the issue is rated CVSS 7.7 and is a genuine, moderately high-priority concern for users running the Continue CLI agent on untrusted inputs.
Authenticated users of the MarkLogic Query Console can read arbitrary files from the underlying server by supplying unsafe path values to a privileged filesystem helper, a classic path-traversal disclosure (CWE-22). The issue affects MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7, and carries a CVSS 3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), meaning a network-reachable, low-complexity attack by an authenticated principal that yields high confidentiality impact with no integrity or availability effect and a scope change because the helper runs with privileges beyond the caller's own. Because exploitation requires valid Query Console credentials, this is a credible moderate-to-high priority patching item rather than a drop-everything emergency; no public exploit code or confirmed active exploitation was identified at time of analysis.
Insufficient access controls in Progress MarkLogic Server 12.x (before 12.1.0) and 11.x (before 11.3.7) allow a remote, authenticated attacker holding only limited management privileges to read security-sensitive information, which can then be used to reach protected resources outside that account's intended scope. The CVE carries a 7.7 score with a scope-changing vector (S:C) because the confidentiality impact crosses a privilege boundary, but exploitation is gated on the attacker already possessing a valid low-privilege management account (PR:L), and no user interaction is required. No public exploit code and no CISA KEV listing were identified at time of analysis, so real-world exposure concentrates in multi-tenant or role-segmented installations, or as a lateral-movement step after an initial account compromise.
Authenticated users of the Red Hat OpenShift web console can abuse the Helm chart URL input to make the console pod issue requests to arbitrary destinations, turning the console into a Server-Side Request Forgery (SSRF) proxy (CWE-918, CVSS 3.1 base 7.7). Because the console pod typically sits inside the cluster network with broader reachability than the user, a low-privileged console account with the ability to add or load a Helm chart can use leaked error output to read sensitive responses and can perform blind port scanning against internal services. Exploitation requires an authenticated console session and the privilege to supply a chart repository URL (PR:L, unauthenticated outsiders cannot reach it), and the assessed impact is confidentiality-only with no integrity or availability effect; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
Unintended outbound network egress in IBM Maximo Application Suite's optional Location Service for Esri Component (versions 9.0, 9.1, and 9.2) stems from a misconfigured Kubernetes NetworkPolicy that fails to restrict pod egress, allowing traffic to reach destinations the deployment intended to block. Rated CVSS 3.1 base 7.7, the score is driven mostly by the Scope change (S:C) and High confidentiality impact (C:H) rather than ease of attack; the vector (AV:N/AC:L/PR:L/UI:N) indicates remote exploitation at low complexity but with the attacker already holding a low-privileged foothold inside the environment, and no user interaction is needed. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV not listed), so this is best treated as a moderate-priority network-segmentation and data-exposure issue affecting clusters that rely on the shipped NetworkPolicy for egress control.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 contains an XML external entity (XXE) injection flaw that allows an authenticated attacker holding an elevated/privileged account to read sensitive information from the application server and, through the changed-scope condition in the CVSS vector, potentially from resources beyond the vulnerable component's own security boundary. Network access with low attack complexity and no user interaction is required, but the PR:H privilege requirement confines realistic exploitation to insiders or attackers who have already obtained privileged credentials, making this a moderate-priority issue rather than an emergency; no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV.
Open WebUI versions 0.6.27 through 0.11.3 forward the entire browser cookie jar - session cookies included - to OpenAI-compatible connections, OpenAPI tool servers, and terminal servers that are configured in OAuth mode, letting the operator of such a destination server capture those cookies from routine requests and replay them to hijack accounts, including administrators. The issue is unauthenticated from the attacker's perspective (CVSS 4.0 7.6; independently assessed as CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N), but it is constrained: the attacker must control or monitor an endpoint an administrator has deliberately connected to, and a victim user must route a request through that connection. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV); a vendor-released patch exists in 0.11.4.
Path traversal in IBM Maximo Application Suite 8.10, 8.11, 9.0, 9.1 and 9.2 lets remote, unauthenticated attackers read arbitrary files from the server by sending crafted URL requests containing '../' sequences. The flaw carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), so impact is confined to confidentiality with no data modification or denial of service, and the independent assessment rates the overall signal as moderate and internally consistent rather than alarming. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV; practical exposure depends mainly on internet reachability and on the OS-level file permissions of the account running the Maximo web process, since only files that account can read are disclosed.
Path traversal in the Hex package manager for the Elixir/Erlang (Mix) ecosystem, versions 0.6.0 through 2.5.1, lets a malicious package publisher delete a directory outside the project's deps/ folder and write the package's files into that location when a developer runs mix deps.get or mix deps.update. The attacker abuses a dependency's OTP application label, which Hex copies from the signed registry without validation and Mix joins onto deps/ as the checkout path, so a crafted label such as '../../target' escapes the project tree through File.rm_rf!/1 before any dependency code is compiled. Exploitation requires the victim project to depend directly or transitively on the attacker-controlled release and the developer to explicitly fetch dependencies, so no victim-side authentication is needed (PR:N) but user interaction is required; no public exploit identified at time of analysis, and the vendor rates it CVSS 7.5.
Progress MarkLogic Server deployments on Microsoft Azure running 12.x releases before 12.1.0 or 11.x releases before 11.3.7 can write security-sensitive authentication information into diagnostic logs under a specific, non-default configuration, allowing anyone with read access to those logs to harvest credentials or secrets and use them to reach protected cloud resources. The exposure is confidentiality-only: the vulnerability itself provides no code execution, integrity, or availability impact, and it is limited to Azure-hosted deployments - on-premises and other non-Azure installations appear out of scope. Exploitation requires an attacker to already have access to the diagnostic logs (through log storage, a log aggregation pipeline, or insider/lateral access) and requires the triggering configuration to be present; no public exploit code and no confirmed active exploitation were identified at time of analysis. Note that the vendor-published CVSS 3.1 vector (AV:N/AC:L/PR:N, 7.5) describes a remote unauthenticated attack, which conflicts with the description, CWE-532, and our assessed vector (AV:L/AC:H/PR:L, confidentiality-only), so the practical attack path should be treated as a log-access-dependent secret disclosure rather than an unauthenticated remote breach.
A path traversal flaw in rebar3, the standard build and dependency-management tool for Erlang/OTP, lets a malicious Hex package publisher cause rebar3 to delete an arbitrary directory and write package files into it whenever a developer or CI job fetches that package's dependencies. The attack abuses an unvalidated 'app' field in Hex registry dependency metadata: rebar3 treats that field as the dependency directory name, so a value such as '../../../../target' resolves outside the project's _build tree and is then removed with rm -rf before the fetched package is moved into place. Only rebar3 3.7.0-rc1 through 3.27.1 is affected, exploitation requires user interaction (a developer running rebar3 get-deps against a project that pulls in the malicious release, directly or transitively), and because the deletion occurs before the dependency's rebar.config.script is evaluated and get-deps compiles nothing, the practical impact is destructive file deletion and overwrite rather than immediate code execution; no public exploit code has been identified at time of analysis, and the public hex.pm registry added validation for the field on 2026-10-12, leaving private or self-hosted Hex registries as the main residual exposure.
Arbitrary file write via path traversal in IBM Planning Analytics 2.0 and 2.1 allows remote unauthenticated attackers to write files to arbitrary locations on the server by submitting a crafted URL containing '/../' sequences. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high integrity impact but no confidentiality or availability impact. A vendor patch is available per IBM support node 7291604, and no public exploit identified at time of analysis.
Unauthenticated remote attackers can exploit deprecated OpsDirector functionality in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 to perform server-side request forgery (SSRF), making unauthorized requests to internal services or forging trusted requests that may expose protected information. Exploitation is conditional on the OpsDirector component being present and network-reachable; no public exploit code has been identified at time of analysis. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates high confidentiality impact with no integrity or availability impact.
XML external entity (XXE) processing in Progress MarkLogic Server 11.x before 11.3.7 allows remote, unauthenticated attackers to disclose local files or trigger outbound network requests from the server through attacker-supplied SAML messages. Exploitation is conditional: the instance must be configured to use SAML single sign-on, since only the SAML parser's handling of external DTDs and entities is affected, and the impact is limited to confidentiality (C:H, no integrity or availability impact, CVSS 7.5). No public exploit code and no confirmed active exploitation have been identified at time of analysis, so this represents a genuine but conditional priority - patching matters most for deployments that have SAML SSO enabled and exposed to untrusted networks.
Remote unauthenticated attackers can cause a denial of service in IBM Aspera Enterprise WebApps versions 1.0.0 through 1.0.6 by exhausting resources through uncontrolled resource consumption (CWE-400). The flaw is network-reachable with low complexity, requires no privileges or user interaction, and results in high availability impact, yielding a CVSS 3.1 base score of 7.5. No public exploit code has been identified at time of analysis, and IBM has released a patch.
MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 fail to consistently write successful authentication events to the audit log, which degrades a customer's ability to detect and investigate unauthorized access or credential misuse. The exposure is limited to logging/visibility: independent assessment rates the impact as integrity-only against the audit record (C:N/I:L/A:N), and the flaw gives an attacker no access by itself - harm only materialises after a separate successful authentication with legitimate or stolen credentials. There is no public exploit identified at time of analysis, and remediation is an upgrade to 12.1.0 or 11.3.7 or later.
Unauthenticated network requests to IBM Maximo AI Service 9.1.0 and 9.2.0 can exhaust server resources and render the service unavailable, as described by CWE-400 uncontrolled resource consumption. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), the flaw is network-reachable, low-complexity, and requires no credentials or user interaction, but its impact is confined to availability - there is no data disclosure, data modification, or code execution. IBM has published a vendor patch advisory (https://www.ibm.com/support/pages/node/7290473); no public exploit code and no confirmed active exploitation were identified at time of analysis, so the realistic risk is service downtime for internet- or network-exposed deployments rather than a breach.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 SaaS allows remote unauthenticated attackers to trigger uncontrolled recursion in an exposed processing path, causing availability impact. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so no privileges or user interaction are required and only availability is affected; no public exploit identified at time of analysis. IBM has released a vendor patch via its support advisory for the identified service levels, and because the product is SaaS, IBM controls the deployed instance and its patching.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 allows unauthenticated remote attackers to terminate the host process by sending malformed frames that the service does not handle correctly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms that no credentials or user interaction are required, so the only practical gating factor is network reachability to the service endpoint; impact is confined to availability with no data disclosure or modification. No public exploit code has been identified at time of analysis, and the vendor has published a patch advisory.
Denial of service in the IBM Maximo Application Suite IoT Component (versions 9.0.0, 9.1.0, and 9.2.0) allows a remote, unauthenticated attacker to exhaust or crash the service by triggering uncontrolled recursion in its input parsing/processing logic. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials or user interaction are required against a network-reachable instance, but the impact is strictly availability - there is no confidentiality or integrity effect. At the time of analysis there is no public exploit identified, and the vendor has released a fix via its support portal.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 lets remote, unauthenticated attackers disrupt the service through improper input validation (CWE-20), with impact limited to availability and no confidentiality or integrity loss. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) indicates the flaw is network reachable, low complexity, and requires no privileges or user interaction, so any deployment exposing the AI Service interface beyond trusted internal networks is at risk. No public exploit code has been identified at time of analysis and the CVE is not listed as confirmed actively exploited (CISA KEV); the practical risk is driven by exposure scope rather than observed attack activity.
Unauthenticated remote attackers can force the IoT Component of IBM Maximo Application Suite 9.0.0, 9.1.0, and 9.2.0 into an infinite parsing loop by submitting crafted input, hanging the parser and degrading or denying availability of the affected service. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so per the vector no credentials or user interaction are required, but the impact is confined to availability with no data exposure or code execution; the practical exposure depends on whether the IoT parsing interface is reachable from the attacker's network position. There is no indication of confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and our independent assessment rates this a moderate-priority availability issue rather than a top-tier emergency.
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 validate authentication tokens incorrectly, accepting a token the server should reject, so a remote attacker who can reach the instance can obtain unauthorized access under that token's identity. The vendor-published CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), while our independent assessment raises the confidentiality impact to High (C:H/I:H/A:N), reflecting that an improperly accepted token may expose data as well as permit modification; neither vector assesses any availability impact. No public exploit code or confirmed active exploitation was identified at time of analysis (the CVE is not in CISA KEV) and no EPSS score was available in the supplied data, so the realistic limiting factor is deployment exposure: the MarkLogic instance must be network-reachable by the attacker.
Improper validation of SAML assertions in Progress MarkLogic Server lets an unauthenticated remote attacker cause the server to accept an assertion that should have been rejected, potentially yielding unauthorized access to the MarkLogic deployment and its data. Affected are 12.x releases before 12.1.0 and 11.x releases before 11.3.7, but only instances explicitly configured to use SAML authentication and whose SAML endpoints are network-reachable are exposed to this flaw. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no credentials and no user interaction are required; no public exploit code was identified at time of analysis, and the vendor has published fixed versions 12.1.0 and 11.3.7.
Cleartext transmission of Amazon S3 credentials and data in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 allows a network-positioned attacker to intercept sensitive information when S3 integration is left on default transport settings. Exploitation is unauthenticated but requires the S3 feature to be in use, the default cleartext transport to be unchanged, and an on-path man-in-the-middle position; deployments using TLS, VPC endpoints, or VPNs are not at risk. No public exploit code has been identified at time of analysis, and our assessment rates this as AC:H rather than AC:L due to these prerequisites.
Progress MarkLogic Server deployments in the 12.x line before 12.1.0 and the 11.x line before 11.3.7 generate predictable anti-CSRF tokens for Query Console, allowing a remote attacker to forge requests that pass CSRF validation and execute server-side code with the permissions of a logged-in victim. Exploitation is conditional: the attacker must lure a user who currently holds a live authenticated Query Console session to an attacker-controlled page, so user interaction is mandatory and unattended servers or logged-out users are not reachable this way. A vendor advisory is available (community.progress.com MarkLogic Critical Security Alert Bulletin, October 2026) and confirmed fixed versions exist; there is no CISA KEV entry and no public exploit code identified at time of analysis, and no EPSS score was supplied, so this is best treated as a credible but conditional risk rather than a drop-everything emergency.
Improper verification of cryptographic signatures across the DigiDoc suite lets an attacker craft a document carrying a forged XAdES signature that affected software displays as valid, undermining the integrity of electronically signed documents (CVSS 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - pure integrity impact with no confidentiality or availability effect). The defect is reachable by unauthenticated remote attackers (PR:N) with no user privilege or special configuration, but exploitation still requires a relying party to validate the forged file with an unpatched build: libdigidocpp before 4.5.0, DigiDoc4 before 4.11.0, or DigiDoc for Android/iOS before 3.1.0. Vendor fixes are available per the ENISA-referenced disclosure and upstream PR; no public exploit code has been identified at time of analysis, and no active exploitation is confirmed.
Deny-pattern bypass in Network-AI's ClaudeHookBridge PreToolUse hook (versions 5.14.0 through 5.15.1) allows a prompt-injected agent to smuggle dangerous payloads past configured denyPatterns by placing a benign value in the first candidate field the hook inspects (such as file_path or command) while putting the actual malicious content in a secondary field the hook never evaluates, notably the Write tool's content parameter or an MCP script parameter - enabling web shell writes or script execution inside the local agent-execution context. The affected deployment must rely on the PreToolUse hook with denyPatterns as its guardrail, and exploitation additionally requires a successful prompt injection into the agent, which is why risk is bounded to local agent workflows rather than remote reachability; CVSS 4.0 scores 7.5 with attack requirements present (AT:P), and the assessed CVSS 3.1 vector is AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning no prior authentication or user interaction is required per the vector but the attack is local and complex. There is confirmed actively exploited status not present - no CISA KEV listing and no public exploit code - so at time of analysis no public exploit identified at time of analysis; EPSS, SSVC, and KEV signals were absent from the supplied intelligence, so prioritization inputs remain incomplete.
SQL injection in Kong Gateway (Enterprise and Open Source) Hybrid Mode clustering logic allows an attacker who can reach the Control Plane's clustering port and present a valid mTLS client certificate and key to inject arbitrary SQL into the Control Plane's backing database, resulting in unauthorized read and write access to gateway configuration and related data. Successful exploitation yields high confidentiality, integrity, and availability impact on the Control Plane database (CVSS 4.0 base 7.5 / assessed CVSS 3.1 8.8), but the prerequisites are substantial: the deployment must be running the Control Plane/Data Plane split, the attacker must have adjacent network access to the normally internal clustering channel, and must hold legitimate clustering credentials, which effectively limits realistic abuse to compromised Data Plane nodes or insiders with stolen cluster keys. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
openstack-network-exporter can be made to silently skip basic authentication when an operator enables user authentication but forgets or misconfigures TLS, letting an adjacent-network attacker pull OVS/OVN dataplane metrics without credentials. Only deployments in that specific non-default, inconsistent configuration are exposed; correct TLS deployments and deployments without authentication enabled are unaffected. The published CVSS is 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), but our assessment narrows this to AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - adjacency-limited, read-only information disclosure, with no integrity or availability impact and no public exploit identified at time of analysis.
Kerberos authentication service impersonation in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 lets an unauthenticated, suitably positioned network attacker impersonate trusted authentication infrastructure, potentially resulting in unauthorized access to or modification of protected data. Exploitation is conditional: it requires a deployment configured with Kerberos-backed password-based (external) authentication and an attacker holding a privileged on-path network position between the server and the Kerberos KDC, which is why CVSS rates attack complexity as high despite no required user interaction or prior authentication. No public exploit code or confirmed active exploitation has been identified at time of analysis.
FreeRDP 3.0.0 through 3.31.x allows an on-path attacker to capture OAuth authorization codes and substitute the OpenID discovery document during Azure AD authentication because freerdp_http_request() completes TLS handshakes without validating the server certificate chain. Exploitation requires the victim to use the Azure AD/AAD-brokered RDP path (plain RDP is unaffected) and to actively perform the login while the attacker holds a man-in-the-middle network position, making this a conditional risk rather than a broadly exploitable flaw. No public exploit code has been identified at time of analysis, and the issue is patched in FreeRDP 3.32.0.
Arbitrary file write in Progress ShareFile Storage Zones Controller 5.12.6 and earlier lets an unauthenticated remote attacker who can influence the remote file identifier consumed by FileCopyService place attacker-controlled content into any filesystem location writable by the Storage Zones service account. Escalating that write to remote code execution requires a second, non-default condition: an IIS-served directory that is both executable and writable by that same account, which is why the assessed attack complexity is high. No public exploit code has been identified at time of analysis, and the risk profile is configuration-dependent rather than a mass-exploitation emergency.
Cleartext transmission of certain cluster-management communications in Progress MarkLogic Server 12.x releases before 12.1.0 allows an on-path attacker to read and modify inter-node management data, compromising both confidentiality and integrity of cluster operations. The vendor CVSS is 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N): exploitation requires no authentication and no user interaction, but the attacker must already occupy a man-in-the-middle position on the network segment carrying MarkLogic cluster traffic, which in well-segmented environments is a trusted internal VLAN not reachable from general user networks - realistically limiting exposure to insiders or attackers who have already achieved lateral movement. Availability is unaffected, and no public exploit identified at time of analysis.
Outbound TLS connections initiated by Progress MarkLogic Server can be intercepted and modified by an on-path attacker because the product does not consistently validate the certificate hostname for certain outbound connections (CWE-297). Affected are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is unauthenticated from the attacker's perspective (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) but requires the attacker to first occupy a man-in-the-middle position - for example via ARP or DNS spoofing, a rogue gateway, or control of intermediate network infrastructure - and requires MarkLogic to actually open one of the specific outbound connections that skip hostname verification. Impact is limited to confidentiality and integrity of those communications (C:H/I:H) with no availability impact and no code execution; no public exploit code or active exploitation has been identified at time of analysis.
Man-in-the-middle interception of IBM DataStage on Cloud Pak for Data 5.4.0.0 client sessions lets an attacker who presents a forged TLS certificate capture the IAM bearer Authorization header that the session adapter attaches automatically, granting full platform-scope tenant API access to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. The root cause is CWE-295 improper certificate validation in client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor on the path between that machine and the Cloud Pak for Data platform - a co-tenant inside the shared cluster cannot exploit it - together with an active authenticated session that transmits a live token. CVSS 3.1 scores this 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N); no public exploit identified at time of analysis, and patch data indicates a fix is available from the vendor.
Arbitrary local program execution is possible in EdgeEver Desktop 1.92.0 through 1.112.0 because the desktop:acp-probe IPC handler performs no sender validation and spawns whatever executable path is supplied in the caller's input.path, running it with the victim user's privileges. This is not a standalone network RCE: an attacker must first land stored cross-site scripting in a renderer through the template-preview or drag-preview feature, and the victim must then preview that attacker-controlled content so the renderer script can invoke probeAcpAdapter (CVSS v4.0 7.3; independent assessment CVSS v3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). No public exploit code and no CISA KEV listing were identified at time of analysis; an upstream fix commit has been referenced, but no patched release version has been independently confirmed.
Cross-site request forgery in the Patreon WordPress plugin (patreon-connect), affecting all versions up to and including 1.10.0, allows an attacker to ride a logged-in user's browser session and trigger state-changing plugin requests that lack a valid anti-CSRF token. The CVSS vector (PR:N, UI:R) means the attacker needs no credentials of their own but must convince an authenticated user - typically a site administrator or other privileged account - to load attacker-controlled content while logged in; the realistic impact is unauthorized state modification rather than data theft or denial of service. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so there is no evidence of active exploitation; the Patchstack advisory is the only public reference.
An out-of-bounds read in the Netcore NR268 router firmware (version 1.7.121109) can be triggered by manipulating the put_file argument of the ARP filter import handler at /router/filter_arp_put_file.cgi, allowing an attacker with an authenticated management session to disclose process memory or crash the device; no code execution or lateral impact was assessed. Exploitation requires high/administrative privileges (CVSS PR:H) on the router, so this is not reachable by an anonymous external attacker despite the network-facing attack vector. Publicly available exploit code exists - the researcher's write-up is published on GitHub and the vendor was contacted but never responded - and the CVSS 4.0 vector carries an E:P (proof-of-exploit) modifier; no CISA KEV listing and no EPSS score were supplied in the available data, and no vendor-released patch has been identified, so unpatched, internet- or management-exposed NR268 units should be treated as at risk of authenticated memory disclosure and denial of service.