1050 matches found
CVE-2026-100865
The Heym workflow automation platform, in versions before 0.0.53 , is vulnerable to Remote Code Execution (RCE) due to insufficient sandboxing when evaluating workflow condition expressions using Python's eval() function in the workflow executor service. Authenticated users can exploit this by ed...
CVE-2026-100865 Heym before 0.0.53 Remote Code Execution via eval() Sandbox Escape
Heym before 0.0.53 evaluates workflow condition expressions using Python's eval with insufficient sandboxing in the workflow executor service. Authenticated users can edit workflow condition nodes or import malicious templates to execute arbitrary Python and OS commands as the backend process use...
EUVD-2026-87830
Heym before 0.0.53 evaluates workflow condition expressions using Python's eval with insufficient sandboxing in the workflow executor service. Authenticated users can edit workflow condition nodes or import malicious templates to execute arbitrary Python and OS commands as the backend process use...
CVE-2026-100865 Heym before 0.0.53 Remote Code Execution via eval() Sandbox Escape
Heym before 0.0.53 evaluates workflow condition expressions using Python's eval with insufficient sandboxing in the workflow executor service. Authenticated users can edit workflow condition nodes or import malicious templates to execute arbitrary Python and OS commands as the backend process use...
CVE-2026-100862
The workflow automation platform heym versions prior to 0.0.91 contains multiple plaintext storage vulnerabilities. The application fails to encrypt several sensitive secrets, including webhook header-auth values , MCP API keys , portal session tokens , workflow execution JWTs , and Discord inter...
CVE-2026-100862 heym before 0.0.91 Multiple Secrets Plaintext Storage
heym, a workflow automation platform, stores and returns multiple capability secrets in plaintext in versions prior to 0.0.91. Affected secrets include webhook header-auth values returned in cleartext by GET /api/workflows/id and persisted unsanitized into execution history, MCP API keys stored a...
CVE-2026-100862 heym before 0.0.91 Multiple Secrets Plaintext Storage
heym, a workflow automation platform, stores and returns multiple capability secrets in plaintext in versions prior to 0.0.91. Affected secrets include webhook header-auth values returned in cleartext by GET /api/workflows/id and persisted unsanitized into execution history, MCP API keys stored a...
CVE-2025-71422
The Contrast Kubernetes runtime for confidential containers is vulnerable in versions before 1.12.1 . A malicious host can supply a crafted LUKS2 volume to a pod VM. Because LUKS2 volume metadata is not authenticated and older cryptsetup versions (prior to 2.8.1) accept null keyslot encryption al...
PT-2026-99482
Name of the Vulnerable Software and Affected Versions heym versions prior to 0.0.91 Description This workflow automation platform stores and returns multiple capability secrets in plaintext. Affected secrets include webhook header-auth values, which are returned in cleartext by the 'GET...
CVE-2026-100862: Cleartext Storage of Sensitive Information
heym, a workflow automation platform, stores and returns multiple capability secrets in plaintext in versions prior to 0.0.91. Affected secrets include webhook header-auth values returned in cleartext by GET /api/workflows/id and persisted unsanitized into execution history, MCP API keys stored a...
PT-2026-99485
Name of the Vulnerable Software and Affected Versions Heym versions prior to 0.0.53 Description Multiple security issues exist in the software. The workflow condition evaluator uses the Python eval function without an effective sandbox, enabling users who can edit workflow branch/condition nodes ...
GHSA-G5XV-MHGM-V5F6 MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
Summary When OAuth tokens are saved, MCP Atlassian always writes a plaintext fallback copy under /.mcp-atlassian/oauth-.json. The fallback file is created with the process default umask rather than restrictive permissions. In this environment the file was created as mode 0664, exposing access and...
MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
Summary When OAuth tokens are saved, MCP Atlassian always writes a plaintext fallback copy under /.mcp-atlassian/oauth-.json. The fallback file is created with the process default umask rather than restrictive permissions. In this environment the file was created as mode 0664, exposing access and...
CVE-2026-77250 MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
MCP Atlassian is a Model Context Protocol MCP server for Atlassian products Confluence and Jira. Prior to 0.22.0, OAuthConfig writes a plaintext fallback file containing access and refresh tokens under the user's .mcp-atlassian directory using process-default permissions. On systems with a...
CVE-2026-77250 MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
MCP Atlassian is a Model Context Protocol MCP server for Atlassian products Confluence and Jira. Prior to 0.22.0, OAuthConfig writes a plaintext fallback file containing access and refresh tokens under the user's .mcp-atlassian directory using process-default permissions. On systems with a...
CVE-2026-77250 MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
MCP Atlassian is a Model Context Protocol MCP server for Atlassian products Confluence and Jira. Prior to 0.22.0, OAuthConfig writes a plaintext fallback file containing access and refresh tokens under the user's .mcp-atlassian directory using process-default permissions. On systems with a...
CVE-2026-86555
The ZTE SmartLife application has a hardcoded key. The key used to decrypt account server information is stored in plaintext in the code. Once the key is obtained, the server information can be decrypted, thus exposing it...
CVE-2026-86555
The ZTE SmartLife mobile application contains a hardcoded key used to decrypt account server information. The key is stored in plaintext within the application code, so an attacker with access to the binary can extract it and decrypt the protected server configuration data. The CVSS v3.1 score is...
CVE-2026-86555 Hardcoded Key Vulnerability in ZTE SmartLife APP
The ZTE SmartLife application has a hardcoded key. The key used to decrypt account server information is stored in plaintext in the code. Once the key is obtained, the server information can be decrypted, thus exposing it...
CVE-2026-86555 Hardcoded Key Vulnerability in ZTE SmartLife APP
The ZTE SmartLife application has a hardcoded key. The key used to decrypt account server information is stored in plaintext in the code. Once the key is obtained, the server information can be decrypted, thus exposing it...