dbcve.org
Parse ServerApplication · Parseplatform

CVE-2025-67727

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to after 8.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Parse Server is an open source backend that can be deployed to any infrastructure that runs Node.js. In versions prior to 8.6.0-alpha.2, a GitHub CI workflow is triggered in a way that grants the GitHub Actions workflow elevated permissions, giving it access to GitHub secrets and write permissions which are defined in the workflow. Code from a fork or lifecycle scripts is potentially included. Only the repository's CI/CD infrastructure is affected, including any public GitHub forks with GitHub Actions enabled. This issue is fixed version 8.6.0-alpha.2 and commits 6b9f896 and e3d27fe.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Parse Server versions prior to 8.6.0-alpha.2 have a CI/CD security vulnerability where a GitHub Actions workflow is triggered with elevated permissions (access to secrets and write permissions). Malicious code from forks or lifecycle scripts can potentially exfiltrate these secrets due to the overly permissive workflow configuration.

MitigationUpgrade to version 8.6.0-alpha.2 or cherry-pick commits 6b9f896 and e3d27fe to fix the workflow permission configuration. Public forks should disable GitHub Actions until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parse ServerApplication
Affected:<= 8.5.0= 8.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Parse Server version
    Run 'npm list parse-server' or check package.json for the parse-server version entry. Alternatively, query the Parse Server /version endpoint if exposed.
    Affected if Version is 8.5.0 or lower, or exactly 8.6.0 (8.6.0-alpha.2 and above are not affected)
  2. Locate GitHub Actions workflow files
    Inspect the .github/workflows/ directory in the repository for YAML workflow files.
    Affected if Workflow files exist and the repository uses GitHub Actions for CI/CD
  3. Examine workflow permission settings
    Open each workflow YAML file and look for the 'permissions' block at the top level. Check if permissions include 'contents: write', 'actions: write', or if 'secrets' are accessible (not set to 'none').
    Affected if Workflow has write permissions on contents or actions, or has broad access to secrets
  4. Check workflow trigger configuration
    Look for 'on:' sections in workflow files to identify triggers such as 'pull_request_target', 'workflow_dispatch', or triggers that run on forks.
    Affected if Workflows can be triggered by external contributors, forks, or untrusted inputs

You are affected if Parse Server version is 8.6.0 or lower AND your repository contains GitHub Actions workflows with write permissions or secret access that can be triggered by forks or external inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.5.0
Vendor patch github.com →
Interim mitigation

Upgrade to version 8.6.0-alpha.2 or cherry-pick commits 6b9f896 and e3d27fe to fix the workflow permission configuration. Public forks should disable GitHub Actions until patched.

Recommended fix High confidence

8.6.0-alpha.2 or later

  1. Check current Parse Server version using `npm list parse-server` or checking package.json
  2. Backup your current deployment and configuration
  3. Upgrade to Parse Server version 8.6.0-alpha.2 or later using `npm install [email protected]` or newer
  4. Verify the upgrade was successful by checking the installed version
  5. Review and test your Parse Server deployment to ensure functionality is intact
Caveat Alpha releases may have stability considerations; ensure testing in non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parse Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67727 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data