Privilege escalation in the Crash Reporting component

Why this deserves its current priority

A CVSS score is not reported in the current record. 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 15, 2026

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

2. Source modified

   Sep 15, 2026

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

3. First seen by HOL

   Sep 15, 2026

Sources and claim methodology

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

Related CVEs

• Consulting - Business, Finance WordPress Theme <= 6.7.16 - Authenticated (Subscriber+) Privilege Escalation via AJAXAlso CWE-269
• Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolutionAlso CWE-269
• Woodpecker: Privilege escalation via unrestricted serviceAccountName in the Kubernetes backendAlso CWE-269
• Privilege escalation in the Enterprise Policies componentAlso CWE-269