CVE-2021-47986 Details
Description
Parse Server before 4.10.0 contains a supply chain vulnerability where incorrect version tags were pushed to the repository linking to unreviewed code in a personal fork. Attackers could exploit this by specifying affected version tags in dependency declarations to execute unreviewed and potentially malicious code.
A supply chain vulnerability has been identified in Parse Server versions prior to 4.10.0. This vulnerability arises from incorrect version tags that were pushed to the repository, linking to unreviewed code in a personal fork of a contributor with write access. Attackers could exploit this by specifying the affected version tags in dependency declarations, potentially executing malicious code. The issue also affects users of the Bitnami Parse Server image, which incorporated one of the incorrect tags.
Users are advised to upgrade to Parse Server version 4.10.0. If the vulnerability has already been exploited, a downgrade to version 4.5.2 is recommended.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 26, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-494 | Download of Code Without Integrity Check | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| parseplatform parse-server | 4.0.0 beta1 4.0.0 beta2 4.0.0 beta3 4.0.0 beta4 4.0.0 beta5 4.0.0 beta6 4.0.3 4.0.4 4.0.6 4.0.7 4.0.8 4.0.9 4.0.10 4.0.11 4.0.12 4.0.13 4.0.14 4.6.0 - 4.6.0 beta 4.7.0 4.8.0 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.9.0 4.9.1 4.9.2 4.9.3 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | Initial Analysis | [email protected] |
| Jun 26, 2026 | CVE Modified | CISA-ADP |
| Jun 25, 2026 | New CVE Received | [email protected] |