Vulnerabilities

SIMAC MyPHR 1.1 is vulnerable to an insecure direct object reference (IDOR, CWE-639) because the employee update endpoint does not validate server-side that the authenticated user owns the record being modified. Any authenticated user can send a PUT request to that endpoint with an arbitrary employee identifier and a password value they control, allowing them to change other employees' passwords and take over their accounts. The same flaw also permits enumeration of employee records and retrieval of sensitive personally identifiable information, including private pay bulletins. Organizations running SIMAC MyPHR 1.1 with multiple employee accounts are affected, with a low barrier to exploitation (network-accessible, low privileges, no user interaction per the 8.7 CVSS 4.0 score). No public proof-of-concept, CISA KEV listing, or confirmed in-the-wild exploitation is known at this time.

Do: Contact the vendor for a patched release or an official fix, since no fixed version is stated in the available data. As an interim measure, audit application logs for PUT requests to the employee update endpoint referencing employee IDs other than the requester's own, and reset credentials for any accounts whose passwords may have been changed unexpectedly. Ensure employee accounts use strong, unique passwords to limit the impact of account takeover until server-side ownership validation is fixed.

Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries() permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier could enumerate that entity's entry search results, disclosing attribute values intended to be restricted to privileged users. For Express entities that do not support entry-specific permissions (i.e., supportsEntrySpecificPermissions() returns false), per-entry permission filtering is additionally disabled via EntryList::ignorePermissions(). The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 6.3 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks Daniel Powell for reporting.

ContiNew Admin through 4.1.0 contains an authorization bypass (CWE-639) in its personal message delete endpoint: the server fails to verify that the requesting user owns the targeted message rows. An authenticated low-privileged user can supply arbitrary message identifiers in the IdsReq parameter to delete any other user's messages and announcements, and to purge all recipients' read receipts in a single request. The impact is a loss of message integrity (high integrity per the CVSS 4.0 score of 7.1) rather than confidentiality or availability. Any deployment of ContiNew Admin up to and including 4.1.0 that exposes the messaging module to ordinary authenticated accounts is affected. No public proof-of-concept is known, the issue is not listed in CISA KEV, and no exploitation has been reported.

Do: Upgrade to a ContiNew Admin release newer than 4.1.0 once the vendor publishes a patched build, as no fixed version is confirmed in the current data. As an interim mitigation, restrict the message-delete endpoint to administrative roles and enforce server-side ownership validation of message IDs. Audit application logs for delete requests where the IdsReq identifiers reference messages owned by other users.

TDuck survey form through version 5.3 contains a server-side request forgery and broken-access-control flaw (CWE-918) in its WebhookConfigController, which neither validates the webhook URL supplied nor verifies that the requesting user owns the target form. An authenticated attacker with a low-privilege account can attach a webhook pointing to an arbitrary external or internal address to another user's form. When victims then submit that form, their submission data is pushed to the attacker-controlled URL, enabling data exfiltration, and the server can be made to send requests to internal network addresses. Any organization running a TDuck deployment at version 5.3 or earlier, particularly multi-user deployments, is affected. No public proof-of-concept, CISA KEV listing, or confirmed exploitation has been reported as of this analysis.

Do: Upgrade TDuck to a patched release as soon as the vendor publishes one (no fixed version is specified in the available data), and in the meantime restrict which authenticated roles can create or modify webhooks. Audit existing webhook configurations for entries on forms you did not create, apply egress filtering so the TDuck server cannot reach unexpected internal or external hosts, and remove or disable the webhook feature for untrusted users until the ownership check is fixed.

Guns, an open-source Java admin/management platform, is affected by an improper access control flaw (CWE-862) in its SysNoticeController, where the requiredPermission flag defaults to false and is never overridden by any action method. Any user who can authenticate to the application — even without any role assigned — can therefore invoke the notice endpoints to create, edit, delete, publish, and retract system-wide notices directed at arbitrary users and departments. An attacker gains integrity-level control over the internal notice/messaging system, which could be abused to push fake announcements to an entire organization (e.g., for internal phishing) or to silently remove or alter legitimate communications, though CVSS indicates no confidentiality impact. All deployments running Guns version 8.3.5 or earlier are affected. No public proof-of-concept is known, the issue is not in CISA KEV, and exploitation has not been observed in the wild.

Do: Upgrade Guns to a release newer than 8.3.5 as soon as a patched version is published, since no fix is confirmed in the current data. In the interim, restrict network access to the Guns admin console to trusted users/networks, review accounts able to authenticate without assigned roles, and audit the notice records/logs (sys_notice) for unauthorized creations, edits, deletions, publishes, or retractions. Administrators who build from source should consider enforcing an explicit permission check on the SysNoticeController endpoints.

The Guns administration platform through version 8.3.5 contains a missing-authorization flaw (CWE-862) in SysUserController: the /sysUser/detail and /sysUser/page endpoints lack the requiredPermission configuration, so the platform's permission interceptor skips RBAC validation entirely for these routes. Any remote attacker holding any valid login token — regardless of assigned role — can call these endpoints and retrieve account names, real names, email addresses, phone numbers, last login IPs, and role assignments for every user in the system. This effectively discloses the full user directory of the console, which is valuable for phishing, social engineering, and reconnaissance toward privilege escalation. All deployments of Guns up to and including 8.3.5 are affected, with risk concentrated in systems exposed beyond the local network. No public proof-of-concept, KEV listing, or confirmed in-the-wild exploitation is currently known.

Do: Upgrade Guns to the latest release beyond 8.3.5 as soon as a patched version is available, since the fixed version is not specified in current disclosures. As an interim mitigation, restrict or block access to /sysUser/detail and /sysUser/page at the gateway/WAF for non-administrator roles, or add the missing requiredPermission annotations on those endpoints. Review access logs for calls to these endpoints by low-privilege accounts to detect prior abuse.

A security vulnerability has been detected in SourceCodester Inventory and Monitoring System 1.0. The affected element is an unknown function of the file /index.php. Such manipulation of the argument Username leads to sql injection. The attack may be launched remotely. The exploit has been disclosed publicly and may be used.

A security flaw has been discovered in ChangeWeDer crm up to c07bd4c97141521af6475034bc58523beed51bbd. This issue affects the function index of the file UserController.java of the component top.upstudy.crm.controller.UserController. The manipulation results in missing authorization. The attack can be launched remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was identified in ChangeWeDer crm up to c07bd4c97141521af6475034bc58523beed51bbd. This vulnerability affects the function top.upstudy.crm.utils.LoginUserUtil.releaseUserIdFromCookie. The manipulation leads to improper authentication. The attack can be initiated remotely. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was determined in GPAC 26.07.0. This affects the function rmt_client_handle_ws_frame of the file src/utils/rmt_ws.c of the component WebSocket Handler. Executing a manipulation of the argument payload_size can lead to heap-based buffer overflow. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version abi-16.26 is able to mitigate this issue. This patch is called 37bccbb30cf53a0e1a084cea9a1ce422b3ddfe12. Upgrading the affected component is recommended.

The Ruijie RG-EW3000GX Wi-Fi router running firmware EW_3.0(1)B11P380 contains an OS command injection flaw (CWE-77/CWE-78) in the user_list_note module, which handles the file /etc/rg_config/admin. A remote attacker who already holds administrative privileges manipulates the 'Name' argument, causing injected commands to be executed on the router's operating system; the CVSS 4.0 vector (PR:H) confirms admin-level access is required, so this is not an unauthenticated bug. Successful exploitation yields full command execution on the device, with confidentiality, integrity and availability impacts rated high for both the router and subsequent (downstream) systems, effectively letting an attacker take over the gateway and pivot into the network behind it. Only the RG-EW3000GX on build EW_3.0(1)B11P380 is confirmed affected; other firmware builds or EW-series models are not ruled out but are not documented in the advisory. The advisory states the exploit has been made public and could be used, though no standalone PoC is catalogued in this listing and the flaw is not yet in CISA's Known Exploited Vulnerabilities catalog.

Do: Upgrade the RG-EW3000GX to a firmware release newer than EW_3.0(1)B11P380 as soon as Ruijie publishes a fix (no fixed version is named in the advisory); until then, disable WAN-side/remote administration and restrict the management interface to trusted LAN clients or management allowlists. Rotate administrative credentials and audit the admin/user list configuration (the user_list_note module and /etc/rg_config/admin data) for unauthorized accounts, since that is the component under attack. Because exploitation requires admin-level privileges, exposed management ports combined with weak or reused passwords are the main risk multipliers — prioritize internet-reachable devices.

n Concrete CMS 9.2.0 through 9.5.3, the REST API user creation endpoint (POST /ccm/api/1.0/users, the add() method of concrete/src/Api/Controller/Users.php) did not perform a permission check before creating an account. As a result, any valid OAuth token carrying the users:add scope, including a client_credentials token with no associated user context, could create active, validated user accounts, bypassing email verification and administrator approval. Under default registration settings the created accounts could then edit page content, providing a path to stored cross-site scripting and further compromise. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.

Concrete CMS 9 through 9.5.3 did not confirm that a board InstanceItem submitted to the custom-slot preview endpoint belonged to the board instance the requesting user was authorized to edit, and did not enforce page-view permission before generating page-backed summary content. As a result, an authenticated user holding edit-board-contents permission on a single board instance could submit the identifier of an item belonging to a different board instance and receive summary fields, including the page title and description, of an underlying page the same user was otherwise forbidden to view. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.3 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks Pakung for reporting.

Dell Repository Manager (DRM) versions prior to 3.5.2 ship with incorrect default permissions (CWE-276) on files or components of the application, leaving them writable or usable by accounts that should not have that level of access. A low-privileged attacker who already has some form of remote access to the system running DRM could leverage these misconfigured permissions to elevate privileges, a path reflected in the high-severity CVSS score of 8.5 with network attack vector, high attack complexity, and a changed scope indicating impact beyond the vulnerable component itself. Successful exploitation could yield high confidentiality, integrity, and availability impact on the host and potentially related resources. Organizations are affected if they run affected DRM versions, typically on administrator workstations or management servers used to build and host Dell update repositories. Exploitation status: this flaw is not listed in CISA's KEV catalog, no public proof-of-concept is known, and there are no reports of in-the-wild exploitation.

Do: Upgrade to Dell Repository Manager 3.5.2 or later, which corrects the default permissions. In the meantime, restrict network and local access to hosts running DRM to trusted administrative users, and audit permissions on DRM installation directories, services, and scheduled tasks for overly permissive settings. Since exploitation requires a low-privileged foothold with remote access, prioritize patching hosts reachable from broader networks or shared user environments.

Dell Update Package Framework, versions prior to 26.07.03, contains a Stack-based Buffer Overflow vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this vulnerability, leading to Remote execution.

SSH.NET, a widely used Secure Shell library for .NET, is vulnerable to command injection (CWE-78) in its ScpClient, which places caller-supplied remote paths directly into the scp command executed on the server. When an application passes an attacker-controlled remote path to a shell-based SSH server, shell metacharacters not neutralized by the active IRemotePathTransformation (including the default DoubleQuote transformation) are interpreted by the remote shell, allowing an authenticated attacker to execute arbitrary commands with the privileges of the SSH user. Exploitation requires valid low-privilege SSH credentials, a shell-based server, and a path crafted for that shell's parsing rules, so attack complexity is high; non-shell servers and applications using SftpClient (which avoids the remote shell entirely) are not affected. Any application built on SSH.NET prior to 2026.0.0 that uses ScpClient with attacker-influenced remote paths is affected. No public proof-of-concept or in-the-wild exploitation is known, and the issue is not on CISA's KEV list.

Do: Upgrade to SSH.NET 2026.0.0. Where an immediate upgrade is not possible, switch from ScpClient to SftpClient (which avoids the remote shell entirely) or use RemotePathTransformation.ShellQuote for POSIX shell servers, and audit code for attacker-controlled remote paths passed to ScpClient.

oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, the parseLink function in registry/remote/utils.go accepts an absolute URL from a registry-controlled Link response header without validating its scheme, host, or port. Tags, Referrers, and Repositories pagination operations then issue a GET request to the attacker-selected URL from the victim's network, allowing blind server-side request forgery against internal services. The response body is not returned to the attacker, but timing and error differences can reveal service reachability, and credentials may be attached when the credential store has an entry for the target host. Exploitation requires a victim to perform a pagination-based listing operation against a malicious registry. The maintainer identifies this report as a duplicate of GHSA-3hr5-mjrr-hfjh and states that remediation is consolidated in that earlier advisory. The consolidated issue is fixed in version 2.6.2.

oras-go, a Go library for managing OCI artifacts, contains a path traversal flaw (CWE-22, CWE-59) in its content/file.Store code: when extracting OCI layers annotated with io.deis.oras.content.unpack=true, symlink targets are validated only lexically and writeFile follows a terminal symlink when opening a regular file, allowing a crafted archive to escape the store working directory even when AllowPathTraversalOnWrite is false. Attackers trigger it by getting a user, developer, or CI pipeline to pull an attacker-controlled artifact through the vulnerable extraction path. The result is creation or overwrite of any file writable by the pulling process, which can lead to code execution via overwriting scripts, configuration, or other executable content. Any application, CLI, or service that embeds oras-go prior to version 2.6.2 and unpacks artifacts from untrusted or compromised registries is affected. No public proof-of-concept, CISA KEV listing, or confirmed in-the-wild exploitation is currently known.

Do: Upgrade oras-go to version 2.6.2 and rebuild any tooling that embeds it; check dependency manifests for github.com/opencontainers/oras-go to identify affected builds. Until patched, avoid pulling or unpacking OCI artifacts from untrusted registries, and on systems where such pulls run, audit for unexpected file creation or modification by the pulling process.

Concrete CMS before 9.5.4 failed to sanitize XML and XSLT files submitted through a public Form Block file-upload question, validating uploads by file extension only and storing them as publicly accessible files served inline from the site's own origin. An unauthenticated visitor could upload an XML document containing an xml-stylesheet processing instruction that referenced an attacker-supplied, same-origin XSLT stylesheet; when a victim opened the stored XML directly, the browser applied the stylesheet and executed attacker-controlled JavaScript in the Concrete CMS origin, resulting in stored cross-site scripting. If the victim was an authenticated administrator, the script could act with that administrator's session, and the reporter demonstrated creation of a new user in the Administrators group. Any Concrete CMS deployment running a version before 9.5.4 that exposes a public form with a file-upload question is affected. No public proof-of-concept or in-the-wild exploitation is currently known, and the issue is not listed in CISA KEV.

Do: Upgrade to Concrete CMS 9.5.4 or later. As interim mitigation, remove or restrict file-upload questions in public Form Blocks so XML/XSLT files cannot be uploaded, or serve uploads with attachment disposition and nosniff headers. Review the file manager for unexpected .xml/.xslt uploads and audit the Administrators group for unauthorized users.

Concrete CMS versions below 9.5.4 fail to validate the user timezone value (uTimezone) on write and render it without output encoding on the Dashboard user management page, since Date::getTimezoneDisplayName() passes through any non-IANA value unchanged, enabling stored cross-site scripting. An attacker stores a script payload in the timezone field, and it executes in an administrator's browser when the admin views that user in the Dashboard, running in the admin session. With admin-level script execution, the attacker can read CSRF tokens, create administrator accounts, or change site settings. All versions below 9.5.4 are affected if the concrete.misc.user_timezones setting is enabled (off by default); in 9.5.3 the field is reachable by unauthenticated visitors when public registration is enabled, while in versions below 9.5.3 it is reachable by any authenticated user through the account profile editor. No public proof-of-concept or in-the-wild exploitation is currently known, and the issue is not listed in CISA's KEV.

Do: Upgrade to Concrete CMS 9.5.4 or later. As interim mitigation, disable concrete.misc.user_timezones (and public registration if you rely on the 9.5.3 path), and audit existing user records for suspicious timezone values plus the Dashboard for unexpectedly created administrator accounts or changed site settings.

MikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to 6.6.16 and 7.1.7, the shared SQL layer validates the field key of an orderBy clause but does not validate its direction value before AbstractSqlPlatform.getOrderByExpression concatenates it into an ORDER BY clause. Applications that bind attacker-controlled request data to the direction in em.find(), em.findOne(), em.findAndCount(), QueryBuilder.orderBy(), or QueryBuilderHelper.getQueryOrderFromObject() can permit a raw SQL fragment that performs blind or boolean extraction of data available to the database account. The BaseMySqlPlatform and MsSqlPlatform fallthrough paths have the same behavior, affecting SQLite, PostgreSQL, MySQL, MariaDB, MSSQL, libSQL, and Oracle drivers, while MongoDB is not affected. This issue is fixed in versions 6.6.16 and 7.1.7.

CVE-2026-76420 is an improper authorization flaw (CWE-285) in the internal configuration of the Apache JServ Protocol (AJP) connector in Cisco Secure FMC Software, caused by incorrect initialization of the connector's encryption parameters at boot time. An unauthenticated remote attacker can trigger it by sending crafted packets to the AJP connector, but only while the valid sftunnel connection between the FMC and its managed Cisco Secure FTD devices is down — allowing the attacker to impersonate a peer device. A successful exploit yields command execution as root and full control of the FMC REST APIs, giving complete compromise of the management center and, by extension, the firewall policies it pushes. Any organization running Cisco Secure FMC paired with Secure FTD devices is affected during a tunnel outage; no exploitation in the wild, public PoC, or KEV listing is currently known.

Do: Upgrade Cisco Secure FMC to the fixed release per Cisco's advisory (fixed versions not listed in this data). Until patched, keep the FMC–FTD sftunnel connection healthy and restore any tunnel outages immediately, restrict access to the FMC management interface (including the AJP port, typically TCP 8009) to trusted management networks, and alert on FTD disconnect/tunnel-down events as elevated-risk windows.

Dell Update Package Framework, versions prior to 26.07.03, contains an Improper Link Resolution Before File Access ('Link Following') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Filesystem access for attacker.

Dell Update Package Framework versions prior to 26.07.03 fail to verify a return value before proceeding (CWE-252, Unchecked Return Value), a flaw that a low-privileged local attacker can leverage to gain elevated privileges on the host. The attack requires local access to the machine and user interaction (per the CVSS UI:R metric), consistent with inducing a privileged update process to continue past a failed operation. Because the CVSS scope is changed with high confidentiality, integrity, and availability impact, a successful exploit can compromise resources beyond the vulnerable component's security context. Any Dell client system or administrator workstation running the framework below the fixed version is affected. No public proof-of-concept and no known in-the-wild exploitation have been reported, and the issue is not on the CISA KEV catalog.

Do: Update Dell Update Package Framework to version 26.07.03 or later, obtainable through Dell Command | Update, Dell Update, or the Dell support site, and verify the installed version in the Windows apps list or via the Dell utility. Because exploitation requires local access, prioritize patching shared or multi-user endpoints and remind users not to run untrusted local code while unpatched.

Dell Update Package Framework versions prior to 26.07.03 contain an OS command injection flaw (CWE-78) in which special elements are improperly neutralized before being passed to the operating system. A local, low-privileged attacker can trigger the vulnerability, and the CVSS vector (UI:R) indicates user interaction is required to exploit it. Successful exploitation executes arbitrary OS commands in the context of the update framework, elevating the attacker's privileges with high impact on confidentiality, integrity, and availability. Any Dell client system running the affected framework — typically deployed as part of Dell's client update tooling on consumer and commercial PCs — is affected. No public proof of concept is known and the flaw is not in CISA KEV, so exploitation is not currently observed.

Do: Upgrade Dell Update Package Framework to version 26.07.03 or later, available via Dell's support site or Dell Command | Update / Dell Update channels. Because exploitation requires local low-privileged access and user interaction, prioritize patching shared, multi-user, and kiosk-style endpoints, and verify the installed framework version on managed Dell clients.

node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarms_and_conditions/client_alarm.ts directly assigns unsanitized field names and allows a __proto__.pollutedKey path to modify Object.prototype. Successful exploitation requires an application to expose attacker-controlled event fields to fieldsToJson and may cause denial of service or application logic corruption. This vulnerability is fixed in 2.145.0.

node-opcua, the most widely used open-source OPC UA implementation for Node.js, contains a resource-exhaustion flaw (CWE-400) in which every failed reconnection leaves a TCP socket stranded in FIN-WAIT-2 state, leaking file descriptors and memory until the process or container is killed by the OOM killer. No attacker interaction is required: with the default keepSessionAlive: true setting, a server clock skewed beyond the server's timestamp tolerance (e.g., an industrial PLC roughly 50 minutes ahead of the client) makes the keepalive manager misread the resulting BadInvalidTimestamp fault as a network outage and force a full transport reconnect every keepAliveInterval, while the failed HEL/ACK handshake path calls socket.end() instead of socket.destroy(), so sockets the PLC never closes accumulate indefinitely. At the commonly used 3-second keepAliveInterval this is about 20 leaked sockets per minute (~1,200 per hour), so an attacker who controls or spoofs a skewed, non-responsive OPC UA endpoint — or simple clock misconfiguration — can crash the Node.js client application, gateway, or SCADA data bridge (CVSS 3.1 7.0 High, availability-focused). Any node-opcua client deployment carries the flawed code (confirmed on 2.169.0, the latest release as of April 2026), but only installations communicating with clock-skewed or non-responding servers actually leak; no public proof-of-concept or in-the-wild exploitation is known.

Do: No fixed version is named in the advisory, so watch node-opcua releases beyond 2.169.0 and upgrade as soon as a patch lands; in the interim, either disable keepSessionAlive or lengthen keepAliveInterval, and enforce NTP time synchronization (or raise the server's accepted timestamp tolerance) so client request timestamps stay within the server's window. Monitor FIN-WAIT-2 socket counts on client hosts and apply container file-descriptor/memory limits so any leak surfaces as a bounded, restartable failure rather than a silent OOM crash.

Stanza, Stanford NLP's Python library for tokenization, NER, and parsing, contains a zip path traversal flaw in stanza.resources.common.unzip (stanza/resources/common.py), which passes downloaded model and resource archives directly to zipfile.ZipFile.extractall without validating member paths. The vulnerable extraction path is reachable through the commonly used stanza.download and stanza.install_corenlp functions, so a malicious archive containing parent-directory traversal entries can write files outside the intended model directory. An attacker who can supply or tamper with the archive (for example via a compromised mirror, proxy, or man-in-the-middle download) gains arbitrary file writes with the privileges of the Stanza process, potentially achieving code execution by overwriting shell configuration, SSH authorized_keys, Python packages, or executable scripts. Anyone running Stanza prior to version 1.14.0 is affected. No public proof-of-concept or confirmed exploitation is known, and the flaw is not listed in CISA's KEV catalog.

Do: Upgrade Stanza to version 1.14.0 or later, which validates archive member paths before extraction. Until upgraded, avoid running stanza.download or stanza.install_corenlp from untrusted networks, proxies, or unofficial model mirrors, and review model directories plus shell startup files, ~/.ssh/authorized_keys, site-packages, and scripts for unexpected modifications on hosts where untrusted downloads occurred.

Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and from 2.3.0 until 2.10.3, a malicious or compromised dependency can bypass the earlier CVE-2026-59946 binary-path hardening because Composer validates literal parent-directory segments only during dependency resolution, while the symlink and installed-metadata paths described by the advisory skip that validation. A package can ship an in-package binary symlink that resolves outside its installation directory, or attacker-influenced vendor/composer/installed.json metadata can provide an escaping binary path during a reinstall or regeneration of missing vendor/bin entries. The installed-metadata path is reachable only when the vendor directory was not populated by the same validated install run, such as when it is restored from an untrusted cache, copied from an earlier build stage, carried over from an older Composer run, or writable by a lower-trust build step. Composer can follow the path, change the external target's permissions to make it world-readable and executable, and create a runnable vendor/bin proxy to that external file. The issue does not directly read or transmit data and does not by itself provide remote code execution. This issue is fixed in versions 2.2.30 and 2.10.3.

vLLM is an inference and serving engine for large language models. Prior to 0.24.0, the input_audio handling path for /v1/chat/completions calls AudioMediaIO.load_bytes or AudioMediaIO.load_file without passing VLLM_MAX_AUDIO_DECODE_DURATION_S to the shared audio decoder. An unauthenticated client can therefore submit a small compressed audio input that expands into a very large float32 PCM allocation, bypassing the duration guard already used by /v1/audio/transcriptions and causing an out-of-memory worker crash. Inline data URLs reach this path without being bounded by VLLM_AUDIO_FETCH_TIMEOUT. The issue affects deployments serving an audio-capable model, and authentication changes only the deployment-specific reachability. This issue is fixed in version 0.24.0.

sequoia-openpgp, a widely used Rust implementation of OpenPGP, incorrectly infers key capabilities for older certificates that lack a key flags subpacket, creating a discrepancy between the key flags a verifier assumes and what the certificate actually declares. An attacker who controls such a legacy-style certificate can leverage this confusion to bypass the back-signature check, which normally proves that a primary key authorized a signing subkey. As a result, an attacker can bind an arbitrary subkey to their own certificate and produce signatures that verifiers accept as legitimate, compromising the cryptographic integrity of signature verification. Any software or service that uses sequoia-openpgp to verify attacker-supplied OpenPGP certificates and signatures is affected, including downstream tooling such as RPM package signature verification in RPM-based Linux distributions. No public proof-of-concept is known, the issue is not in CISA's KEV catalog, and no in-the-wild exploitation has been reported.

Do: Track the Sequoia PGP security advisory (CVE-2026-42784) and upgrade sequoia-openpgp to the patched release as soon as one is published; RPM-based distribution users should apply package-manager security updates as vendors ship rebuilt components. Until patched, exercise caution when verifying certificates that lack a key flags subpacket, and treat subkey-binding and back-signature validation results from unpatched sequoia-openpgp versions as untrusted. Audit your dependency tree (cargo) to determine whether sequoia-openpgp is present in verification-critical paths.

CVE-2026-20331 tracks multiple internally discovered vulnerabilities in Cisco Secure Adaptive Security Appliance (ASA) Software, Cisco Secure Firewall Threat Defense (FTD) Software, and Cisco Secure Firewall Management Center (FMC) Software, all classified as failures of protection mechanisms (CWE-693) and addressed through a software hardening release. Cisco has not published detailed technical specifics, but the CVSS 3.1 vector indicates an attacker needs only adjacent network access, with no privileges or user interaction, and that impact crosses security boundaries (scope changed) with high confidentiality and integrity effects plus low availability impact. This is consistent with a bypass of security controls on a firewall/VPN platform, where successful exploitation could let an attacker defeat protections the appliance is meant to enforce. Any organization running affected ASA, FTD, or FMC software is in scope, and FMC operators should note that the management center can propagate exposure across large fleets of managed FTD devices. As of now there is no known exploitation, no public proof of concept, and the issue is not on the CISA KEV list.

Do: Consult Cisco's advisory for the hardening release and upgrade ASA, FTD, and FMC to the fixed releases it specifies for your software train, since the bundle covers multiple internally found issues. In the interim, limit adjacent-network reachability to device management interfaces and review VPN and management-plane access controls. Because the flaws were found internally and details are sparse, monitor Cisco PSIRT for updated indicators and remediation guidance.

Cisco Identity Services Engine (ISE) contains an insecure deserialization flaw (CWE-502) in its web-based management interface, caused by unsafe handling of a user-supplied Java byte stream. An attacker who already holds at least low-privileged administrative credentials can send a crafted serialized Java object to the management interface to trigger the flaw. Successful exploitation yields arbitrary code execution on the underlying operating system and privilege escalation to root; in single-node deployments it can also render the ISE node unavailable, blocking network access for endpoints that have not yet authenticated. All Cisco ISE deployments whose management interface is reachable by an attacker with administrative credentials are affected, though specific version ranges were not provided in the source data. As of now the flaw is not listed in CISA's KEV catalog and no public proof-of-concept is known.

Do: Upgrade affected ISE nodes to the fixed release identified in Cisco's advisory. Until patched, restrict access to the ISE web management interface to trusted administrative networks and audit which accounts hold low-privileged administrative credentials. Operators of single-node deployments should prioritize patching since exploitation would cause a full denial of network access for unauthenticated endpoints.

Cisco ISE and ISE-PIC contain a command injection vulnerability (CWE-78) in their REST API, caused by improper validation of user-supplied input. An authenticated, remote attacker who already holds valid administrative credentials can send crafted commands to the web-based management interface to trigger the flaw. Successful exploitation allows arbitrary code execution on the underlying operating system with elevation to root privileges. In single-node deployments, exploitation can also render the ISE node unavailable, denying network access to endpoints that have not yet authenticated. As of the latest data, the flaw is not listed in CISA's KEV catalog and no public proof-of-concept is known.

Do: Upgrade ISE and ISE-PIC to the fixed releases identified in the Cisco Security Advisory (version numbers not provided in available data). Until patched, restrict access to the management and REST API interfaces to trusted admin networks, audit and rotate privileged administrative credentials (since valid admin creds are required for exploitation), and enable MFA for ISE administrators. Organizations running single-node deployments should prioritize patching and maintain backups, as exploitation could take the sole node offline and block new endpoint authentication.

A command injection flaw (CWE-78) exists in the diagnostic tools of Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC), caused by improper validation of user-supplied input. An authenticated remote attacker who already holds valid administrative credentials can send crafted commands through the web-based management interface to inject commands into the underlying operating system. A successful exploit yields arbitrary code execution and elevation to root on the affected node. Organizations running ISE or ISE-PIC are affected; in single-node deployments, exploitation can render the ISE node unavailable, blocking endpoints that have not yet authenticated from accessing the network. No public proof-of-concept is known and the flaw is not listed in CISA's KEV, so exploitation has not been confirmed.

Do: Upgrade ISE and ISE-PIC nodes to the fixed releases identified in the Cisco security advisory for CVE-2026-20305, as no workaround is described in the available data. Because valid admin credentials are required, restrict access to the web-based management interface, review and rotate administrative credentials, and audit admin activity logs for unexpected diagnostic-tool commands. Treat single-node deployments as higher risk given the potential denial-of-service impact on network access.

CVE-2026-20234 is a set of insufficiently protected credential issues (CWE-522) in Cisco Identity Services Engine (ISE) and the Cisco ISE Passive Identity Connector (ISE-PIC), discovered during Cisco's internal security review and fixed in a software hardening release. An attacker with low-privileged network access to the device can exploit the flaw without user interaction; the CVSS scope change (S:C) with high confidentiality, integrity, and availability impacts indicates the attacker can cross a security boundary and gain far more than their initial low-privilege foothold, plausibly by recovering protected credentials stored or managed by ISE. Any organization running Cisco ISE or ISE-PIC is in scope, since these platforms centrally handle network access control and identity data for the enterprise. Exploitation status is currently clean: the issue is not in CISA's KEV catalog and no public proof-of-concept is known.

Do: Apply Cisco's software hardening release for ISE and ISE-PIC as soon as practical, checking the official Cisco advisory for the exact fixed versions for your release train. Because the flaw centers on insufficiently protected credentials, rotate credentials that ISE stores or manages (including administrative and internal identity store passwords) after patching, and restrict low-privileged user access to the appliance. Review ISE audit and authentication logs for signs that a low-privilege account was used to access protected configuration or credential data.

A heap-use-after-free vulnerability exists in H5T__conv_f_f() in src/H5Tconv.c in HDF5 before 1.14.2. When converting a compound datatype containing floating-point members during a dataset read, a temporary buffer allocated with calloc() is freed and subsequently read from within the same conversion routine. An attacker who can supply a crafted HDF5 file containing a specially constructed compound datatype can trigger the use-after-free when the file is parsed by an application that reads the affected dataset, such as h5dump. This can result in a crash and, depending on heap layout and allocator behavior, may be exploitable for further memory corruption up to remote code execution.

Control iD iDSecure, an on-premises access control management platform, versions prior to 4.8.3.0 contain an unauthenticated denial-of-service flaw (CWE-476). An attacker can send a simple network request to the /api/dguardintegration/dguardVersion endpoint, which dereferences the DGuard integration login state without checking whether it is set, triggering an unhandled null reference exception. Because the exception is raised inside an asynchronous method that returns void, it is never observed by a caller and can crash the entire iDSecure process. Any organization running an affected version is exposed, with the greatest risk to instances whose web API is reachable by untrusted networks. No public proof-of-concept is known, the flaw is not in CISA KEV, and no in-the-wild exploitation has been reported.

Do: Upgrade iDSecure to version 4.8.3.0 or later, which resolves the flaw. If upgrading is not immediately possible, restrict network access to the iDSecure server so that only trusted hosts can reach its web API, and monitor for unexplained iDSecure process restarts or crashes, which would indicate attempted exploitation.

Control iD iDSecure, an access-control management server, exposes the /api/license/restartService endpoint without requiring authentication in versions prior to 4.8.3.0 (CWE-306, missing authentication for a critical function). When called, this endpoint runs an internal routine that terminates the iDSecure service process and relaunches it via a generated batch script. An unauthenticated remote attacker can invoke the endpoint repeatedly to trap the service in a continuous restart cycle, leaving the server unavailable and disrupting access-control management. Any organization running iDSecure before 4.8.3.0 is affected, with risk highest where the server's API is reachable from untrusted networks rather than only the local LAN. No public proof-of-concept is known, the flaw is not listed in CISA KEV, and no exploitation has been reported to date.

Do: Upgrade iDSecure to version 4.8.3.0 or later, which restores authentication on the restartService endpoint. Until patched, restrict network access to the iDSecure server so /api/license/* is reachable only from trusted management hosts, and check firewall/proxy logs for repeated unauthenticated requests to /api/license/restartService, which would indicate restart-loop attempts.

A flaw was found in flightctl. The configureRepoHTTPSClient() function in the device-render worker builds a per-repository tls.Config (which may include InsecureSkipVerify, a custom CA bundle, or tenant-supplied mTLS client certificates) and installs it into go-git's process-global client.Protocols map via gitclient.InstallProtocol("https", ...). Because the worker renders devices for multiple organizations concurrently from a shared goroutine pool, whichever tenant's repository configuration is written last wins for all in-flight git.Clone calls. This race condition can cause one tenant's TLS settings, including InsecureSkipVerify or mTLS client credentials, to leak into another tenant's git operations.

CVE-2026-92397 is an operating system command injection vulnerability in the cc_set function of unifyframe-sgi.elf, part of the configChange component of the Ruijie RG-EW3000GX wireless router running firmware EW_3.0(1)B11P380. An attacker sends a crafted request in which the data.url argument is concatenated into a shell command without sanitization, allowing arbitrary OS commands to be executed remotely; per the CVSS 4.0 vector (PR:H), the attack requires an authenticated high-privilege (administrator-level) session but no user interaction. Successful exploitation yields full command execution on the device (confidentiality, integrity and availability impacts all rated High), enabling router takeover, traffic manipulation, and pivoting into the connected LAN. Only RG-EW3000GX units running the affected EW_3.0(1)B11P380 firmware are implicated, a product line typically deployed in SOHO and small-business Wi-Fi networks. The flaw is not listed in CISA KEV and no standalone public PoC has been catalogued, although the source advisory states an exploit has been publicly disclosed; no confirmed in-the-wild exploitation is documented.

Do: Check the router's firmware version in the admin console and, if it is EW_3.0(1)B11P380, apply the latest EW 3.0 firmware from Ruijie's official support channel (no fixed version is specified in the available data, so confirm the patched release with the vendor). Minimize exposure by disabling remote/WAN management, restricting the management interface to trusted networks, and placing the device behind a firewall where possible. Monitor for unexpected requests to the configChange/unifyframe-sgi.elf handler containing shell metacharacters in the data.url parameter, and rotate administrator credentials on any device that may have been accessed.

A vulnerability has been found in SourceCodester Online Food Ordering System 1.0. The affected element is an unknown function of the file /admin/update_category.php of the component Category Update. The manipulation leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Sentry Seer, Sentry's AI-powered debugging/fix agent, suffers from a multi-stage trust-boundary violation in which unauthenticated, attacker-controlled telemetry (Sentry events) is treated as trusted input and ultimately becomes code executed by the agent in a privileged automation environment. An external attacker triggers the flaw by submitting fabricated error events to a victim's Sentry organization without needing access to the victim's account, source repository, or infrastructure; when Seer processes the crafted events, the embedded content is translated into executed automation. Successful exploitation gives the attacker code execution within Seer's privileged environment, with whatever access that automation context carries. Any Sentry customer organization that has Seer enabled and accepts externally submitted event data is affected. As of this writing the flaw has no CVSS score, is not in CISA KEV, has no known public proof-of-concept, and there are no confirmed reports of in-the-wild exploitation (CERT/CC advisory VU#212479).

Do: Track CERT/CC VU#212479 and Sentry's advisories for the patched release and apply it promptly, since Seer is a SaaS feature and remediation may arrive server-side or as a configuration change. Until patched, consider disabling Seer or excluding projects that receive unauthenticated SDK events (e.g., public-facing web/mobile apps) from automated analysis, and lock down event ingestion (DSN handling, allowlisted origins). Review Seer automation logs and any agent-executed actions for unexpected code execution or anomalous event sources.

Dell ObjectScale, Dell's Kubernetes-based software-defined object storage platform, versions prior to 4.4.0.0 contain an incorrect permission assignment for a critical OS resource (CWE-732). The flaw can be triggered by an attacker who already holds high privileges and has remote access to the system, by acting on improperly protected OS resources. Successful exploitation primarily results in denial of service (high availability impact, with a minor integrity impact per the CVSS vector), which could disrupt object storage services. Only organizations running affected ObjectScale releases are exposed, and the attacker must already be highly privileged, limiting the realistic attack surface. No public proof-of-concept is known, the issue is not in CISA's KEV catalog, and no in-the-wild exploitation has been reported.

Do: Upgrade Dell ObjectScale to version 4.4.0.0 or later. Restrict remote access to high-privileged accounts and management interfaces (VPN, allow-listing, MFA), since exploitation requires high privileges, and audit administrative accounts for unusual activity. Monitor for storage service disruptions or restarts that could indicate exploitation.

Dell ObjectScale, Dell's Kubernetes-based enterprise object storage platform, contains a deserialization of untrusted data flaw (CWE-502) in all versions prior to 4.4.0.0. An unauthenticated attacker with remote network access to a vulnerable deployment can supply maliciously crafted serialized data to trigger the flaw, requiring no credentials or user interaction. Successful exploitation results in remote code execution, and the CVSS scope change (S:C) with high confidentiality, integrity, and availability impacts indicates a compromise could extend beyond the vulnerable component to the wider cluster or host. All Dell ObjectScale deployments running versions before 4.4.0.0 are affected. There is currently no evidence of in-the-wild exploitation, no known public proof-of-concept, and the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog.

Do: Upgrade Dell ObjectScale to version 4.4.0.0 or later per Dell's security advisory. Until patched, restrict network access to ObjectScale management and service interfaces to trusted networks only, since the flaw is exploitable remotely without authentication. Review Dell's advisory for related ObjectScale fixes shipped in the same release and monitor for updates.

djust, a Python (pip) LiveView framework, left its Server-Sent-Events transport open to cross-site request forgery: the SSE client-to-server POST endpoints were decorated @csrf_exempt and the SSE GET stream endpoint performed no Origin check. An attacker hosts a web page that forces a victim's browser to GET the stream URL (which creates and mounts a LiveView using the victim's cookies) and then POSTs to the message endpoint with credentials included, using a client-chosen session_id and a text/plain JSON body that qualifies as a CORS simple request with no preflight. This lets the attacker fire state-changing, victim-authenticated event handlers on the server, with high confidentiality and integrity impact but no availability impact (CVSS 3.1: 8.1). Any djust application that exposes the SSE transport to authenticated users is affected. No public proof-of-concept or in-the-wild exploitation is known, and the flaw is not listed in CISA KEV.

Do: Upgrade to djust 1.0.7, which validates the request Origin against ALLOWED_HOSTS on all three SSE endpoints (rejecting cross-origin requests with 403) and requires Content-Type: application/json on POST endpoints (415 otherwise). If upgrading is not immediately possible, disable the SSE transport or place a reverse proxy in front of the SSE endpoints that enforces an Origin allowlist. Audit any djust application that uses SSE with cookie-authenticated LiveViews, since only those deployments are exposed to this flaw.

Dell ECS and Dell ObjectScale contain an improper privilege management vulnerability (CWE-269) that allows an attacker who already has high privileges and local access to the system to elevate those privileges. Because the CVSS vector requires local access and high existing privileges, exploitation is limited to users or compromised accounts that already have substantial control over the storage platform, but a successful attack yields full high-impact access (high confidentiality, integrity, and availability impact). Affected products are Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.4.0.0; ObjectScale is Dell's Kubernetes-based successor to the ECS object storage platform, so both product lines are deployed primarily in enterprise data centers. There are no reports of in-the-wild exploitation, the flaw is not in CISA KEV, and no public proof-of-concept is known.

Do: Upgrade Dell ObjectScale to version 4.4.0.0 or later and upgrade ECS to a release beyond 3.8.1.7 as specified in Dell's security advisory. Because exploitation requires local access with high privileges, restrict and audit management-plane and SSH access to ECS/ObjectScale nodes, limit the number of high-privileged storage accounts, and monitor privileged activity for anomalies. Follow Dell's advisory (CNA: Dell/emc security team) for exact fixed builds and any interim mitigations.

A flaw was found in the first-broker-login flow of the keycloak-services component. This component handles the initial authentication and account linking when a user logs in via an external identity provider. The issue allows an attacker to register a matching username on an external provider to trigger a collision in Keycloak, which results in the legitimate user being locked out of their account.