Is CVE-2021-47987 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2021-47987 being exploited in the wild.

How severe is CVE-2021-47987?

High severity, with a CVSS score of 7.5, published 25 June 2026.

Which products and versions are affected?

Parse Community Parse Server < 4.10.0.

Is there a fix for CVE-2021-47987?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2021-47987 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2021-47987?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2021-47987: Parse Community Parse Server supply chain compromise via incorrect Git tags

Q: Is there a fix for CVE-2021-47987?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2021-47987 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2021-47987?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2021-47987 · Severity: high · CVSS 7.5 · Published 2026-06-25

Parse Server, an open-source backend framework, was affected by a supply chain incident where unauthorized version tags were added to its official code repository. These tags pointed to unvetted code from a contributor's personal account rather than the official project code. While no official software releases were compromised, organizations that configured their systems to pull code directly from these specific Git tags may have inadvertently installed unreviewed and potentially insecure software.

Quick answers

Is CVE-2021-47987 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2021-47987 being exploited in the wild.
How severe is CVE-2021-47987?: High severity, with a CVSS score of 7.5, published 25 June 2026.
Which products and versions are affected?: Parse Community Parse Server < 4.10.0.
Is there a fix for CVE-2021-47987?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2021-47987 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2021-47987?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A supply chain vulnerability (CWE-494) occurred in Parse Server when a contributor with write access pushed version tags to the official repository that pointed to an unreviewed personal fork. While no official npm releases were published using these tags, the vulnerability affected users who defined git-based dependencies referencing the compromised tags (e.g., `parse-server#4.9.3`). Additionally, some third-party distributions, such as Bitnami images, reportedly ingested the incorrect tags. Although no explicitly malicious code was identified during the investigation, the unvetted nature of the code means security vulnerabilities or backdoors could not be ruled out. The issue was resolved by deleting the incorrect tags and releasing version 4.10.0.

Affected products

Parse Community Parse Server < 4.10.0

Timeline

2021-07-21: other: Project maintainers first became aware of the issue
2021-09-03: advisory: GitHub Security Advisory published
2026-06-25: disclosed: CVE-2021-47987 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.