Malicious dependency resolution via nonfatal repository errors
Published Jan 16, 2026 · Updated Jan 16, 2026
Dependency confusion in Gradle Build Tool before 8.14.4 and 9.0.0 through 9.2.1 allows remote attackers to supply malicious artifacts. After exhausting retries for exceptions such as NoHttpResponseException, dependency resolution treats the failure as nonfatal and advances to the next configured repository. Exploitation requires control of a later repository, disruption of an earlier one, and a build that requests an artifact from the fallback source.
Summary
What happened
Dependency confusion in Gradle Build Tool before 8.14.4 and 9.0.0 through 9.2.1 allows remote attackers to supply malicious artifacts. After exhausting retries for exceptions such as NoHttpResponseException, dependency resolution treats the failure as nonfatal and advances to the next configured repository. Exploitation requires control of a later repository, disruption of an earlier one, and a build that requests an artifact from the fallback source.
The record
- CVE
- CVE-2026-22865
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-829, CWE-494, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 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=< 9.3.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