CVE-2026-52747 Vulnerability Analysis & Exploit Details

CVE-2026-52747
Vulnerability Scoring

8.6
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-52747 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-52747 Details

Status: Analyzed

Last updated: 🕗 14 Jul 2026, 20:00 UTC
Originally published on: 🕙 10 Jul 2026, 22:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-52747 Vulnerability Summary

CVE-2026-52747: ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Prior to 3.0.16, the multipart/form-data request body parser in libmodsecurity silently removes embedded line breaks from non-file form-field values before exporting them to ARGS and ARGS_POST because src/request_body_processor/multipart.cc overwrites reserved bytes in m_reserve instead of appending the current buffer. This creates a parser differential between ModSecurity and backend applications that preserve line breaks in form fields, allowing rules that inspect ARGS or ARGS_POST to miss payloads whose dangerous syntax depends on a line break. This issue is fixed in version 3.0.16.

Assessing the Risk of CVE-2026-52747

Access Complexity Graph

The exploitability of CVE-2026-52747 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-2026-52747

With low attack complexity and no required privileges, CVE-2026-52747 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-2026-52747, 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-2026-52747, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-52747 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2026-52747 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-52747 does not impact system availability.

CVE-2026-52747 References

External References

CWE Common Weakness Enumeration

CWE-180

CAPEC Common Attack Pattern Enumeration and Classification

  • Leverage Alternate Encoding CAPEC-267 An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
  • Using Unicode Encoding to Bypass Validation Logic CAPEC-71 An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.
  • Using Escaped Slashes in Alternate Encoding CAPEC-78 This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
  • Using UTF-8 Encoding to Bypass Validation Logic CAPEC-80 This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the "shortest possible" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.

Vulnerable Configurations

  • cpe:2.3:a:owasp:modsecurity:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.0:rc7:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.0:rc7:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:dev2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:dev2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:dev3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:dev3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.1:dev4:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.1:dev4:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.2:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.2:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.2:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.2:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.2:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.2:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.2:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.2:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.3:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.3:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.3:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.3:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.4:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.4:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.4:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.4:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.4:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.4:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.4:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.4:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.4:rc4:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.4:rc4:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.2.0:dev1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.2.0:dev1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.0:dev2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.0:dev2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.1:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.1:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.7:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.7:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.7:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.7:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.8:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.8:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.9:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.9:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.10:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.10:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.10:dev1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.10:dev1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.10:dev2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.10:dev2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.10:dev3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.10:dev3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.11:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.11:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.12:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.12:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.13:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.13:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.5.13:dev1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.5.13:dev1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.1:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.1:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.2:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.2:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.2:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.2:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.3:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.3:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.4:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.4:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.4:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.4:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.6.8:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.6.8:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.7.7:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.7.7:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.8.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.8.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.8.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.8.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.1:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.1:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.7:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.7:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.8:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.8:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.9:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.9:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.10:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.10:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.11:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.11:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:2.9.12:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:2.9.12:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:modsecurity:3.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:modsecurity:3.0.14:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-52747: 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-2026-16632 – A flaw has been found in boazsegev facil.io up to 0.7.4. Affected is the function websocket_on_protocol_error in the library lib/facil/http/parsers...
  • CVE-2026-16631 – A vulnerability was detected in publint up to 0.1.4. This impacts the function child_process.exec of the file src/node/pack.js of the component pac...
  • CVE-2026-61246 – Vulnerability in the Oracle Platform Security for Java product of Oracle Fusion Middleware (component: Centralized Thirdparty Jars). Supported ver...
  • CVE-2026-60455 – Vulnerability in the Oracle Platform Security for Java product of Oracle Fusion Middleware (component: Centralized Thirdparty Jars). Supported ver...
  • CVE-2026-60439 – Vulnerability in the Oracle Platform Security for Java product of Oracle Fusion Middleware (component: Centralized Thirdparty Jars). Supported ver...