Unauthorized code merges via unverified commit provenance
Published May 31, 2022 · Updated Apr 23, 2025
Improper ownership verification in GitHub Action Merge Dependabot before 3.2.0 allows attackers to merge malicious code through Dependabot PRs. The action trusts the pull request actor name dependabot[bot] without verifying each commit's author, committer, and GitHub signature. Exploitation requires a workflow action that can modify the Dependabot pull request, after which the trusted automation approves and merges the injected commit without maintainer review.
Summary
What happened
Improper ownership verification in GitHub Action Merge Dependabot before 3.2.0 allows attackers to merge malicious code through Dependabot PRs. The action trusts the pull request actor name dependabot[bot] without verifying each commit's author, committer, and GitHub signature. Exploitation requires a workflow action that can modify the Dependabot pull request, after which the trusted automation approves and merges the injected commit without maintainer review.
The record
- CVE
- CVE-2022-29220
- Published
- May 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- Fastify
- Product
- GitHub Action Merge Dependabot
- Classifications
- CWE-345, CWE-283, T1195.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 3.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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