# CVE-2026-12225: syracom Secure Login (2FA) for Confluence allows 2FA bypass via spoofed User-Agent

> Attackers with valid credentials can bypass two-factor authentication by spoofing specific User-Agent headers, potentially gaining administrative access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2026
- **Updated:** 21 Jun 2026
- **Also known as:** GHSA-xfw8-8p99-43jw

## What is CVE-2026-12225?

CVE-2026-12225 is a high-severity authentication bypass vulnerability in syracom AG Secure Login (2FA) for Bitbucket, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-12225?


## How do I fix CVE-2026-12225?

No fix has been published for CVE-2026-12225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12225 being exploited?

There is no known exploitation of CVE-2026-12225 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12225 and fix it if it is affected.

What it is: CVE-2026-12225 is a high-severity authentication bypass vulnerability in syracom AG Secure Login (2FA) for Bitbucket, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12225 in the wild and no public exploit code.

Affected product: syracom AG Secure Login (2FA) for Bitbucket. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12225/ (Markdown: https://insights.sbomify.com/CVE-2026-12225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12225
- OSV: https://osv.dev/vulnerability/CVE-2026-12225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12225/
Summaries are generated and may contain mistakes; the official description above is the record.