CVE-2026-12225

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-37066 (ENISA EUVD) · GHSA-xfw8-8p99-43jw (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 16, 2026

Last Modified

June 21, 2026

Advisory Details (4)

Auto-updated Jun 16, 2026
Fix named in the CVE record.
Web page
https://syracom-bee.atlassian.net/wiki/spaces/SL/pages/4230217729/Mobile+app+login+does+not+work+with+Secure+Login
Web page
https://syracom-bee.atlassian.net/wiki/spaces/SL/pages/4193255427/2026-05-11+-+Secure+Login+security+advisory+-+Broken+Access+Control
Web page

Broken Access Control in syracom AG Secure Login (2FA) for Atlassian Jira / Confluence / Bitbucket - SEC Consult

https://r.sec-consult.com/syracom
Web page

Secure Login (2FA) for Confluence | Atlassian Marketplace

https://marketplace.atlassian.com/apps/1214491/secure-login-2fa-for-confluence

Vendor Advisories for CVE-2026-12225(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 280 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 180 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-31 07:43 UTCEG score recompute
  5. 2026-10-31 07:42 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 14:49 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-24 13:17 UTCEG score recompute
  15. 2026-10-24 13:17 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-18 05:04 UTCEG score recompute
  23. 2026-10-17 18:52 UTCEG score recompute
  24. 2026-10-17 18:52 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  25. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-12 16:36 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-11 20:12 UTCEG score recompute
  8. 2026-10-11 18:24 UTCEG score recompute
  9. 2026-10-11 14:58 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-09-14 03:33 UTCEG score recompute
  29. 2026-09-14 03:33 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  30. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-08-30 22:50 UTCEG score recompute
  43. 2026-08-30 22:50 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  44. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-24 23:26 UTCEG score recompute
  50. 2026-08-24 23:26 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  51. 2026-08-23 21:40 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  52. 2026-08-23 09:29 UTCEG score recompute
  53. 2026-08-23 09:29 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  54. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-08-21 22:36 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  57. 2026-08-21 09:46 UTCEG score recompute
  58. 2026-08-21 09:46 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  59. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-08-20 20:46 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  61. 2026-08-20 08:34 UTCEG score recompute
  62. 2026-08-20 08:34 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  63. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-19 13:09 UTCEG score recompute
  65. 2026-08-19 13:08 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  66. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-08-17 11:56 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  68. 2026-08-16 23:45 UTCEG score recompute
  69. 2026-08-16 23:45 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  70. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  71. 2026-08-16 11:33 UTCEG score recompute
  72. 2026-08-16 11:33 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  73. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  74. 2026-08-15 23:22 UTCGHSA enrichmentGHSA-xfw8-8p99-43jw · GitHub severity HIGH
  75. 2026-08-15 11:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12225?
CVE-2026-12225 is a high-severity vulnerability; its CVE record was published on June 16, 2026. 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…
When was the CVE record for CVE-2026-12225 published?
The CVE record for CVE-2026-12225 was published on June 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 21, 2026; the record at its source may have been updated since.
Is CVE-2026-12225 actively exploited?
CVE-2026-12225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12225?
CVE-2026-12225 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12225?
The CVE record for CVE-2026-12225 names the fix: "The issue is fixed in version 3.5.0.0." The vendor advisories EchelonGraph has for CVE-2026-12225 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12225

Explore →

Is Your Infrastructure Affected by CVE-2026-12225?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs