CVE-2026-21876 Vulnerability Analysis & Exploit Details

CVE-2026-21876
Vulnerability Scoring

9.3
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-21876 has severe implications, demanding immediate intervention.

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-21876 Details

Status: Analyzed

Last updated: 🕡 23 Feb 2026, 18:33 UTC
Originally published on: 🕑 08 Jan 2026, 14:15 UTC

Time between publication and last update: 46 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:H/I:L/A:N

CVE-2026-21876 Vulnerability Summary

CVE-2026-21876: The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls. Prior to versions 4.22.0 and 3.3.8, the current rule 922110 has a bug when processing multipart requests with multiple parts. When the first rule in a chain iterates over a collection (like `MULTIPART_PART_HEADERS`), the capture variables (`TX:0`, `TX:1`) get overwritten with each iteration. Only the last captured value is available to the chained rule, which means malicious charsets in earlier parts can be missed if a later part has a legitimate charset. Versions 4.22.0 and 3.3.8 patch the issue.

Assessing the Risk of CVE-2026-21876

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2026-21876 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-21876, 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-21876, 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-2026-21876 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2026-21876 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-21876 does not impact system availability.

CVE-2026-21876 References

External References

CWE Common Weakness Enumeration

CWE-794

Vulnerable Configurations

  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:2.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:owasp:owasp_modsecurity_core_rule_set:3.3.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-21876: 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-3395 – A flaw has been found in MaxSite CMS up to 109.1. This impacts the function eval of the file application/maxsite/admin/plugins/editor_markitup/prev...
  • CVE-2026-3394 – A vulnerability was detected in jarikomppa soloud up to 20200207. This affects the function SoLoud::Wav::loadwav of the file src/audiosource/wav/so...
  • CVE-2026-3393 – A security vulnerability has been detected in jarikomppa soloud up to 20200207. The impacted element is the function SoLoud::Wav::loadflac of the f...
  • CVE-2026-3392 – A weakness has been identified in FascinatedBox lily up to 2.3. The affected element is the function eval_tree of the file src/lily_emitter.c. This...
  • CVE-2026-3391 – A security flaw has been discovered in FascinatedBox lily up to 2.3. Impacted is the function clear_storages of the file src/lily_emitter.c. The ma...