CVE-2026-54674 is an OS command injection vulnerability in FreePBX's security-reporting component affecting versions prior to 16.0.39 and 17.0.7. Authenticated users with access to the User Control Panel (UCP) can execute arbitrary commands as the webserver user due to insufficient sanitization of URL parameters. This vulnerability requires authenticated UCP access, which is more commonly granted to less-privileged users than to administrators. The issue has been addressed in FreePBX versions 16.0.39 and 17.0.7.
FreePBX versions prior to 16.0.4 and 17.0.6 contain a critical OS command injection vulnerability in the Music on Hold (MoH) module. Authenticated attackers with administrator privileges can inject arbitrary system commands via a POST parameter that defines a custom Asterisk application. This parameter is stored without sanitization and later written directly to the musiconhold_additional.conf configuration file, which Asterisk executes with its service privileges. The vulnerability has been patched in versions 16.0.4 and 17.0.6.
A flaw has been found in ag-ui-protocol ag-ui up to 2026-09-07. This vulnerability affects the function FilterToolCallsMiddleware of the file sdks/typescript/packages/client/src/middleware/filter-tool-calls.ts of the component Middleware. Executing a manipulation can lead to incomplete cleanup. The attack may be launched remotely. Upgrading to version 2026-09-08 is able to resolve this issue. This patch is called c346119fe870b70f5c19738ee5119f3e1456e59d. It is suggested to upgrade the affected component.
CVE-2026-88816 is a high-severity vulnerability in Perl's DBI module versions before 1.654. It involves a type confusion issue where numeric values are incorrectly treated as strings in the FetchHashKeyName attribute. This leads to a segmentation fault when fetchrow_hashref attempts to use an invalid pointer as a hash key name. The flaw can be triggered by setting FetchHashKeyName to a numeric value such as an integer or floating-point number.
CVE-2026-85644 is a type confusion vulnerability in XS::Parse::Infix versions 0.40 through 0.49 for Perl. The vulnerability arises because the wrapper function incorrectly checks argument types, leading to dereferencing invalid memory and causing a segmentation fault. This can be triggered by supplying crafted input, such as a number treated as an array reference, potentially allowing an attacker to control memory dereferencing.
CVE-2026-101099 is a medium severity vulnerability in the ag-ui component of the ag-ui-protocol project, specifically affecting version 2026-09-23. The issue involves improper handling of exceptional conditions in the SseParser.kt file of the Kotlin Community SDK. This vulnerability can be triggered remotely without user interaction and requires low privileges to exploit. A fix has been developed but is pending acceptance in a pull request.
A security vulnerability has been detected in ag-ui-protocol ag-ui up to 2026-09-23. Affected by this issue is the function readAllBytes of the file JdkAgentHttpHandler.java of the component HTTP Handler. Such manipulation leads to resource consumption. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
An OS command injection vulnerability in the WatchGuard AP internal API service allows an attacker with network access to the AP to execute arbitrary shell commands on the underlying operating system.
An OS command injection vulnerability in the WatchGuard AP diagnostic CLI allows an authenticated administrator to execute arbitrary operating system commands by supplying crafted input.
An improper access control vulnerability in an internal API service on WatchGuard Access Points allows an unauthenticated attacker with network access to the AP to obtain a valid API session.
A security vulnerability has been detected in PMWeb v7.x/v8.x/v2025.x. Impacted is an unknown function in the library encryptionhelper.dll. Such manipulation leads to information disclosure. The attack may be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.
Payy is an Ethereum L2 zk-rollup for privacy preserving and regulatory compliant transactions. Prior to version 1.3.0, agg_agg forwards the compacted message stream from its inner proofs into a public messages: [Field; 1000] array, but it never checks that the unused tail of the outer array is zero. A registered prover can build a valid agg_final proof for an approved rollup block while inserting an extra burn message after the real messages. RollupV1.verifyRollup() then parses that public input as a normal burn and transfers USDC from the rollup contract to the attacker. This is a severe circuit soundness failure: the proof system accepts a public statement whose messages array is not fully derived from the verified inner proofs. On the current deployment, verifyRollup() is restricted to the existing allowlisted prover, so a fresh public caller cannot submit the invalid proof directly. That gate limits who can reach L1 today; it does not make the circuit statement sound. The issue becomes permissionless under the prover model described in the Payy whitepaper. Section 3.3.2 states: "To join as a prover, the prover is required to submit a small stake", and Section 3.3.1 states that if a prover fails to submit, "other nodes can submit the block proof instead." In that model, an attacker only needs to become a registered prover and use public validator approval data for an already approved block. This issue has been patched in version 1.3.0.
fast-mcp-telegram versions prior to 30.1 contain a server-side request forgery (SSRF) vulnerability in the send_message and send_message_to_phone MCP tools. These tools accept files as lists of HTTP(S) URLs, which the server downloads and attaches to outgoing Telegram messages. The URL validation relies on a denylist that checks only the hostname string without DNS resolution, allowing attackers to bypass restrictions and cause the server to fetch resources from internal or private network addresses. This results in a full-read SSRF that can exfiltrate data by returning the fetched content as a Telegram file attachment. The vulnerability is patched in version 30.1.
Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS, PDU and SCD hardware. Prior to commits 658b24e and 1aa31d1, the GitHub Actions script used to prepare NUT tarballs and update GitHub Checks statuses and PR comments about it was mis-structured in terms of mixing code running with higher privileges (single-use token generated with write permissions) and untrusted inputs (PR source branch). A malicious PR run from a fork could extract the GITHUB_TOKEN value. It could potentially be abused while it was valid (while the GHA job ran) to manipulate Git repository contents, commit checks/statuses, or issue/PR comments, according to permissions it was issued with. This issue has been patched via commits 658b24e and 1aa31d1.
CVE-2026-101082 is a path traversal vulnerability in PMWeb affecting versions 7.x, 8.x, and 2025.x. The issue involves improper handling of the FullFileName/FileName argument in the file downloader.aspx component, allowing remote attackers to manipulate file paths. Exploit code is publicly available. The vendor has not responded to disclosure requests, and no patch or remediation guidance is currently known. The vulnerability has a medium severity rating with a CVSS score of 6.9.
A security flaw has been discovered in D-Link DI-8400 16.07. This vulnerability affects the function menu_nat_more_asp of the file menu_nat_more.asp of the component Web Administration Service. The manipulation of the argument opt results in stack-based buffer overflow. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.
A sender spoofing vulnerability in Proton Mail's web interface allows an attacker to forge the sender identity using display-name homographs that visually mimic legitimate email addresses. The issue exploits the font rendering of certain characters (e.g., capital 'I' vs lowercase 'l') in the default system font, making look-alike domains indistinguishable from real ones. Proton Mail does not display authentication failure warnings for domains without DMARC records, allowing spoofed messages to appear clean and trustworthy in the inbox. Despite reporting and a bounty awarded in early 2025, Proton has not fixed the issue as of September 2026.
CVE-2026-88815 is a type confusion vulnerability in Perl's DBI module versions before 1.654. It occurs when numeric values are incorrectly treated as strings during SQL type casting, leading to a segmentation fault. This flaw arises because the function sql_type_cast_svpv passes a string pointer without proper stringification, causing invalid memory access. The vulnerability can be triggered by calling sql_type_cast with a numeric value and SQL_NUMERIC type.
A vulnerability was identified in Tencent AI-Infra-Guard up to 4.5.2/4.6.2. This affects the function startsWith of the file skill_scan/tools/dir/dir_actions.py of the component File Access. The manipulation leads to path traversal. The attack needs to be performed locally. The exploit is publicly available and might be used. Upgrading to version 4.6.0 is able to mitigate this issue. The identifier of the patch is ac0384edc9dbea3b226edefcf50613bd8509134f. You should upgrade the affected component.