dbcve.org
GradleApplication

CVE-2026-22865

HIGH · 7.4 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to 8.14.4 / 9.3.0 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. An exception like NoHttpResponseException can indicate transient errors. If the errors persist after a maximum number of retries, Gradle would continue to the next repository. This behavior could allow an attacker to disrupt the service of a repository and leverage another repository to serve malicious artifacts. This attack requires the attacker to have control over a repository after the disrupted repository. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Gradle versions before 9.3.0, certain transient exceptions (like NoHttpResponseException) during dependency resolution were not treated as fatal errors and did not disable the failing repository. Gradle would continue to the next repository in the list, potentially resolving dependencies from an attacker-controlled repository after disrupting a legitimate one.

MitigationUpgrade to Gradle 9.3.0 or later, which stops searching other repositories when encountering these types of errors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GradleApplication
Affected:< 8.14.4>= 9.0.0, < 9.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Gradle version
    Run 'gradle --version' or check the Gradle wrapper properties file (gradle/wrapper/gradle-wrapper.properties) for the 'distributionUrl' property
    Affected if The version is less than 8.14.4, or greater than or equal to 9.0.0 but less than 9.3.0
  2. Identify configured repositories
    Search build configuration files (build.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts) for 'repositories' blocks and count the number of declared repositories
    Affected if Multiple repositories are declared in any build configuration
  3. Check for repository failover behavior
    Review build logs or dependency resolution output for cases where Gradle falls back to a secondary repository after a transient failure (such as NoHttpResponseException or network-related exceptions)
    Affected if Gradle successfully resolves dependencies from a secondary repository after a transient error from a primary repository

You are affected if your installed Gradle version falls within the vulnerable ranges AND you have multiple repositories configured, allowing Gradle to continue searching other repositories after transient failures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.14.4 / 9.3.0 or later
Fixed in 8.14.49.3.0
Interim mitigation

Upgrade to Gradle 9.3.0 or later, which stops searching other repositories when encountering these types of errors.

Recommended fix High confidence

Gradle 8.14.4 (for 8.x users) or Gradle 9.3.0 (for 9.x users)

  1. Identify the current Gradle version in use by checking the Gradle wrapper properties file (gradle/wrapper/gradle-wrapper.properties) or running 'gradle --version'
  2. Determine which Gradle release line (8.x or 9.x) is in use based on the current version
  3. If using Gradle 8.x version < 8.14.4: Upgrade to Gradle 8.14.4 or later (8.14.4, 8.14.5, etc.)
  4. If using Gradle 9.x version >= 9.0.0 and < 9.3.0: Upgrade to Gradle 9.3.0 or later
  5. Update the Gradle wrapper by running 'gradle wrapper --gradle-version=<new-version>' or manually updating the gradle-wrapper.properties file
  6. Verify the upgrade by running 'gradle --version' to confirm the new version is active
  7. Test build scripts and plugins to ensure compatibility with the new Gradle version
Caveat Major Gradle upgrades may introduce breaking changes in build scripts, task names, or plugin compatibility; review the Gradle release notes for the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gradle Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22865 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data