Home

Description

syracom AG Secure Login (2FA) for Atlassian Jira, Confluence, and Bitbucket 3.4.0.x contains an authentication bypass vulnerability. An attacker with valid credentials for a user account can bypass the two-factor authentication flow by sending HTTP requests with a crafted User-Agent header containing specific strings such as AtlassianMobileApp or JIRA. When such a User-Agent is present, the plugin does not enforce the configured 2FA checks for protected web resources. Successful exploitation allows the attacker to access the affected Atlassian application as the compromised user without completing 2FA. If the compromised account has administrative privileges, the attacker can access administrative functionality and may disable the 2FA plugin or make arbitrary administrative changes. The issue is fixed in version 3.5.0.0.

PUBLISHED Reserved 2026-06-14 | Published 2026-06-16 | Updated 2026-06-16 | Assigner SEC-VLab




HIGH: 8.7CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Problem types

CWE-288 Authentication bypass using an alternate path or channel

Product status

Default status
unaffected

3.4.0.0 (custom) before 3.5.0.0
affected

Default status
unaffected

3.4.0.0 (custom) before 3.5.0.0
affected

Default status
unaffected

3.4.0.0 (custom)
affected

Credits

Laurentius von Oppenkowski, SEC Consult Vulnerability Lab finder

Timo Müller, SEC Consult Vulnerability Lab finder

References

marketplace.atlassian.com/...secure-login-2fa-for-confluence product

syracom-bee.atlassian.net/...dvisory+-+Broken+Access+Control vendor-advisory

syracom-bee.atlassian.net/...does+not+work+with+Secure+Login mitigation

r.sec-consult.com/syracom third-party-advisory

cve.org (CVE-2026-12225)

nvd.nist.gov (CVE-2026-12225)

Download JSON