CVE-2026-13410
OAuth2 TLS verification disabled in Dancer::Plugin::Auth::Google enables MITM login as any Google user.
Is CVE-2026-13410 being exploited?
Not confirmed. CVE-2026-13410 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-13410?
CVE-2026-13410 is rated High with a CVSS score of 8.2. 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-13410?
Yes. A fix has been recorded for CVE-2026-13410. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13410 affect?
CVE-2026-13410 affects Dancer::Plugin::Auth::Google <= 0.07, Perl Dancer web applications using this plugin, Apps using googleapis.com OAuth2 via this plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13410?
Upgrade plugin to patched version (>0.07) or re-enable TLS verification; restrict network access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An on-path attacker can forge access_tokens and user profile data to authenticate as arbitrary Google users on affected apps.
Immediate action required
- affected< 0.08
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.