Unreviewed code execution via incorrect Git tags
Published Jun 25, 2026 · Updated Jun 25, 2026
Supply-chain exposure in Parse Server before 4.10.0 allows attackers to run unreviewed code through dependencies pinned to incorrect Git tags. Repository tags for named versions resolved to a contributor's personal fork rather than reviewed Parse Platform code, so dependency resolution installed that fork. Exposure requires a Git-tag dependency or the Bitnami 4.9.3 image; no npm release used the tags, and the vendor found no malicious code.
Summary
What happened
Supply-chain exposure in Parse Server before 4.10.0 allows attackers to run unreviewed code through dependencies pinned to incorrect Git tags. Repository tags for named versions resolved to a contributor's personal fork rather than reviewed Parse Platform code, so dependency resolution installed that fork. Exposure requires a Git-tag dependency or the Bitnami 4.9.3 image; no npm release used the tags, and the vendor found no malicious code.
The record
- CVE
- CVE-2021-47986
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Parse Platform
- Product
- Parse Server
- Classifications
- CWE-494, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.10.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo