Improper authorization in Apache SkyWalking BanyanDB 0.11.0 allows a user holding only a readonly Canopy role to push non-read requests through the Canopy monitoring proxy to a configured monitoring target, effectively escalating a read-only account into a write-capable path. The flaw is reachable only under a non-default deployment in which the experimental Canopy proof-of-concept role system and the monitoring-proxy feature are both enabled and a monitoring target is configured, and the attacker must already hold a valid low-privilege Canopy credential; the headline CVSS of 9.1 assumes PR:N/AC:L, which conflicts with this assessed PR:L/AC:H profile. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS is low at 0.15% (4th percentile), reflecting the narrow configuration prerequisites. Users should upgrade to 0.11.1, which fixes the issue.
Authenticated low-privilege attackers can invoke destructive PostgreSQL database operations in Zoho ManageEngine DDI Central by exploiting insufficient access control on the high-availability (HA) failover endpoint in all versions before 6201. With a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), the flaw is network-reachable, requires only low-privilege credentials and no user interaction, and carries full impact to confidentiality, integrity, and availability - an attacker who reaches the failover endpoint can act well beyond their intended permissions. The vendor has published a fix in version 6201, and no public exploit code has been identified at time of analysis; this CVE is not in CISA KEV, so there is no confirmation of active exploitation.
Authenticated command injection in Apache Karaf's instance-management service lets a principal who can reach the instance:* shell commands (instance:create, instance:start, instance:restart, instance:change-opts) or the equivalent InstancesMBean JMX operations execute arbitrary OS commands as the Karaf process user, because the caller-supplied javaOpts value is concatenated into a launch string that is then handed to /bin/sh or cscript. Affected deployments are Apache Karaf instances before 4.4.12, and exploitation requires an authenticated principal (CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) with the ability to supply javaOpts; the risk is amplified by a fail-open default in which unconfigured command scopes are not role-restricted. EPSS is low (0.40%, ~32nd percentile), CISA SSVC records no known exploitation, and no public exploit code was identified at time of analysis, so this is a high-priority but not an emergency issue.
PHP object injection in the ConvertPlus WordPress plugin (all versions through 3.6.3) allows any authenticated attacker at Subscriber level or above to reach the cp_display_preview_modal AJAX action, bypass its nonce guard simply by omitting the cp_admin_page_nonce parameter (the isset() check fails open and no capability check is performed), and inject a second attacker-controlled [smile_modal] shortcode via the style parameter that ultimately feeds attacker-supplied base64-decoded bytes into maybe_unserialize() with no allowed_classes restriction. The object-injection primitive is inert by itself - ConvertPlus ships no usable POP gadget chain - so real impact such as arbitrary file deletion, sensitive data disclosure, or code execution requires a separate installed plugin or theme that provides a compatible chain. No public exploit code or confirmed active exploitation was identified at time of analysis, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) reflects the low-privilege login requirement and the strong third-party gadget-chain dependency rather than automatic compromise.
Authorization bypass in Apache Karaf before 4.4.12 allows an authenticated JMX client holding any role - including the least-privileged 'viewer' - to evade RBAC and achieve remote code execution inside the Karaf JVM. Karaf's MBeanServer guard never checks the lifecycle operations createMBean, registerMBean and unregisterMBean, so a caller can instantiate and register the standard javax.management.loading.MLet class and then invoke its getMBeansFromURL operation, which the shipped default 'get* = viewer' ACL wildcard inadvertently authorizes, causing attacker-hosted classes to be fetched and loaded as new MBeans. Exploitation requires network reachability to the default-enabled remote JMX RMI connector on ports 1099/44444, a valid JMX credential of any role, and outbound network access to the attacker's .mlet host; no public exploit code and no active exploitation were identified at time of analysis, and the issue is rated important by the vendor while the independent assessment places it at high impact across confidentiality, integrity and availability.
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. Rated 8.8 by the vendor (the independent assessment scores it higher, 9.9, because the trust boundary crossing changes scope); no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis.
OS command injection in aaPanel BaoTa through 11.8.0 lets an authenticated panel operator execute arbitrary shell commands on the underlying host by supplying a crafted Password value to the archive-extraction routine. The defect sits in the function panelTask.bt_task._unzip within /www/server/panel/class/panelTask.py, and because the panel normally runs as root a successful injection yields full server compromise; a user-interaction step is required to invoke the unzip workflow. Publicly available exploit code exists (disclosed via a public gist referenced by VulDB), the vendor was contacted early but did not respond, and no vendor-released patch has been identified at time of analysis - this is the third near-identical command-injection flaw in the same release line alongside CVE-2026-101007 and CVE-2026-101008.
An unauthenticated remote attacker can lock up an Angular server-side rendering process by submitting HTML that contains an unterminated DOCTYPE declaration with trailing whitespace (for example `<!DOCTYPE html `), which drives the bundled domino HTML parser into an infinite synchronous loop that pins a CPU core at 100% and stalls the Node.js event loop, silently dropping all concurrent and subsequent requests. Only SSR deployments that run @angular/platform-server and feed attacker-controlled markup into server-side DOM parsing - via `[innerHTML]`, interpolation into rendered HTML, `insertAdjacentHTML`, `outerHTML`, or server-side sanitization - are reachable; the vulnerable version ranges are <=19.2.25, 20.0.0 through 20.3.30, 21.0.0 through 21.2.22, and 22.0.0 through 22.1.5. The trigger payload is trivial to construct, but no public exploit code has been observed circulating and the issue is not listed in CISA KEV, so the practical risk is a function of whether the application actually routes untrusted HTML through domino on the server.
OS command injection in SUSE NeuVector 5.4 (before 5.4.11), 5.5 (before 5.5.4), and 5.6 (before 5.6.2) allows an attacker who already satisfies one of two prerequisites - an authenticated NeuVector user holding the namespaced Runtime Policies (write) permission, or possession of NeuVector's internal gRPC certificate key pair - to inject operating-system commands that execute inside the privileged enforcer container, resulting in complete compromise of the underlying worker node. The flaw is rated 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning remote reachability, low attack complexity, authenticated low privileges, and no user interaction, with total confidentiality, integrity, and availability impact once the prerequisite is met. Ordinary read-only users and unauthenticated network clients cannot trigger it, but any deployment that grants Runtime Policies write access broadly or leaks the internal gRPC key pair is at high risk; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, though weaponization would be straightforward given the trivially reachable command sink.
Authenticated remote code execution in FreePBX (versions prior to 16.0.10 and 17.0.5) lets an attacker who possesses a valid, known username abuse the sound-language upload and conversion workflow to write arbitrary files, including malicious PHP, into the web server's document root. The root cause is a path-traversal weakness (CWE-22) in the conversion step where path sanitization is insufficient, and successful exploitation gives full confidentiality, integrity and availability impact on the PBX host (vendor CVSS v4.0 8.7; independent assessment CVSS v3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, so authentication - not user interaction - is the gate). No CISA KEV entry and no public exploit code were identified at time of analysis, meaning this is a high-severity, patch-now issue for PBX administrators rather than a mass-exploitation emergency; practical risk concentrates where FreePBX administrative panels are internet-facing or protected by weak or default operator credentials, and is reduced where the panel is network-segmented.
Code injection in Innotim Logsign SIEM versions 6.4.101 through 6.4.117 exposes network-reachable deployments to full compromise of confidentiality, integrity, and availability, as reflected by the CVSS 3.1 score of 8.8 and the CVE's CWE-94 classification. According to the CVSS vector (AV:N/AC:L/PR:L/UI:N), exploitation requires a valid low-privilege authenticated account on the SIEM instance, needs no user interaction, and can be carried out with low complexity - an anonymous attacker cannot trigger it without first obtaining credentials, and the risk is confined to the stated version window. No public exploit code or confirmed active exploitation was identified at time of analysis, and the specific vulnerable feature or endpoint is not disclosed in the available advisory data.
Authenticated SQL injection in Iron Mountain enVision builds prior to 260655 allows a network-based attacker holding a low-privilege account to inject arbitrary SQL through an improperly neutralized input parameter. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) reflects low-complexity exploitation with no user interaction and high impact across confidentiality, integrity, and availability, meaning an authenticated user could read, modify, or destroy database contents. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but the vendor reports a patch is available; discovery is credited to TR-CERT (Turkish national CERT).
Authenticated abuse of the document upload function in eBA Plus Document and Workflow Management System (versions 6.7.141 through 10.0.10) lets a low-privilege user place a Web Shell on the server and, if the uploaded file can be reached through a web-accessible path, run code with the privileges of the web application. The defect is CWE-434 (unrestricted upload of a file with a dangerous type) and carries a CVSS of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so valid credentials or a self-registration path are required rather than unauthenticated access, and installations already on 10.0.11 or later are outside the affected range. No public exploit has been identified at time of analysis; TR-CERT (Turkish national CERT) is the reporting and reference source. This is a genuine high-priority issue for organizations running the affected product.
Unauthenticated stack-based buffer overflow in Buffalo WSR-300HP routers and WEX-G300 Wi-Fi extenders allows network-adjacent attackers to crash devices via crafted HTTP requests, causing denial-of-service. Exploitation requires network access to the HTTP management interface, typically only reachable from the local network unless remote administration is exposed to the WAN. No public exploit code or confirmed active exploitation (CISA KEV) has been identified, and the issue is assessed as genuine but low-priority due to reachability constraints.
Missing authorization in WarehousePG (WHPG) 7.x before 7.6.0-WHPG lets any authenticated database role - with no superuser rights, no GRANT, and no special role membership - call the built-in server-side file functions pg_file_write, pg_file_rename, pg_file_unlink and pg_logdir_ls, because the REVOKE that contrib/adminpack applies to the equivalent functions was never carried over to WHPG core when their catalog entries were repointed to the ungated adminpack-derived _v1_1 implementations during the merge onto a PostgreSQL 12 base. An attacker holding ordinary database credentials can therefore create, append to, overwrite, rename and delete files under the data and log directories and enumerate log file names, and by appending directives such as shared_preload_libraries or archive_command to postgresql.auto.conf can achieve arbitrary code execution as the postgres operating system user on the next server restart or configuration reload. WarehousePG 6.x is not affected because its equivalent functions enforce an internal superuser check, and no public exploit code has been identified at time of analysis (no CISA KEV entry).
Account takeover of the InvoicePlane primary administrator (user_id=1) is possible for any authenticated secondary administrator (user_type=1, user_id != 1) on version 1.7.2 prior to commit 8616fa4. The attacker uses Users::form(), which performs no object-level authorization check on the primary admin's record, to overwrite the primary administrator's user_email value (it is not listed in PROTECTED_FIELDS), then drives the instance's public, logged-out password-recovery flow that resolves accounts by user_email to obtain the reset token and seize control of user_id=1. This is an alternate path around the earlier fix in PR #1638, which protected only Users::change_password(); no public exploit code was identified at time of analysis and there is no CISA KEV entry, but the vendor has published a GitHub Security Advisory (GHSA-77hm-22wp-96wp) and a patch commit.
Authenticated command injection in FreePBX prior to 17.0.9 allows a user who is authorized to access the GraphQL API module interface to execute arbitrary shell commands on the PBX host, running as the web/PBX service account (typically 'asterisk'). The flaw sits in the PBX API module's documentation generator, which accepts a caller-supplied 'host' parameter and interpolates it into a shell command; the code validates the generated OAuth access token before execution but never validates or escapes the host value. Exploitation requires a pre-existing, privileged account with API-module authorization (CVSS:4.0 PR:H, our assessment CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), which materially limits exposure; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor-released fix is version 17.0.9.
Circuit soundness failure in Payy (polybase/payy) prior to 1.3.0 lets an authorized rollup prover smuggle an extra burn message into the public messages[1000] array accepted by RollupV1.verifyRollup(), causing the rollup contract to transfer USDC from the contract to an attacker-controlled recipient. The attacker must be a registered prover with the ability to construct a valid agg_final proof for an already-approved rollup block and to manipulate the unconstrained tail of the public input array, so the assessed vector is authenticated (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, integrity-only impact with no confidentiality or availability loss). Exploitability today is further limited because verifyRollup() is restricted to the existing allowlisted prover, but the flaw becomes effectively unauthenticated under the permissionless prover model in the Payy whitepaper (Section 3.3.2 stake-to-join and Section 3.3.1 fallback submission by other nodes). No public exploit code had been identified at time of analysis, and the vendor-released patch is version 1.3.0.
Authenticated command injection in the FreePBX User Control Panel (UCP) allows any account with UCP access - including low-privilege users who are frequently granted UCP but not Administrator Control Panel (ACP) rights - to run arbitrary commands on the PBX host as the web-server user (typically asterisk) via crafted HTTP requests. The flaw affects FreePBX versions prior to 16.0.39 and 17.0.7 and stems from insufficient sanitization of UCP URL parameters, which permits command chaining into host binaries; the vendor rates it CVSS 8.6 (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H) and the independent assessment concurs with high confidentiality and integrity impact over the network with low privileges required. No public exploit identified at time of analysis, and successful exploitation requires a valid UCP session plus network reachability to the PBX web interface, but no victim interaction.
Authenticated users holding backup or restore privileges on affected FreePBX deployments can achieve remote code execution through the backup Module on versions prior to 16.0.72 and 17.0.7. Improper path sanitization during backup restore lets a crafted archive place attacker-controlled PHP files directly into the web root, where the FreePBX web server will execute them, giving the attacker full control of the host and, by extension, the underlying Asterisk telephony platform (CVSS:4.0 8.6; independent assessment scores CVSS:3.1 8.8, AV:N/AC:L/PR:L/UI:N with high confidentiality and integrity impact). Exploitation is not pre-authentication: it requires a valid account with sufficient access permissions and/or write access to backup files plus network reachability of the FreePBX administration interface, and no public exploit code has been identified at time of analysis. This is a high-priority issue for internet-exposed or broadly permissioned FreePBX instances rather than a drop-everything emergency, since the primary attack surface is a privileged administrative workflow.
Authenticated remote code execution in the FreePBX Superfecta module (FreePBX prior to 16.0.40 and 17.0.7) allows a user holding valid credentials with a known username to make the module's AJAX handler dynamically include attacker-influenced PHP files from its sources/ directory, executing arbitrary PHP with the privileges of the web server user. Exploitation is remote and low-complexity from the attacker's side (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N, score 8.6), but our assessment notes the inclusion flaw alone is not sufficient: per the GitHub advisory (GHSA-j53p-5m8r-j3p6) the attacker must chain it with arbitrary directory creation via the backup module and a path-revealing file upload via the soundlang module, so the Superfecta, backup, and soundlang modules must all be present and a valid login is mandatory (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; vendor-released patches are available in versions 16.0.40 and 17.0.7, making this a high-priority fix rather than an internet-facing emergency, particularly for systems with the affected modules exposed to untrusted users.
Loading a malicious model into Unsloth Zoo 2025.9.9 through 2026.8.13 (as shipped in Unsloth 2025.9.9 through 2026.8.19) lets that model's config.json run arbitrary Python in the loading user's process, because a nested model_type value containing a newline escapes into an exec()-generated import statement. Exploitation requires the victim to load an attacker-controlled model for training or inference - a user-interaction gate, but no authentication on the attacker side (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; vendor score 8.6). No public exploit code has been identified at time of analysis, and the practical exposure is concentrated in pipelines that automatically ingest third-party or user-supplied models from public hubs rather than those loading only vetted first-party checkpoints.
Authenticated command injection in BUFFALO WSR-300HP wireless routers and WEX-G300 range extenders lets a user who already holds administrative access to the device's web management interface execute arbitrary operating system commands by submitting a crafted HTTP request to a web form field. Successful exploitation yields full compromise of the device (confidentiality, integrity and availability all rated High), but the attack is gated behind valid admin credentials or an active admin session, which is the dominant risk-limiting factor, and the affected models are primarily Japanese consumer/SOHO devices. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the vendor CVSS 4.0 score of 8.6 reflects impact severity once the prerequisite administrative access is met.
OS command injection in the WatchGuard AP diagnostic CLI allows an authenticated administrator to execute arbitrary operating system commands on the affected access point by supplying crafted input to a diagnostic parameter. The vulnerability carries a CVSS v4.0 base score of 8.6 (CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and is independently assessed as CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H; exploitation requires valid administrator credentials for the AP's CLI (PR:H), but once authenticated no user interaction and only low attack complexity are needed, yielding high confidentiality, integrity, and availability impact on the device itself. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so realistic risk is concentrated where the AP management/CLI is network-reachable and administrative credentials are weak, reused, or exposed.
Server-side request forgery and local file inclusion in Regular Labs Modules Anywhere for Joomla (Pro versions 1.5.0 through 9.0.5) allow an attacker with content-authoring privileges to override module parameters and cause the server to open attacker-influenced URLs or local files. The parameter-override feature is enabled by default and applies attributes without verifying who authored the content containing the module tag; Joomla's core Feed module with its rssurl parameter is a confirmed vector. The vendor rates this 8.5 under CVSS 4.0, but the independent assessment (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N) indicates high technical impact with moderate real-world priority because authentication is required and exposure depends on the selected module; no public exploit was identified at time of analysis.
Command injection in the aaPanel (BaoTa) server management panel through version 11.8.0 lets an authenticated high-privilege panel user execute arbitrary operating-system commands by manipulating the split_file_path argument handled by merge_split_file in /www/server/panel/class/files.py. The flaw is network-reachable and requires no user interaction, but it demands an existing administrator-level session (PR:H), so realistic risk is concentrated on panels with untrusted account holders, exposed management interfaces protected by weak or default credentials, or environments where admin credentials have already been stolen. Publicly available exploit code exists, exploitation evidence is rated E:P, and the vendor was contacted early but did not respond, so no fix is currently available; this is a genuine but conditional risk rather than a pre-auth emergency.
A static buffer overflow in ZoneMinder's Remote HTTP camera response parser (RemoteCameraHttp::GetResponse()) affects all versions before 1.38.4 and lets a malicious or compromised HTTP camera - or an on-path attacker able to modify the camera's traffic - corrupt fixed-size buffers by sending oversized HTTP status messages, Connection headers, Content-Type values, or multipart boundaries. Successful abuse corrupts parser state and can crash the capture process or corrupt memory; integrity impact is limited (VI:L) while availability impact is high (VA:H), and no public exploit has been identified at time of analysis. Exploitation is unauthenticated but conditional: it requires a monitor configured for a remote HTTP camera source and attacker positioning on the camera side of the connection rather than against ZoneMinder's own listening interface.
Prototype-pollution gadget in the Axios promise-based HTTP client for Node.js and the browser lets a separate, pre-existing prototype-pollution flaw in the same JavaScript process steer how ToFormData serializes outgoing request bodies in Axios 0.28.0 through 0.33.x and 1.15.1 through 1.19.x. Inherited dots, indexes, metaTokens, maxDepth, visitor, or Blob values planted on Object.prototype silently rename or reinterpret serialized fields, or make requests fail outright via a polluted maxDepth; a polluted visitor only executes when the attacker already possesses a stronger function-injection primitive, so Axios adds no new code-execution capability on its own. Remote unauthenticated exploitation is inert without that chained second bug, and no public exploit identified at time of analysis, with no confirmed actively exploited (CISA KEV) status; vendor-released patches ship in 0.34.0 and 1.20.0.
An authenticated user with access to the EmailTask component in Google Cloud Application Integration (versions prior to 2026-06-30) can exploit a confused deputy weakness to read and exfiltrate arbitrary Google-internal files by supplying a crafted attachment file path. The flaw requires low-privilege authentication (PR:L) and no user interaction, with high confidentiality impact (C:H) on both the service and a subsequent system (SC:H). No public exploit code or active exploitation has been identified at time of analysis; the issue was patched server-side on 2026-06-30, so no customer action is required.
Authenticated federation peers can cause denial of service and broker state manipulation in Apache ActiveMQ Artemis before 2.34.0 by sending a crafted FEDERATION_DOWNSTREAM_CONNECT packet that forces the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. The vulnerability arises from unsafe reflection (CWE-470) in FederationStreamConnectMessage.getFederationPolicy(), which passes an unvalidated class name from the CORE protocol wire buffer to Class.forName(). Although the original CVSS 3.1 vector reports PR:N (8.2 High), the described authentication requirement means the practical severity is lower; the authoritative assessment uses PR:L. No public exploit code has been identified at time of analysis.
Denial of service in the Axios HTTP client affects Node.js deployments running versions 1.15.0 through 1.19.x, where a crafted redirect Location hostname triggers quadratic regular-expression backtracking inside the proxy-bypass check and blocks the Node.js event loop. Successful exploitation requires an unusually specific combination - HTTP_PROXY/HTTPS_PROXY set, a non-empty NO_PROXY/no_proxy value, redirect following enabled, and requests reaching an attacker-influenced server that can return the malicious redirect - so exposure is narrow, and the reverse-trust nature of the attack means the adversary must control or compromise the redirect target rather than simply send a request to the victim. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV) for CVE-2026-101906; the high vendor CVSS 4.0 score of 8.2 largely reflects the VA:H availability weighting rather than ease of exploitation, as reflected in our independent assessment of CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
Axios versions 1.13.0 through 1.19.x can crash a Node.js process because the HTTP/2 adapter installs no error handler on a ClientHttp2Session created for a request made with httpVersion: 2, so a session-level 'error' event emitted during session initialization or reuse escapes normal Promise rejection handling and becomes an uncaught exception that terminates the process, producing a denial of service. Only applications that explicitly opt into HTTP/2 are affected; the browser build and the default HTTP/1.x path are not, and the attacker must additionally be able to induce a genuine HTTP/2 session error (for example via a peer or intermediary), which is why the independent assessment rates this as high complexity rather than trivially triggerable. Impact is availability-only - no data exposure, no code execution, and no privilege requirement (unauthenticated). No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Axios 1.16.1 through 1.19.x can be driven into catastrophic regular-expression backtracking through its data-URI parser, letting an unauthenticated remote attacker stall the Node.js event loop and cause a denial of service. The trigger is an attacker-controlled, malformed RFC 2397 data URL containing many slash characters on both sides of the media-type separator and no comma, which the fromDataURI / DATA_URL_PATTERN logic must exhaustively re-split before rejecting; because the parse is synchronous, the whole single-threaded process is blocked. Exploitation requires that the application actually route untrusted input into Axios's data: parsing path, so services that only make ordinary HTTP requests are not exposed; there is no confidentiality or integrity impact, authentication is not required, and no public exploit identified at time of analysis. Severity is rated 8.2 under the supplied CVSS 4.0 vector, while our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) treats it as availability-only and high-complexity given the deployment prerequisite, and the vendor-released patch is Axios 1.20.0.
Token exposure in the Network UPS Tools GitHub Actions tarball-preparation workflow allows an attacker submitting a fork pull request to cause the job to run with a single-use write-permission GITHUB_TOKEN that is reachable by untrusted PR-source-branch content, letting the attacker extract the token. Because the vector is AV:N/AC:H/PR:N/UI:R/S:C, exploitation is unauthenticated at the network level but requires user interaction (the workflow must actually run on the malicious fork PR) and is confined to the short window while the GHA job and token remain valid; within that window the token's write scopes permit manipulation of repository contents, commit checks/statuses, or issue/PR comments. GHSA-w6wj-3r73-fxmh documents the flaw, which is fixed by commits 658b24e and 1aa31d1; no public exploit identified at time of analysis. This affects only the NUT project's CI supply chain - installed NUT UPS/PDU monitoring deployments are not affected.
Memory exhaustion denial-of-service in Elixir Mint affects versions 1.1.0 through 1.10.x and allows a malicious or compromised HTTP/2 server to force a client application to allocate roughly 1 GB per response by abusing HPACK indexed header fields and cookie handling, potentially exhausting the BEAM VM. The vulnerability requires the application to initiate an outbound HTTP/2 connection to an attacker-influenced endpoint (reverse-trust), and no public exploit code or confirmed active exploitation is identified at time of analysis. Downstream clients such as Finch and Req that use Mint are also affected when making outbound HTTP/2 requests to untrusted servers.
Remote attackers holding a previously issued Rancher session token can retain access even after the legitimate user logs out in SUSE Rancher 2.15 before 2.15.2, because the server fails to clear credentials on logout (CWE-613). This session persistence flaw carries a CVSS 3.1 base score of 8.1 (High) with network reach, low complexity, no attacker privileges (PR:N), and required user interaction (UI:R) for the logout. No public exploit identified at time of analysis; exploitation is limited to scenarios where the attacker already possesses a valid token, such as shared-device or stolen-session situations.
Authorization bypass in Enocta Platform (all versions through 2026-09-28) lets an authenticated low-privilege user read or alter other users' records by tampering with a user-controlled identifier in requests. With a CVSS 3.1 base score of 8.1 (High), the flaw yields high confidentiality and integrity impact but no availability impact. No public exploit code has been identified and the issue is not in CISA KEV; exploitation requires a valid low-privilege account on the platform.
Local privilege escalation in Extegrity Exam4 on macOS lets any unprivileged local user escalate to full root by abusing command injection in the root-running com.extegrity.LogTool privileged helper, which is reachable over XPC. An attacker with a low-privileged local session (PR:L, AV:L, no user interaction required, UI:N) can send crafted XPC messages that reach [ConsoleLogHelper copyConsoleIntoFileFromStartDate:], where attacker-controlled parameters are passed into a syslog command without sanitization and executed with root privileges via LaunchSynchronous, yielding complete confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, HIGH). Exploitation requires the helper to be installed, registered, and reachable on the host; remote exploitation is not possible, and no public exploit code was identified at time of analysis.
Command injection in the Windows DNS Query Resolution Policy name field of ManageEngine DDI Central versions below 6201 enables an authenticated high-privilege administrator to run arbitrary operating-system commands, resulting in remote code execution on the DDI Central host. The CVSS 3.1 vector (7.2 HIGH, AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) reflects a network-reachable, low-complexity attack that nonetheless requires privileged console access and the ability to create or edit a Windows DNS Query Resolution Policy, and no public exploit has been identified at time of analysis. The vulnerability is fixed in version 6201, so affected deployments that manage Windows DNS should be prioritized for upgrade, especially since a successful exploit yields full confidentiality, integrity, and availability impact on the compromised server.
An insufficient buffer-size validation defect in Zephyr RTOS's ADI MAX32 ADC driver (drivers/adc/adc_max32.c) allows a local, low-privileged user-mode thread to write up to twice the length of its supplied buffer into kernel memory, producing attacker-controlled out-of-bounds writes at an attacker-chosen offset. Exploitation requires a build compiled with CONFIG_USERSPACE running on ADI MAX32 hardware where the calling thread has already been granted access to a MAX32 ADC device object; on such a build the attacker fully controls channels, buffer, buffer_size and options->extra_samplings, and the resulting corruption of adjacent memory, kernel data or thread stacks is a plausible local privilege-escalation and denial-of-service primitive (CVSS 7.8, AV:L/PR:L). The flaw is not remotely exploitable, and builds without CONFIG_USERSPACE are reduced to a caller-side robustness defect since the application supplies its own buffer; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
An out-of-bounds kernel-mode write in Zephyr RTOS's NXP MCUX LPADC driver (drivers/adc/adc_mcux_lpadc.c) lets an unprivileged user-mode thread corrupt memory outside its own partition, providing a genuine local privilege-escalation and denial-of-service primitive rather than an inflated high-severity score. The bug affects builds compiled with CONFIG_USERSPACE that use the MCUX LPADC driver in interrupt-driven mode (or DMA-driven mode on releases carrying the DMA path), where adc_read()/adc_read_async() are system calls: a thread already granted access to the LPADC device object controls channels, buffer, buffer_size and options->extra_samplings, and can demand up to channels × 65536 samples into a tiny buffer, causing the driver's ISR or DMA callback to walk past the buffer while running in kernel mode where the MPU does not confine it. No public exploit code or confirmed active exploitation has been identified at time of analysis, but the CVSS vector (7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects high confidentiality and integrity impact from an authenticated local attacker, and upstream fixes are available.
Kernel memory corruption in Zephyr RTOS arises from the RTIO userspace syscall verifier z_vrfy_rtio_sqe_copy_in_get_handles(), which validates the RTIO object handle and the incoming sqes array but never checks that the caller-supplied handle out-parameter is writable before executing *handle = sqe in supervisor mode. Any user-mode thread that has been granted a struct rtio kernel object - the normal situation for applications using sensor_read_async_mempool() or the async ADC helpers, which call rtio_sqe_copy_in_get_handles() internally - can supply an arbitrary destination address and thereby obtain a write-what-where primitive that stores a pointer to attacker-controlled ring data at any kernel location, corrupting function pointers, thread structures or memory-domain partition tables and breaking the CONFIG_USERSPACE isolation boundary. The issue is local-only and build-gated (CVSS 7.8, AV:L/PR:L, CWE-787), requires both CONFIG_USERSPACE and CONFIG_RTIO, and no public exploit code has been identified at time of analysis, although an upstream vendor fix and GitHub security advisory are available.
Memory corruption in Wind River VxWorks 7 occurs when a task passes crafted arguments to a specific system call, causing an out-of-bounds write inside the RTOS memory-management subsystem and giving the caller full confidentiality, integrity, and availability impact on the running instance (CVSS 3.1 7.8 HIGH). The flaw is local in nature - per the vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) the attacker must already execute code on the device as at least a low-privileged task, so only VxWorks 7 deployments that run untrusted or lower-trust code are realistically exposed; locked-down devices that execute only vendor-signed firmware are not remotely reachable through this bug. All VxWorks 7 builds prior to version 26.09 are affected, and there is no public exploit code or CISA KEV entry identified at time of analysis.
Cross-weblog authorization bypass in Apache Roller 6.1.5 lets an authenticated user holding authoring rights on one weblog read, modify, or delete resources belonging to another weblog - bookmarks, bookmark folders, media files and directories, entries, categories, and comments - by supplying identifiers that are resolved without being scoped to the acting weblog. The same flaw allows a user with administrator rights on their own weblog to overwrite a victim weblog's Velocity template, whose content is then evaluated when that weblog renders, giving code-in-context execution within the victim's blog. Rated CVSS 7.7 High (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:L), exploitation requires an authenticated author-level account and knowledge or enumeration of valid foreign resource identifiers; no public exploit was identified at time of analysis. Multi-user shared-hosting installations where weblogs are meant to be isolated are affected, while single-user or single-tenant deployments are not meaningfully exposed.
Command injection in the FreePBX Music on Hold (MoH) module lets anyone holding an existing FreePBX administrator account run arbitrary system commands with the privileges of the Asterisk service, because a POST parameter that defines a custom Asterisk application is stored in the database unsanitized and later written verbatim into musiconhold_additional.conf, which Asterisk loads and executes. Deployments running FreePBX prior to 16.0.4 or 17.0.6 with the MoH module enabled and a functioning Asterisk backend are exposed; the vendor has patched the issue in 16.0.4 and 17.0.6. The required admin credentials (PR:L in the published CVSS 4.0 vector, PR:H in the independent CVSS 3.1 assessment) make this a post-authentication privilege-to-code-execution flaw rather than a pre-auth remote takeover, so realistic risk is confined to insider misuse, credential theft, or chaining from another auth bypass; no public exploit code and no confirmed active exploitation (CISA KEV) are identified in the available intelligence.
XML external entity (XXE) injection in Apache Roller 6.1.5 lets an authenticated user who holds entry-editing rights on any weblog force the server to fetch and parse an attacker-influenced trackback response with an XML parser that resolves external entities, disclosing files readable by the Roller process account. The Trackback control is hidden in the standard UI, but its Struts2 action remains directly reachable over HTTP and no non-default server configuration is required, so the practical prerequisite is a valid low-privileged account plus a host the attacker controls to serve the malicious trackback XML (CVSS 3.1 7.7 High, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, scope change reflecting reads outside the application's own data). No public exploit code was identified at the time of analysis, and the vendor-released fix is Apache Roller 6.1.6, which eliminates the outbound trackback response parser.
Incorrect authorization in Canonical LXD 5.0.0 through versions before 5.0.10, 5.21.8, and 6.10 allows an authenticated client with permission to create custom storage volumes in one project to copy and read any custom volume, including its snapshots and configuration, from any other project on the same server. The flaw resides in the custom storage volume creation endpoint, where a crafted request that sets a source volume and source.project but omits source.type bypasses the cross-project authorization check. This affects multi-project LXD deployments only, requires low privileges (PR:L), and yields high confidentiality impact (CVSS 7.7, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N); no public exploit code or confirmed active exploitation was identified at time of analysis.
Hardcoded root SSH access in F&F Filipowski's mH-DEVELOPER smart home module allows anyone who obtains the matching private key to log in as root over the always-running SSH daemon and fully compromise the device. The key is baked into /root/.ssh/authorized_keys, cannot be deleted without remounting the filesystem, and survives a factory reset, so the exposure persists until firmware 3.0.30 is installed. Attack surface is adjacent/local rather than Internet-wide (CVSS 4.0 7.7, AV:A/AC:H) and the private key is not published in the available sources, which is the main practical barrier; no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patch: 3.0.30.
Credential and response tampering in Axios's Node HTTP adapter (lib/adapters/http.js) affects versions 1.15.2 through 1.19.x when a separate, same-process prototype-pollution flaw plants a function on Object.prototype.createConnection: because the adapter supplies request options without an own createConnection property, Node resolves and invokes the inherited function as the socket factory, redirecting the transport to an attacker-controlled endpoint that receives request headers and bodies (including credentials) and returns forged responses while the requested URL still appears legitimate. This is a confused-deputy gadget rather than a self-contained flaw - it is inert without a co-resident pollution primitive that can write a function onto Object.prototype, which is why the vendor CVSS 4.0 vector carries AT:P and why our independent assessment (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) treats exploitation as contingent on that chain. The issue is fixed in Axios 1.20.0; there is confirmed actively exploited (CISA KEV) status absent and no public exploit code identified at time of analysis.
Server-side request forgery in Stringer, a self-hosted RSS reader, allows an authenticated low-privileged user to make the server issue arbitrary HTTP/HTTPS requests to internal network hosts, loopback services, and cloud metadata endpoints such as AWS IMDS at 169.254.169.254. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L, base 7.6) confirms a network-reachable, low-complexity attack requiring only an authenticated account - a barrier that collapses to near-anonymous when self-service signup (Setting::UserSignup) is enabled, since any visitor can register. Impact ranges from internal port and service scanning to theft of cloud IAM credentials when Stringer runs on a cloud instance with an attached role reachable via IMDSv1; there is no public exploit identified at time of analysis and no confirmed CISA KEV active exploitation, though the attack surface is trivial to exercise for anyone holding a valid session.