CVE-2025-67727

9.8 CRITICAL

📋 TL;DR

This CVE describes a GitHub Actions workflow vulnerability in Parse Server that grants elevated permissions to CI/CD pipelines. It allows unauthorized access to GitHub secrets and write permissions, potentially enabling code injection from forks or lifecycle scripts. Only repositories using GitHub Actions for CI/CD are affected, including public forks with Actions enabled.

💻 Affected Systems

Products:
  • Parse Server
Versions: All versions prior to 8.6.0-alpha.2
Operating Systems: Any OS running Node.js
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects GitHub Actions CI/CD workflows in the repository and public forks with Actions enabled. Does not affect Parse Server runtime or production deployments directly.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal GitHub secrets, inject malicious code into the repository, compromise the CI/CD pipeline, and potentially gain persistent access to the development infrastructure.

🟠

Likely Case

Unauthorized access to GitHub secrets leading to credential theft, potential code injection in CI/CD workflows, and compromise of the repository's build/deploy process.

🟢

If Mitigated

Limited to repository forks with Actions enabled, with no direct impact on production Parse Server deployments if proper secrets management and access controls are in place.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires access to create or modify GitHub Actions workflows, typically through repository forks or compromised contributor accounts.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 8.6.0-alpha.2

Vendor Advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-6w8g-mgvv-3fcj

Restart Required: No

Instructions:

1. Update Parse Server to version 8.6.0-alpha.2 or later. 2. Apply commits 6b9f8963cc3debf59cd9c5dfc5422aff9404ce9d and e3d27fea08c8d8bdd9770a689bc2d757cda48b66. 3. Review and update GitHub Actions workflows to ensure proper permission scoping.

🔧 Temporary Workarounds

Disable GitHub Actions in Forks

all

Disable GitHub Actions in repository forks to prevent exploitation through forked workflows.

Navigate to repository Settings > Actions > General > Disable Actions for forked repositories

Restrict GitHub Secrets Access

all

Review and restrict GitHub secrets access in workflows, using minimal required permissions.

Review .github/workflows/*.yml files and set permissions: read-only where possible

🧯 If You Can't Patch

  • Review and audit all GitHub Actions workflows for excessive permissions
  • Rotate all GitHub secrets and credentials that may have been exposed

🔍 How to Verify

Check if Vulnerable:

Check if using Parse Server version < 8.6.0-alpha.2 and review GitHub Actions workflow files for permission settings.

Check Version:

npm list parse-server | grep parse-server

Verify Fix Applied:

Verify Parse Server version is >= 8.6.0-alpha.2 and that commits 6b9f896 and e3d27fe are applied.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized GitHub Actions workflow runs
  • Unexpected access to GitHub secrets in workflow logs
  • Suspicious code execution in CI/CD pipelines

Network Indicators:

  • Unusual API calls to GitHub from CI/CD infrastructure
  • Unexpected external connections during builds

SIEM Query:

source="github-actions" AND (event="workflow_run" OR event="repository_dispatch") AND action="completed" AND result="failure" | search suspicious_patterns

🔗 References

📤 Share & Export