CVE-2026-48612
OAuth state verification flaw allows account linking to attacker.
Is CVE-2026-48612 being exploited?
Not confirmed. CVE-2026-48612 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.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-48612?
CVE-2026-48612 is rated High with a CVSS score of 8.0. 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-48612?
Not known from our data. No patch reference has been recorded for CVE-2026-48612, 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 does CVE-2026-48612 affect?
CVE-2026-48612 affects OAuth-enabled apps, Auth services with weak state verification. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48612?
Fix state validation; bind OAuth to sessions; rotate tokens after fix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can cause victim's account to be linked to attacker-controlled account, enabling account takeover.
Patch when possible
- affected>= 3.3.0 and <= 3.3.16
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.