Widely used Atlassian Jira/Confluence/Bitbucket ecosystem; 2FA bypass via crafted User-Agent enables unauthorized access and admin abuse.
CVE-2026-12225
2FA bypass in Syracom Secure Login for Jira/Confluence/Bitbucket via crafted User-Agent.
Is CVE-2026-12225 being exploited?
Not confirmed. CVE-2026-12225 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-12225?
CVE-2026-12225 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-12225?
Yes. A fix has been recorded for CVE-2026-12225. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12225 affect?
CVE-2026-12225 affects Jira (Syracom Secure Login 3.4.0.x), Confluence (Syracom Secure Login 3.4.0.x), Bitbucket (Syracom Secure Login 3.4.0.x). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12225?
Upgrade to 3.5.0.0; review 2FA plugin configs and admin access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
2FA bypass lets attackers login with valid creds and access resources; admins can disable 2FA or modify settings.
Patch when possible
- affected3.4.0.0
- affected>= 3.4.0.0 and < 3.5.0.0
- affected>= 3.4.0.0 and < 3.5.0.0
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.