CVE-2026-3321
Auth bypass via user-controlled key leaks Q&A history.
Is CVE-2026-3321 being exploited?
Not confirmed. CVE-2026-3321 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-3321?
CVE-2026-3321 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3321?
Not known from our data. No patch reference has been recorded for CVE-2026-3321, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What should I do about CVE-2026-3321?
Patch when available; restrict API access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated access exposes event IDs, private URLs and messages, enabling recon and potential lateral movement.
Patch when possible
- affected<= *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.