A remote code injection vulnerability exists in the execute_code function of the code_utils.py file within the CodeAction component of eosphoros-ai DB-GPT versions up to 0.8.2. This flaw allows an attacker to execute arbitrary code remotely. Public exploit code has been released, and the project has not yet issued a response or fix.
Ansible-core versions starting from 2.19 introduced a regression where tasks marked with no_log: true still leak sensitive information in their exception messages. This occurs because the exception field is preserved and printed by default, exposing secret values in error outputs such as argument-validation errors, templating errors, and assertion failures. The issue does not exist in version 2.16, where error texts are properly censored.
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Apache Sling Engine. Content-Type, charset, and redirect changes from an included component evade the protectheaders / checkcontenttype enforcement through setHeader(), repeated calls to setContentType(), the charset APIs, Servlet 6.1 redirect overloads, and stale config - enabling stored XSS despite enabled protections.
This issue affects Apache Sling Engine before 3.0.4.
Users are recommended to upgrade to version 3.0.4, which fixes the issue.
---
_-= Per source details. Do not edit below this line.=-_
## Source: kam193 (54d27496a09fce8a393650469621dc308a6578c6cf694589bda9d4b298a6c08e)
Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.
---
Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.
Campaign: GENERIC-standard-pypi-install-pentest
Reasons (based on the campaign):
- The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
- The package overrides the install command in setup.py to execute malicious code during installation.
## Source: ossf-package-analysis (a5d59e94208df065ea45c96e99b262462ea08b134b85f9d1f707f4350623d7ff)
The OpenSSF Package Analysis project identified 'mcp-teamviewer' @ 0.0.1 (pypi) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Execution with unnecessary privileges vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute pardus-usb-formatter allows Privilege Abuse.
This issue affects pardus-usb-formatter: from 0.7.0 before 0.7.2.
In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of the Keycloak users that the chart creates in cleartext in a Kubernetes ConfigMap.
The template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-basyx-keycloak-init-config`. By default this includes the bootstrap administrator user. That user holds the `admin` role and has a non-temporary password. A principal that can read ConfigMaps but not Secrets in the release namespace, such as a holder of the built-in Kubernetes `view` ClusterRole, can read the password from the ConfigMap and log in to Keycloak as this user. The resulting token carries the `admin` role, which the default BaSyx ABAC rules map to full rights on all BaSyx APIs in the deployment.
The bundled Keycloak is disabled by default. The issue is fixed in version 3.12.2 of the `basyx` chart, which moves the initialization users to the Keycloak credentials Secret. Affected users should upgrade and change the passwords of users that were created through the chart.
A weakness has been identified in eosphoros-ai DB-GPT up to 0.8.2. Impacted is the function exec_module of the file hf_adapter.py of the component HuggingFace Adapter. Executing a manipulation of the argument trust_remote_code can lead to inclusion of functionality from untrusted control sphere. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-121489 is a critical path traversal vulnerability in Apache Juneau affecting versions prior to 9.2.1. The DirectoryResource microservice fails to restrict request paths to its configured root directory, allowing clients to read, write, or delete files outside the intended directory when certain resource settings are enabled. This flaw is fixed in version 9.2.1.
CVE-2026-96677 is a critical cross-site scripting (XSS) vulnerability in Apache Juneau affecting versions prior to 9.2.1. The issue arises because HTML document serialization does not encode variable substitutions in page chrome elements such as headers and navigation bars. Applications that include request-derived variables in these areas without encoding them are vulnerable to XSS attacks. The default chrome does not use request variables, so only customized applications are affected. The vulnerability is fixed in Apache Juneau version 9.2.1.
CVE-2026-73117 is a critical HTTP Response Splitting vulnerability in Apache Juneau through version 9.2.0. The issue arises because response header values and redirect targets passed to the servlet container are not properly sanitized, allowing remote attackers to inject malicious header lines or redirect users to arbitrary external sites. The vulnerability depends on application code that uses request data to set headers or redirects. Apache Juneau version 9.2.1 addresses this by sanitizing header values by default and introducing a safer redirect method.
CVE-2026-73116 is a critical vulnerability in Apache Juneau through version 9.2.0 where the RestClient improperly retains credential headers during HTTP redirects. This allows sensitive headers such as Authorization, Cookie, Proxy-Authorization, and X-API-Key to be sent to unintended hosts or downgraded protocols. The issue is fixed in version 9.2.1.
Apache Juneau versions prior to 9.2.1 have a vulnerability where error responses expose internal exception class names and messages to remote clients. This occurs through the 'Thrown' response header and may also include internal exception messages in the error body, even if stack-trace rendering is disabled. This information disclosure reveals implementation details that could aid attackers. The issue is fixed in version 9.2.1.
The 'teamviewer-mcp-server' package version 0.0.1 on PyPI has been identified as malicious by the OpenSSF Package Analysis project. The package is flagged due to its communication with a domain linked to malicious activity. No CVSS score or detailed technical impact is provided.
CVE-2026-73100 is a critical vulnerability in Apache Juneau up to version 9.2.0 where sensitive information such as Authorization headers and API keys are logged in cleartext when a server error occurs. This exposure occurs because the default REST server call logger does not redact sensitive request headers before writing them to application logs. The issue is fixed in version 9.2.1.
Cross-Site Request Forgery (CSRF) vulnerability in Apache Juneau.
The REST server accepts a "content" query parameter that replaces the request body, and this is enabled by default on every HTTP method, including GET. A cross-site link can therefore deliver an attacker-chosen request body to an endpoint without a CORS preflight, defeating protections that rely on the HTTP method or content type instead of an anti-CSRF token.
This issue affects Apache Juneau: through 9.2.0.
Users are recommended to upgrade to version 9.2.1, which fixes the issue. Applications that do not use the content parameter can also set disableContentParam to true.
Improper control of dynamically-loaded code vulnerability in Apache Juneau.
When Apache Juneau parses a value into a property of type java.lang.Class (including parameterized forms), the default class swap loaded the named class with initialization enabled, so input naming a class on the application classpath ran that class's static initializer. The impact depends on the classes present in the deployment.
This issue affects Apache Juneau: through 9.2.0.
Users are recommended to upgrade to version 9.2.1, which fixes the issue.