Heimdall versions prior to 0.17.17 have an improper input validation vulnerability in proxy mode. The software constructs the Forwarded HTTP header by directly inserting the incoming request's Host header without sanitizing commas or semicolons. This allows attackers to inject additional parameters into the Forwarded header, potentially spoofing IP addresses for upstream services. The issue is patched in version 0.17.17.
CVE-2026-55422 is a medium severity cross-site scripting (XSS) vulnerability in the conda-forge.github.io website. The issue arises because two React components render externally-sourced strings directly as HTML using dangerouslySetInnerHTML without sanitization. These strings include raw output from build logs, patch outputs, and tracebacks generated by the conda-forge autotick bot. No patches are publicly available at the time of publication.
A vulnerability in pghoard, a PostgreSQL backup daemon, prior to version 2.7.1 causes sensitive database connection information, including username and password, to be logged at the debug level when using .pgpass. This issue has been fixed in version 2.7.1.
pghoard is a PostgreSQL backup daemon and restore tooling that stores backup data in cloud object stores. Prior to version 2.7.2, an incomplete path traversal fix in pghoard allows an attacker with write access to the backup object storage (such as S3, GCS, or Azure) to execute arbitrary file writes and directory creation outside the designated PostgreSQL data directory (pgdata). When a database administrator executes a restore operation (via pghoard_restore get-basebackup), a maliciously crafted delta backup manifest with path traversal sequences (e.g., ../../../../etc/cron.d/backdoor) will write arbitrary payloads to the host system. This issue has been patched in version 2.7.2.
CVE-2026-57117 is an OS command injection vulnerability in MervinPraison PraisonAI versions 4.6.10 up to but not including 4.6.59. The vulnerability arises because file operation commands are constructed using raw path arguments without proper neutralization, allowing an attacker to inject arbitrary shell commands. This affects local subprocess execution and Docker container execution environments. The issue has been patched in version 4.6.59.
PraisonAI versions from 4.5.115 up to but not including 4.6.61 have a vulnerability where unauthenticated access to A2U event streaming routes is possible when using the documented CLI entrypoint. This occurs because the CLI wrapper does not enforce API key authentication, allowing exposure of sensitive information without authorization. The issue is fixed in version 4.6.61.
CVE-2026-57144 is a high-severity vulnerability in MervinPraison's PraisonAI multi-agent teams system affecting versions from 4.5.110 up to but not including 4.6.61. The issue arises when the SandlockSandbox fallback mechanism does not enforce filesystem or network restrictions if the Landlock module is unavailable, allowing sandboxed code to access unauthorized files and network despite restrictions. This vulnerability has been fixed in version 4.6.61.
CVE-2026-57142 is a high-severity OS command injection vulnerability in MervinPraison PraisonAI versions 4.5.87 up to but not including 4.6.61. The vulnerability arises because the recipe execution policy that blocks dangerous tools only checks tools declared in TEMPLATE.yaml, but the actual workflow execution loads tools from workflow.yaml, allowing untrusted recipes to self-approve critical shell tools without explicit permission. This flaw enables unauthorized execution of shell commands. The issue has been fixed in version 4.6.61.
PraisonAI is a multi-agent teams system. From version 0.1.4 to before version 0.1.5 in praisonai-platform, a workspace member can permanently delete any resource — projects, agents, issues, labels, issue dependencies, and issue-label attachments — created by the workspace owner or other members. All six content DELETE endpoints enforce workspace membership but perform no ownership or role check. A single malicious or compromised member account can wipe an entire workspace's content irreversibly. This issue has been patched in version 0.1.5.
PraisonAI versions from 4.2.1 up to but not including 4.6.59 have an unauthenticated AgentOS FastAPI deployment surface. This allows unauthorized actors to invoke agent.chat endpoints without authentication, potentially exposing sensitive information and enabling unauthorized agent operations. The issue has been patched in version 4.6.59.
CVE-2026-57114 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in MervinPraison PraisonAI versions 4.5.126 up to but not including 4.6.59. The Async Jobs API validates webhook URLs during job request parsing and again when constructing the internal Job object, blocking loopback/private targets at validation time. However, the actual webhook delivery does not re-validate the hostname, allowing an attacker to exploit DNS resolution changes to bypass SSRF protections. This vulnerability has been fixed in version 4.6.59.
PraisonAI is a multi-agent teams system. From version 2.6.0 to before version 4.6.59, PraisonAI's template loader accepts GitHub template URIs with refs, for example github:owner/repo/template@v1.0.0. The resolver stores the user-controlled template path and ref verbatim, and the cache layer later joins those values into ~/.praison/cache/templates/github/<owner>/<repo>/<template>/<ref> without normalizing each segment or checking that the final path remains inside the template cache root. A crafted ref such as ../../../../../../outside-delete-target therefore escapes the cache directory. The first load can write .cache_meta.json outside the cache. If the normal cache hierarchy for the same owner/repo/template has already been created, the same path reaches shutil.rmtree(cache_path) and removes an attacker-selected outside directory before replacing it with cache metadata. This issue has been patched in version 4.6.59.
CVE-2026-56840 is a high-severity cross-site scripting (XSS) vulnerability in MervinPraison's PraisonAI multi-agent teams system. Versions from 4.5.2 up to but not including 4.6.59 are affected. The vulnerability occurs because the HTTPApproval component renders attacker-controlled input directly into the approval dashboard HTML without proper neutralization. This allows an attacker to inject JavaScript that executes in the context of the dashboard, potentially approving malicious tool requests automatically. The issue has been patched in version 4.6.59.
CVE-2026-56838 is an OS command injection vulnerability in MervinPraison's PraisonAI affecting versions from 4.5.87 up to but not including 4.6.59. The issue arises because the streaming execution path recipe.run_stream() bypasses the dangerous tool policy check that is enforced in the normal recipe.run() path. This allows execution of commands that should be denied unless explicitly allowed, potentially leading to high impact on confidentiality, integrity, and availability. The vulnerability has been patched in version 4.6.59.
PraisonAI is a multi-agent teams system. From version 4.6.56 to before version 4.6.59, PraisonAI's LinearBot starts a public webhook listener on 0.0.0.0 and treats LINEAR_WEBHOOK_SECRET as optional. When the secret is absent, startup only logs a warning and _handle_webhook() skips Linear-Signature verification entirely. An unauthenticated network caller who can reach the webhook endpoint can submit a forged Linear-Event: AgentSession request. The forged request is parsed, scheduled for background processing, dispatched to _handle_agent_session(), and passed into BotSessionManager.chat(). The bot then attempts to post the agent response back to Linear under the configured bot token. The PoV is offline and deterministic. It does not contact Linear. It calls the webhook handler directly, monkey-patches the outbound Linear comment path, and proves both sides of the boundary. This issue has been patched in version 4.6.59.
CVE-2026-56836 is an improper authentication vulnerability in MervinPraison PraisonAI affecting versions from 4.5.112 up to but not including 4.6.59. The issue arises because the Recipe HTTP server can be started on a non-localhost interface without authentication, allowing unauthenticated access to the recipe API and potentially the /admin/reload endpoint. This vulnerability has been patched in version 4.6.59.
PraisonAI versions from 3.11.0 up to but not including 4.6.59 contain a missing authorization vulnerability in its Slack bot. The bot enforces user and channel restrictions in the normal Slack message event handler but fails to do so in the Slack app_mention event handler. This allows any Slack user who can mention the bot in a channel with the app installed to trigger configured agents despite restrictions, potentially leading to unauthorized actions. The issue is fixed in version 4.6.59.
PraisonAI versions from 3.8.1 up to but not including 4.6.59 contain a path traversal vulnerability in the Dynamic Context Discovery feature. This flaw allows unauthorized reading of arbitrary files on the host filesystem by manipulating artifact tool arguments. The vulnerability arises because the artifact tools do not verify that the supplied paths are within the configured artifact base directory or created by the configured store. This can expose sensitive files such as .env files, cloud credentials, SSH keys, and source code. The issue is fixed in version 4.6.59.
PraisonAI is a multi-agent teams system. From version 3.8.1 to before version 4.6.59, PraisonAI's Dynamic Context module provides filesystem-backed history and terminal-log storage. The module also exports agent-callable tool factories. Those tools accept run_id and agent_id arguments from the tool caller. The underlying stores join those values into filesystem paths without rejecting absolute paths or .. traversal. Because run_id can be an absolute path and agent_id can contain traversal, a lower-trust prompt/user that can call these tools can read .jsonl and .log files outside the configured Dynamic Context base directory. This issue has been patched in version 4.6.59.
PraisonAI versions from 4.5.2 up to but not including 4.6.59 contain a vulnerability in the Discord approval backend where any user able to post in the configured approval channel can approve a pending high-risk tool call by sending a message classified as approval (e.g., 'yes'). This occurs because the system does not verify that the approval message is a direct reply or otherwise bound to the approval request, allowing unthreaded channel cross-talk. The Slack and Telegram approval backends also lack explicit approver allowlist parameters, but the primary issue is with Discord. This vulnerability has been patched in version 4.6.59.