CVE-2025-53546

9.1 CRITICAL

📋 TL;DR

This CVE describes a GitHub Actions vulnerability in Folo where the pull_request_target workflow allows execution of untrusted code with full access to repository secrets. Attackers can exploit this to steal the GITHUB_TOKEN and gain write access to the repository. All Folo users with GitHub Actions enabled are affected.

💻 Affected Systems

Products:
  • Folo
Versions: All versions before commit 585c6a591440cd39f92374230ac5d65d7dd23d6a
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations using GitHub Actions with the vulnerable workflow file.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete repository takeover allowing code modification, secret exfiltration, and potential supply chain attacks against downstream users.

🟠

Likely Case

Unauthorized code commits, secret theft, and repository defacement or malware injection.

🟢

If Mitigated

Limited impact with proper GitHub Actions permissions and secret management controls in place.

🌐 Internet-Facing: HIGH - GitHub repositories are internet-accessible and workflows can be triggered via pull requests.
🏢 Internal Only: LOW - The vulnerability requires external interaction via GitHub's public interface.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires creating a malicious pull request but doesn't require authentication to the target repository.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Commit 585c6a591440cd39f92374230ac5d65d7dd23d6a

Vendor Advisory: https://github.com/RSSNext/Folo/security/advisories/GHSA-h87r-5w74-qfm4

Restart Required: No

Instructions:

1. Update to commit 585c6a591440cd39f92374230ac5d65d7dd23d6a or later. 2. Replace .github/workflows/auto-fix-lint-format-commit.yml with the patched version. 3. Review and rotate any exposed secrets.

🔧 Temporary Workarounds

Disable vulnerable workflow

all

Temporarily disable the auto-fix-lint-format-commit.yml workflow in GitHub Actions settings

Restrict workflow permissions

all

Modify workflow to use read-only GITHUB_TOKEN permissions

permissions: read-all

🧯 If You Can't Patch

  • Disable GitHub Actions entirely for the repository
  • Implement branch protection rules requiring review before workflow execution

🔍 How to Verify

Check if Vulnerable:

Check if .github/workflows/auto-fix-lint-format-commit.yml exists and uses pull_request_target without proper permissions restrictions.

Check Version:

git log --oneline -1 .github/workflows/auto-fix-lint-format-commit.yml

Verify Fix Applied:

Verify the workflow file has been updated to commit 585c6a591440cd39f92374230ac5d65d7dd23d6a and uses appropriate permissions.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected workflow runs from pull requests
  • Unauthorized commits or secret access in GitHub audit logs

Network Indicators:

  • Unusual outbound connections from GitHub Actions runners during pull request processing

SIEM Query:

source="github_audit" action="workflow.run" workflow_name="auto-fix-lint-format-commit.yml"

🔗 References

📤 Share & Export