Darryk10

**Name of the Vulnerable Software and Affected Versions** react-native-bottom-tabs versions 0.9.2 and earlier **Description** The react-native-bottom-tabs library improperly used the `pull request target` event trigger in the `github/workflows/release-canary.yml` GitHub Actions workflow. This allowed untrusted code from a forked pull request to be executed in a privileged context. An attacker could create a pull request containing a malicious `preinstall` script in the `package.json` file and trigger the vulnerable workflow by posting a specific comment (!canary). This enabled arbitrary code execution, potentially leading to the exfiltration of sensitive secrets such as `GITHUB TOKEN` and `NPM TOKEN`, and the possibility of pushing malicious code to the repository or publishing compromised packages to the NPM registry. Approximately 158,500 services are estimated to be affected yearly. **Recommendations** react-native-bottom-tabs versions prior to the release containing the fix for CVE-2025-54594 are vulnerable. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** dedupe versions prior to commit 3f61e79 **Description** dedupe is a Python library used for fuzzy matching, deduplication, and entity resolution on structured data. A critical severity issue exists in the `.github/workflows/benchmark-bot.yml` workflow, triggered by an `issue comment` with the `@benchmark` body. This workflow checks out the branch of a pull request (PR) manipulated by potentially malicious actors, leading to the execution of untrusted code. This could result in the exfiltration of the `GITHUB TOKEN`, which has write permissions, potentially leading to repository takeover. **Recommendations** Update to commit 3f61e79 or later to resolve this issue.

**Name of the Vulnerable Software and Affected Versions** dag-factory versions 0.23.0a8 and below **Description** dag-factory is a library for Apache Airflow® used to construct DAGs declaratively via configuration files. A high-severity issue exists in the `cicd.yml` workflow within the astronomer/dag-factory GitHub repository. When triggered by `pull request target`, the workflow is susceptible to exploitation, allowing an attacker to execute arbitrary code within the GitHub Actions runner environment. This misconfiguration enables an attacker to establish a reverse shell, exfiltrate sensitive secrets, including the `GITHUB TOKEN`, and gain full control over the repository. **Recommendations** Update to version 0.23.0a9 or later.

**Name of the Vulnerable Software and Affected Versions:** Folo (affected versions not specified) **Description:** Folo organizes feeds content into one timeline. The use of `pull request target` in the `.github/workflows/auto-fix-lint-format-commit.yml` workflow file can be exploited by attackers to execute untrusted code with full access to repository secrets. This allows for the exfiltration of the `GITHUB TOKEN`, which possesses high privileges, including content write access, enabling complete control over the repository. **Recommendations:** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** pgai versions prior to 8eb3567 **Description** The issue concerns the pgai Python library, which transforms PostgreSQL into a retrieval engine for RAG and Agentic applications. Prior to a specific commit, the library was vulnerable to an attack that allowed the exfiltration of all secrets used in one workflow. This included the GITHUB TOKEN with write permissions for the repository, enabling an attacker to tamper with all aspects of the repository, such as pushing arbitrary code and releases. **Recommendations** For versions prior to 8eb3567, update to a version that includes the fix from commit 8eb3567 to prevent the exfiltration of secrets. As a temporary workaround, consider restricting access to sensitive information and secrets within the workflow to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Spotipy versions prior to the commit that reverted the change (commit 9dfb7177b8d7bb98a5a6014f8e6436812a47576f) Description: The issue concerns the use of `pull request target` in `.github/workflows/integration tests.yml`, which can be exploited by attackers to execute untrusted code with full access to secrets from the base repository. This can lead to the exfiltration of sensitive information, including `GITHUB TOKEN`, `SPOTIPY CLIENT ID`, and `SPOTIPY CLIENT SECRET`. The `GITHUB TOKEN` can be used to completely take over the repository due to its content write privileges. This is a major security concern, especially in public repositories, as it allows the execution of untrusted code from a pull request with the context of the base repository. Recommendations: As a temporary workaround, consider disabling the use of `pull request target` in `.github/workflows/integration tests.yml` until a patch is available. Restrict access to secrets, such as `GITHUB TOKEN`, `SPOTIPY CLIENT ID`, and `SPOTIPY CLIENT SECRET`, to minimize the risk of exploitation. Update to a version that includes the commit 9dfb7177b8d7bb98a5a6014f8e6436812a47576f, which reverted the change that caused the issue.

**Name of the Vulnerable Software and Affected Versions** Harden-Runner versions 0.12.0 through 2.12.0 **Description** Harden-Runner is a CI/CD security agent that works like an EDR for GitHub Actions runners. The `disable-sudo` policy option is intended to prevent the GitHub Actions runner user from using sudo by removing the runner user from the sudoers file. However, this control can be bypassed as the runner user, being part of the docker group, can interact with the Docker daemon to launch privileged containers or access the host filesystem, allowing the attacker to regain root access or restore the sudoers file, effectively bypassing the restriction. **Recommendations** Update to version 2.12.0 or later to patch the `disable-sudo` bypass vulnerability. As a temporary workaround, consider restricting the runner user's access to the Docker daemon to minimize the risk of exploitation. Avoid using the `disable-sudo` policy option until the issue is resolved.

Name of the Vulnerable Software and Affected Versions: linux kernel (affected versions not specified) Description: The issue is related to a high out-of-bounds write in the uvcvideo module, specifically in the `uvc parse format` function. This can potentially lead to privilege escalation. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.