CWE-526
Cleartext Storage of Sensitive Information in an Environment Variable
Monthly
Authenticated users of Letta through 0.16.8 can read server secrets when the LocalSandbox tool backend is used, because tool subprocesses inherit the server process environment; calling POST /v1/tools/run or running a custom tool can expose LETTA_PG_URI, POSTGRES_PASSWORD, and provider API keys. In multi-tenant deployments sharing one Postgres instance, those leaked database credentials can be used to reach other tenants' data, although single-tenant or properly isolated sandbox deployments are much less exposed. Publicly available exploit code exists, but the provided data does not confirm active exploitation (no CISA KEV entry), and exploitation requires an authenticated account with permission to execute tools.
python-utcp CLI subprocess environment passes all process-level secrets to every tool call. When chained with CVE-2026-45369 command injection, remote authenticated attackers with low-privilege LLM tool access can exfiltrate AWS credentials, API keys, database URLs, and other environment variables in a single HTTP request. Patch available in version 1.1.2 (NVD references 1.1.3 as fixed version). GitHub security advisory confirms proof-of-concept demonstrating credential theft via env dump to attacker-controlled endpoint.
Environment variable exfiltration in PraisonAIAgents versions prior to 1.5.128 allows unauthenticated remote attackers to steal secrets (database credentials, API keys, cloud access keys) through shell_tools.py execute_command function. The vulnerability leverages deceptive command approval where unexpanded $VAR references shown to human reviewers differ from executed commands containing expanded environment variable values. Requires user interaction. No public exploit identified at time of analysis.
Information exposure in mini-swe-agent versions 1.10.0 through 2.4.6 allows remote attackers to read sensitive environment variables, such as API keys, from the host system when the BubblewrapEnvironment sandbox is used. The sandbox fails to clear the environment (missing --clearenv), so sandboxed commands inherit the host environment. An attacker can leverage prompt injection in processed task content to direct the agent to exfiltrate these secrets over the network. Exploitation requires the use of BubblewrapEnvironment, presence of sensitive variables in the environment, and attacker-controlled task content; it is a moderate, context-dependent risk, and no public exploit has been identified at the time of analysis.
Environment variable exposure in Renovate (versions 42.68.1 through 42.96.3 and 43.0.0 through 43.4.4) leaks the full process environment - including privileged credentials - into every child process spawned during dependency update operations. The regression was introduced inadvertently on 2025-12-30 when Renovate migrated to the `execa` library, whose default behavior extends rather than replaces environment variables, silently bypassing Renovate's intended allowlist filtering. Both insider attackers (with repository write access) and outsider attackers (via supply-chain compromise of a processed dependency) can embed credential-harvesting code in scripts that Renovate executes, exfiltrating GitHub tokens, registry credentials, and cloud IAM keys accessible to the deployment. No public exploit has been identified at time of analysis, but the vendor explicitly recommends rotating all credentials that affected Renovate instances had access to.
Cleartext token exposure in Elastic Cloud on Kubernetes allows any principal with namespace workload-spec read access to retrieve live Elasticsearch service account credentials. Affected deployments are those running Fleet Server resources configured to authenticate to Elasticsearch via service account tokens - ECK writes the token directly into the generated Pod specification in cleartext rather than referencing the Kubernetes Secret where other credentials are stored, bypassing an intentional RBAC boundary. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but the confidentiality impact is high given that the exposed credential grants direct Elasticsearch data-plane access.
Sensitive data exposure in JetBrains TeamCity before 2025.11.2 allows authenticated low-privileged users to read confidential values stored in default build agent parameters. The root cause (CWE-526) indicates that sensitive information - such as API keys, tokens, or credentials - is passed or stored through agent environment/configuration parameters without adequate access restrictions. With a CVSS score of 4.3 and no public exploit or KEV listing, this represents a moderate-priority information disclosure risk, most dangerous in environments where agent parameters are used to propagate secrets across pipelines.
IBM Planning Analytics Advanced Certified Containers 3.1.0 versions up to 3.1.4 contains a vulnerability that allows attackers to a local privileged user to obtain sensitive information from environment variabl (CVSS 4.4).
IBM DB2 Recovery Expert for LUW 5.5 Interim Fix 002 discloses sensitive information in an environment variable that could aid in further attacks against the system. [CVSS 5.3 MEDIUM]
IBM Controller 11.1.0 through 11.1.1 and IBM Cognos Controller 11.0.0 through 11.0.1 FP6 stores unencrypted sensitive information in environmental variables files which can be obtained by an authenticated user.
Authenticated users of Letta through 0.16.8 can read server secrets when the LocalSandbox tool backend is used, because tool subprocesses inherit the server process environment; calling POST /v1/tools/run or running a custom tool can expose LETTA_PG_URI, POSTGRES_PASSWORD, and provider API keys. In multi-tenant deployments sharing one Postgres instance, those leaked database credentials can be used to reach other tenants' data, although single-tenant or properly isolated sandbox deployments are much less exposed. Publicly available exploit code exists, but the provided data does not confirm active exploitation (no CISA KEV entry), and exploitation requires an authenticated account with permission to execute tools.
python-utcp CLI subprocess environment passes all process-level secrets to every tool call. When chained with CVE-2026-45369 command injection, remote authenticated attackers with low-privilege LLM tool access can exfiltrate AWS credentials, API keys, database URLs, and other environment variables in a single HTTP request. Patch available in version 1.1.2 (NVD references 1.1.3 as fixed version). GitHub security advisory confirms proof-of-concept demonstrating credential theft via env dump to attacker-controlled endpoint.
Environment variable exfiltration in PraisonAIAgents versions prior to 1.5.128 allows unauthenticated remote attackers to steal secrets (database credentials, API keys, cloud access keys) through shell_tools.py execute_command function. The vulnerability leverages deceptive command approval where unexpanded $VAR references shown to human reviewers differ from executed commands containing expanded environment variable values. Requires user interaction. No public exploit identified at time of analysis.
Information exposure in mini-swe-agent versions 1.10.0 through 2.4.6 allows remote attackers to read sensitive environment variables, such as API keys, from the host system when the BubblewrapEnvironment sandbox is used. The sandbox fails to clear the environment (missing --clearenv), so sandboxed commands inherit the host environment. An attacker can leverage prompt injection in processed task content to direct the agent to exfiltrate these secrets over the network. Exploitation requires the use of BubblewrapEnvironment, presence of sensitive variables in the environment, and attacker-controlled task content; it is a moderate, context-dependent risk, and no public exploit has been identified at the time of analysis.
Environment variable exposure in Renovate (versions 42.68.1 through 42.96.3 and 43.0.0 through 43.4.4) leaks the full process environment - including privileged credentials - into every child process spawned during dependency update operations. The regression was introduced inadvertently on 2025-12-30 when Renovate migrated to the `execa` library, whose default behavior extends rather than replaces environment variables, silently bypassing Renovate's intended allowlist filtering. Both insider attackers (with repository write access) and outsider attackers (via supply-chain compromise of a processed dependency) can embed credential-harvesting code in scripts that Renovate executes, exfiltrating GitHub tokens, registry credentials, and cloud IAM keys accessible to the deployment. No public exploit has been identified at time of analysis, but the vendor explicitly recommends rotating all credentials that affected Renovate instances had access to.
Cleartext token exposure in Elastic Cloud on Kubernetes allows any principal with namespace workload-spec read access to retrieve live Elasticsearch service account credentials. Affected deployments are those running Fleet Server resources configured to authenticate to Elasticsearch via service account tokens - ECK writes the token directly into the generated Pod specification in cleartext rather than referencing the Kubernetes Secret where other credentials are stored, bypassing an intentional RBAC boundary. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but the confidentiality impact is high given that the exposed credential grants direct Elasticsearch data-plane access.
Sensitive data exposure in JetBrains TeamCity before 2025.11.2 allows authenticated low-privileged users to read confidential values stored in default build agent parameters. The root cause (CWE-526) indicates that sensitive information - such as API keys, tokens, or credentials - is passed or stored through agent environment/configuration parameters without adequate access restrictions. With a CVSS score of 4.3 and no public exploit or KEV listing, this represents a moderate-priority information disclosure risk, most dangerous in environments where agent parameters are used to propagate secrets across pipelines.
IBM Planning Analytics Advanced Certified Containers 3.1.0 versions up to 3.1.4 contains a vulnerability that allows attackers to a local privileged user to obtain sensitive information from environment variabl (CVSS 4.4).
IBM DB2 Recovery Expert for LUW 5.5 Interim Fix 002 discloses sensitive information in an environment variable that could aid in further attacks against the system. [CVSS 5.3 MEDIUM]
IBM Controller 11.1.0 through 11.1.1 and IBM Cognos Controller 11.0.0 through 11.0.1 FP6 stores unencrypted sensitive information in environmental variables files which can be obtained by an authenticated user.