CVE-2026-67345
OAuth redirect_uri validation flaw in MaxKey allows authorization code hijacking.
Is CVE-2026-67345 being exploited?
Not confirmed. CVE-2026-67345 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-67345?
CVE-2026-67345 is rated High with a CVSS score of 8.5. 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-67345?
Yes. A fix has been recorded for CVE-2026-67345. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67345 affect?
CVE-2026-67345 affects MaxKey <= 4.1.12, OAuth2 clients using MaxKey DefaultRedirectResolver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67345?
Upgrade to the commit fixing the issue (ddbb72f) or newer and enforce strict dot-boundary redirect_uri checks.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can supply crafted redirect_uri to receive victims' OAuth authorization codes and exchange them for access tokens, enabling account impersonation.
Immediate action required
- affected<= 4.1.12
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.