Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-22816: Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs

33
Routine
HIGH 7.4REMOTEUPGRADE

CVE-2026-22816 is a high-severity flaw (CVSS 7.4) affecting gradle. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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. If a Gradle build used

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.4 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 93%)
CISA exploited listNo
WeaknessCWE-494, CWE-829
Published2026-01-16
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: gradle

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gradle gradle UPGRADE
Affected: < 8.14.4 · >= 9.0.0 and < 9.3.0
Fixed in: 8.14.4, 9.3.0
Safe to downgrade to: a release before 9.0.0
1. Check installed version
apt-cache policy gradle || rpm -q gradle || gradle --version
2. UPGRADE to 8.14.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade gradle
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade gradle
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 9.0.0 (Debian / Ubuntu)
apt-cache madison gradle sudo apt install gradle=<VERSION_BEFORE_9.0.0> sudo apt-mark hold gradle
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list gradle sudo dnf downgrade gradle-<VERSION_BEFORE_9.0.0> sudo dnf versionlock add gradle
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-22816?

gradle: upgrade to 8.14.4, 9.3.0. Exact commands for each OS are on this page.

Is CVE-2026-22816 being exploited?

CVE-2026-22816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-22816 affect?

CVE-2026-22816 affects gradle. Severity is high (CVSS 7.4). 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

How urgent is CVE-2026-22816?

Priority 33/100. High severity; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.