Use-after-free in the CSS Parsing and Computation component

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

1. 1Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

1. Published upstream

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 29, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 29, 2026

Sources and claim methodology

• Source referencebugzilla.mozilla.org
• Source referencemozilla.org
• Source referencemozilla.org

Related CVEs

• Sandbox escape due to use-after-free in the DOM: Core & HTML componentAlso CWE-416
• Sandbox escape due to use-after-free in the Widget: Gtk componentAlso CWE-416
• Use-after-free in the JavaScript Engine: JIT componentAlso CWE-416
• Use-after-free in the DOM: UI Events & Focus Handling componentAlso CWE-416
• Use-after-free in the Graphics: Canvas2D componentAlso CWE-416
• PyPy pyexpat ExternalEntityParserCreate Use-After-FreeAlso CWE-416