How severe is GHSA-hhr2-f668-ff2w?

No CVSS score has been assigned to GHSA-hhr2-f668-ff2w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hhr2-f668-ff2w?

GHSA-hhr2-f668-ff2w affects the following packages: org.gradle:gradle-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-hhr2-f668-ff2w?

Update org.gradle:gradle-core to 6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhr2-f668-ff2w is resolved across your whole dependency graph.

How do I detect GHSA-hhr2-f668-ff2w in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.gradle:gradle-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hhr2-f668-ff2w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-hhr2-f668-ff2w actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-hhr2-f668-ff2w, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-hhr2-f668-ff2w?

GHSA-hhr2-f668-ff2w has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hhr2-f668-ff2w?

GHSA-hhr2-f668-ff2w is classified as Broken Cryptographic Algorithm (CWE-327). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hhr2-f668-ff2w published, and has it been updated?

GHSA-hhr2-f668-ff2w was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Use of a weak cryptographic algorithm in GradleGHSA-hhr2-f668-ff2w

Fix: gradle/gradle#10543

GHSA-hhr2-f668-ff2w is a Broken Cryptographic Algorithm vulnerability in org.gradle:gradle-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.gradle:gradle-core — see the affected versions and patch details below.

Also known asCVE-2019-16370

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.gradle:gradle-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.gradle:gradle-core`	all versions	6.0`org.gradle:gradle-core:6.0`

Affected Products

1 product · 1 configurations

Application

gradlegradle

< 6.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorith…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.gradle:gradle-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.gradle:gradle-core to 6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhr2-f668-ff2w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.