CVE-2023-26053 Vulnerability Analysis & Exploit Details

CVE-2023-26053
Vulnerability Scoring

6.6
/10
High Risk

If left unpatched, CVE-2023-26053 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-26053 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:50 UTC
Originally published on: 🕓 02 Mar 2023, 04:15 UTC

Time between publication and last update: 630 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-26053 Vulnerability Summary

CVE-2023-26053: Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp` element in the metadata is a protection against this issue.

Assessing the Risk of CVE-2023-26053

Access Complexity Graph

The exploitability of CVE-2023-26053 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-26053

The exploitability of CVE-2023-26053 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-26053, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-26053, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-26053 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-26053 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-26053 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.373% (probability of exploit)

EPSS Percentile: 72.96% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 27.040000000000006% of others.

CVE-2023-26053 References

External References

CWE Common Weakness Enumeration

CWE-829

CAPEC Common Attack Pattern Enumeration and Classification

  • Code Inclusion CAPEC-175 An adversary exploits a weakness on the target to force arbitrary code to be retrieved locally or from a remote location and executed. This differs from code injection in that code injection involves the direct inclusion of code while code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
  • Serialized Data External Linking CAPEC-201 An adversary creates a serialized data file (e.g. XML, YAML, etc...) that contains an external data reference. Because serialized data parsers may not validate documents with external references, there may be no checks on the nature of the reference in the external data. This can allow an adversary to open arbitrary files or connections, which may further lead to the adversary gaining access to information on the system that they would normally be unable to obtain.
  • DTD Injection CAPEC-228 An attacker injects malicious content into an application's DTD in an attempt to produce a negative technical impact. DTDs are used to describe how XML documents are processed. Certain malformed DTDs (for example, those with excessive entity expansion as described in CAPEC 197) can cause the XML parsers that process the DTDs to consume excessive resources resulting in resource depletion.
  • Local Code Inclusion CAPEC-251 The attacker forces an application to load arbitrary code files from the local machine. The attacker could use this to try to load old versions of library files that have known vulnerabilities, to load files that the attacker placed on the local machine during a prior attack, or to otherwise change the functionality of the targeted application in unexpected ways.
  • PHP Local File Inclusion CAPEC-252 The attacker loads and executes an arbitrary local PHP file on a target machine. The attacker could use this to try to load old versions of PHP files that have known vulnerabilities, to load PHP files that the attacker placed on the local machine during a prior attack, or to otherwise change the functionality of the targeted application in unexpected ways.
  • Remote Code Inclusion CAPEC-253 The attacker forces an application to load arbitrary code files from a remote location. The attacker could use this to try to load old versions of library files that have known vulnerabilities, to load malicious files that the attacker placed on the remote machine, or to otherwise change the functionality of the targeted application in unexpected ways.
  • Force Use of Corrupted Files CAPEC-263 This describes an attack where an application is forced to use a file that an attacker has corrupted. The result is often a denial of service caused by the application being unable to process the corrupted file, but other results, including the disabling of filters or access controls (if the application fails in an unsafe way rather than failing by locking down) or buffer overflows are possible.
  • Open-Source Library Manipulation CAPEC-538 Adversaries implant malicious code in open source software (OSS) libraries to have it widely distributed, as OSS is commonly downloaded by developers and other users to incorporate into software development projects. The adversary can have a particular system in mind to target, or the implantation can be the first stage of follow-on attacks on many systems.
  • Local Execution of Code CAPEC-549 An adversary installs and executes malicious code on the target system in an effort to achieve a negative technical impact. Examples include rootkits, ransomware, spyware, adware, and others.
  • Inclusion of Code in Existing Process CAPEC-640 The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, function hooking, reflective code loading, and more.
  • Root/Jailbreak Detection Evasion via Hooking CAPEC-660 An adversary forces a non-restricted mobile application to load arbitrary code or code files, via Hooking, with the goal of evading Root/Jailbreak detection. Mobile device users often Root/Jailbreak their devices in order to gain administrative control over the mobile operating system and/or to install third-party mobile applications that are not provided by authorized application stores (e.g. Google Play Store and Apple App Store). Adversaries may further leverage these capabilities to escalate privileges or bypass access control on legitimate applications. Although many mobile applications check if a mobile device is Rooted/Jailbroken prior to authorized use of the application, adversaries may be able to "hook" code in order to circumvent these checks. Successfully evading Root/Jailbreak detection allows an adversary to execute administrative commands, obtain confidential data, impersonate legitimate users of the application, and more.
  • Repo Jacking CAPEC-695 An adversary takes advantage of the redirect property of directly linked Version Control System (VCS) repositories to trick users into incorporating malicious code into their applications.
  • Install Malicious Extension CAPEC-698 An adversary directly installs or tricks a user into installing a malicious extension into existing trusted software, with the goal of achieving a variety of negative technical impacts.

Vulnerable Configurations

  • cpe:2.3:a:gradle:gradle:6.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.3.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.3.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.5.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.5.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.5.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.5.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:rc6:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.0:milestone3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.0:milestone3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.0:milestone3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.0:milestone3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.9.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.9.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.9.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.9.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:6.9.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:6.9.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.0:milestone3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.0:milestone3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.3:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.3:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.3.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.3.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:gradle:gradle:7.6.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:gradle:gradle:7.6.0:milestone1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-26053: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...
  • CVE-2025-2010 – The JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin plugin for WordPress is vulnerable to SQL Injection via the 'jobwp_upload_re...
  • CVE-2025-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...