The pattern names the shape where correcting a wrong affected-versions field on an existing CVE is, in the catalog's own grammar, impossible. Once a CNA publishes a CVE record, the affected-products and affected-versions fields are frozen. The immutability is deliberate. Downstream consumers (NVD's CPE match rules, CISA's KEV catalog, vulnerability scanners, SBOM tools) read each record as authoritative and merge it into their own data at CVE-ID granularity; a mutable scope field would make every prior scanner result an unprovenanced claim. The side effect is that a scope that was wrong on the day of publication remains wrong afterward, and the only legitimate remedy inside the protocol is another number.
The correction protocol issues a second CVE. A second identifier is assigned, a second advisory is written, a second affected-versions field is populated. The second record takes the range the first record missed. Because the two records cannot overlap, overlapping would mean one host matches two CVE identifiers for one bug, which breaks CVE-ID-granular counting in every downstream pipeline, the second record's range stops short of the first record's version by strict inequality. NVD translates the advisory phrasing ("4.0.0 before 6.1.5") into a CPE match rule with versionEndExcluding set to the first record's version. The CPE grammar is explicit that the bound is open; the version named in the field is not in the range the record covers. Automated scanners honour the openness.
Three downstream effects compose. First, administrators reading the second record alone see a false negative for the version the first record covered. The second record's text names the excluded version only to exclude it; nothing else inside the record points at the first. Second, downstream processors that operate at CVE-ID granularity attach exploitation notes, patch deadlines, and severity scores to one CVE at a time. When only one of the two records carries the "actively exploited" language, only that record lands in KEV, and the version only the other record covers is invisible to patch-deadline enforcement. Third, research write-ups, PoC READMEs, and mitigation guides written against the second record propagate its range without re-reading the first; the gap between the records reinforces itself in downstream text.
The Apache Roller exhibit grounds the shape. CVE-2026-82384 named Roller 6.1.5 as affected, following the CNA shorthand of "the version the researcher reported against is the version that got patched." CVE-2026-129448, issued seven weeks later, named "Apache Roller 4.0.0 before 6.1.5" and included the explicit note "This is the same vulnerability as CVE-2026-82384. This issue is being actively exploited." NVD resolved the November advisory into a CPE match with versionEndExcluding: 6.1.5. CISA added the November record to the Known Exploited Vulnerabilities catalog on 20 November with a three-day patch deadline. CISA did not add the September record. The web.xml servlet declaration that enables the vulnerable code path was written in 2007 by the same author who shipped Roller 4.0 and is byte-identical across every release tag from roller-4.0 through roller-6.1.5. The code says "every version since 2007." The catalog says "one version in record A, every other version in record B, and the exclusion between them is a strict inequality that an automated scanner will respect."
The mechanism distinguishes itself from near classes on the axis of why the record understates. Scope Is Support Status names the shape where the affected-versions line encodes a vendor's end-of-support matrix rather than the code's reach; the understatement is a business decision expressed in catalog grammar. CVE Scope Is The Patcher names the shape where the record names the fork that triaged the report and omits the upstream shipping the byte-identical code; the understatement is a maintainer-coordination artefact. Scope-correction-by-reissue is the shape where the catalog protocol itself, once a wrong number has been recorded, forecloses an edit and requires a new number whose range is non-overlapping by construction. The understatement persists because the correction protocol is working as designed. The protocol's job is to preserve the audit trail. The side effect is a strict inequality in the middle of the population at risk.