Skip to main content

CVE-2025-54594: CWE-269: Improper Privilege Management in callstackincubator react-native-bottom-tabs

Critical
VulnerabilityCVE-2025-54594cvecve-2025-54594cwe-269cwe-94
Published: Tue Aug 05 2025 (08/05/2025, 23:31:53 UTC)
Source: CVE Database V5
Vendor/Project: callstackincubator
Product: react-native-bottom-tabs

Description

react-native-bottom-tabs is a library of Native Bottom Tabs for React Native. In versions 0.9.2 and below, the github/workflows/release-canary.yml GitHub Actions repository workflow improperly used the pull_request_target event trigger, which allowed for 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 then trigger the vulnerable workflow by posting a specific comment (!canary). This allowed for arbitrary code execution, leading to the exfiltration of sensitive secrets such as GITHUB_TOKEN and NPM_TOKEN, and could have allowed an attacker to push malicious code to the repository or publish compromised packages to the NPM registry. There is a remediation commit which removes github/workflows/release-canary.yml, but a version with this fix has yet to be released.

AI-Powered Analysis

AILast updated: 08/13/2025, 01:08:20 UTC

Technical Analysis

CVE-2025-54594 is a critical security vulnerability affecting the react-native-bottom-tabs library, a popular React Native component for implementing native bottom tab navigation. The vulnerability arises from improper privilege management in the GitHub Actions workflow file github/workflows/release-canary.yml, specifically in versions 0.9.2 and below. This workflow improperly uses the pull_request_target event trigger, which runs workflows in the context of the base repository rather than the forked pull request. Consequently, an attacker can submit a malicious pull request from a forked repository containing a crafted preinstall script within the package.json file. By posting a specific comment (!canary), the attacker triggers the vulnerable workflow, causing the malicious code to execute with elevated privileges. This leads to arbitrary code execution within the repository's CI environment, enabling the attacker to exfiltrate sensitive secrets such as GITHUB_TOKEN and NPM_TOKEN. These tokens provide access to repository management and NPM package publishing capabilities, respectively. Exploiting this vulnerability could allow an attacker to push malicious code directly to the repository or publish compromised versions of the react-native-bottom-tabs package to the NPM registry, potentially impacting all downstream users. Although a remediation commit has been made to remove the vulnerable workflow file, no fixed version has been officially released yet. The CVSS v3.1 base score is 9.1 (critical), reflecting the high impact on confidentiality and integrity without requiring authentication or user interaction, and with network attack vector and low attack complexity.

Potential Impact

For European organizations, this vulnerability poses a significant risk, especially those relying on react-native-bottom-tabs in their mobile applications or development pipelines. Compromise of the repository or NPM package could lead to widespread distribution of malicious code, affecting the confidentiality and integrity of applications used by European users. Sensitive corporate data could be exfiltrated if attackers leverage stolen tokens to access private repositories or inject backdoors. Furthermore, organizations using CI/CD pipelines that integrate this library may face supply chain attacks, resulting in compromised software builds and potential regulatory non-compliance under GDPR due to data breaches. The ability to publish malicious packages to NPM also threatens the broader European developer ecosystem, potentially impacting numerous downstream projects and users.

Mitigation Recommendations

European organizations should immediately audit their usage of react-native-bottom-tabs and identify if versions 0.9.2 or below are in use. Until an official patched version is released, organizations should consider temporarily removing or replacing this dependency. Additionally, repository administrators should review and restrict GitHub Actions workflows, avoiding the use of pull_request_target triggers with untrusted code. Implementing least privilege principles for GitHub tokens, such as using fine-grained personal access tokens with minimal scopes, can limit potential damage. Monitoring repository activity for unusual pull requests or comments triggering workflows is advised. Organizations should also rotate any exposed secrets and enforce multi-factor authentication on developer accounts. Finally, subscribing to vendor advisories and updating to a patched version promptly once available is critical.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-07-25T16:19:16.095Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68929821ad5a09ad00ec5ad6

Added to database: 8/5/2025, 11:47:45 PM

Last enriched: 8/13/2025, 1:08:20 AM

Last updated: 9/1/2025, 10:14:21 AM

Views: 29

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats