CVE-2012-2926

CRITICAL

9.1

CVSS Score

Published: May 22, 2012 at 03:00 PM UTC

Updated: June 16, 2026 at 11:42 PM UTC

7 products affected across 1 vendorJiraConfluence ServerCrucible

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

CRITICAL9.1

Exploit prediction

EPSS 66%

Description

Atlassian JIRA before 5.0.1; Confluence before 3.5.16, 4.0 before 4.0.7, and 4.1 before 4.1.10; FishEye and Crucible before 2.5.8, 2.6 before 2.6.8, and 2.7 before 2.7.12; Bamboo before 3.3.4 and 3.4.x before 3.4.5; and Crowd before 2.0.9, 2.1 before 2.1.2, 2.2 before 2.2.9, 2.3 before 2.3.7, and 2.4 before 2.4.1 do not properly restrict the capabilities of third-party XML parsers, which allows remote attackers to read arbitrary files or cause a denial of service (resource consumption) via unspecified vectors.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Bamboo · Atlassianatlassian-app

95%

v < 3.3.43.4 ≤ v < 3.4.5

Affected range stops below 3.3.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.4.5, so it looks safe — our inference, not a vendor statement

Confluence · Atlassianatlassian-app

95%

v < 3.5.16

Affected range stops below 3.5.16, so it looks safe — our inference, not a vendor statement

Confluence Server · Atlassianatlassian-app

95%

4.0 ≤ v < 4.0.74.1 ≤ v < 4.1.10

Affected range stops below 4.0.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.1.10, so it looks safe — our inference, not a vendor statement

Crowd · Atlassianatlassian-app

95%

v < 2.0.92.1 ≤ v < 2.1.22.2.0 ≤ v < 2.2.92.3.0 ≤ v < 2.3.72.4.0 ≤ v < 2.4.1

Affected range stops below 2.0.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.4.1, so it looks safe — our inference, not a vendor statement

Crucible · Atlassianatlassian-app

95%

v < 2.5.82.6 ≤ v < 2.6.82.7 ≤ v < 2.7.12

Affected range stops below 2.5.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.6.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.7.12, so it looks safe — our inference, not a vendor statement

Fisheye · Atlassianatlassian-app

95%

v < 2.5.82.6 ≤ v < 2.6.82.7 ≤ v < 2.7.12

Affected range stops below 2.5.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.6.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.7.12, so it looks safe — our inference, not a vendor statement

Jira · Atlassianatlassian-app

95%

v < 5.0.1

Affected range stops below 5.0.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references