CVE-2026-21589 : 상세 정보

CVE-2026-21589

7.5
/
높음
2026-10-05
22h16 +00:00
A01-Broken Access Control
Network
2026-10-29
13h17 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions. Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents. In some configurations, there may be some sensitive files that make this highly severe. This vulnerability allows an unauthenticated remote attacker to access specific files within the web application root directory in affected versions. The vulnerability must be addressed for affected versions of: -- Bitbucket Data Center, introduced in version >= 4.6.0, fix versions: 9.4.26, 10.2.8, 10.5.1 -- Confluence Data Center, introduced in version >= 5.10.0, fix versions 9.2.26, 10.2.19 -- Crowd Data Center, introduced in version >= 2.11.0, fix versions 6.3.7, 7.0.3, 7.1.7, 7.2.4 -- Jira Software Data Center, introduced in version >= 7.1.0, fix versions 9.12.40, 10.3.26, 11.3.12 -- Jira Service Management Data Center, introduced in version >= 3.1.0, fix versions 5.12.40, 10.3.26, 11.3.12 -- Bamboo Data Center >= 7.0.1, fix versions 10.2.24, 12.1.12 -- Crucible, fix versions 4.9.15 -- Fisheye, fix version 4.9.15 -- Exploitation requires prior knowledge of the target file's exact name and path. The vulnerability does not include the capability to enumerate or list directory contents.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-552 Files or Directories Accessible to External Parties
The product makes files or directories accessible to unauthorized actors, even though they should not be.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

nvd@nist.gov

CISA KEV (알려진 악용 취약점)

취약점 이름 : Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability

필요한 조치 : Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

랜섬웨어 캠페인에 사용된 것으로 알려진 취약점 : Unknown

추가됨 : 2026-10-15 00h00 +00:00

조치 기한 : 2026-10-18 00h00 +00:00

중요 정보
이 CVE는 CISA KEV에 따라 활성화된 위협을 제기하는 것으로 식별되었습니다. 잠재적 사이버 공격으로부터 시스템을 보호하기 위해 이 CVE의 업데이트 및 수정을 우선 처리하세요.

언급된 제품

구성 0

Atlassian>>Bitbucket_data_center >> Version 부터 (포함) 7.17.0 까지 (미포함) 9.4.26

Atlassian>>Bitbucket_data_center >> Version 부터 (포함) 9.5.0 까지 (미포함) 10.2.8

Atlassian>>Bitbucket_data_center >> Version 부터 (포함) 10.3.0 까지 (미포함) 10.5.1

Atlassian>>Bitbucket_server >> Version 부터 (포함) 4.6.0 까지 (포함) 8.14.6

구성 0

Atlassian>>Confluence_data_center >> Version 부터 (포함) 5.10.0 까지 (미포함) 9.2.26

Atlassian>>Confluence_data_center >> Version 부터 (포함) 9.3.0 까지 (미포함) 10.2.19

구성 0

Atlassian>>Crowd >> Version 부터 (포함) 2.11.0 까지 (미포함) 6.3.7

Atlassian>>Crowd >> Version 부터 (포함) 7.0.0 까지 (미포함) 7.0.3

Atlassian>>Crowd >> Version 부터 (포함) 7.1.0 까지 (미포함) 7.1.7

Atlassian>>Crowd >> Version 부터 (포함) 7.2.0 까지 (미포함) 7.2.4

구성 0

Atlassian>>Jira_data_center >> Version 부터 (포함) 7.1.0 까지 (미포함) 9.12.40

Atlassian>>Jira_data_center >> Version 부터 (포함) 9.13.0 까지 (미포함) 10.3.26

Atlassian>>Jira_data_center >> Version 부터 (포함) 10.4.0 까지 (미포함) 11.3.12

구성 0

Atlassian>>Jira_service_desk >> Version 부터 (포함) 3.1.0 까지 (포함) 4.13.27

Atlassian>>Jira_service_management >> Version 부터 (포함) 4.14.0 까지 (미포함) 5.12.40

Atlassian>>Jira_service_management >> Version 부터 (포함) 5.13.0 까지 (미포함) 10.3.26

Atlassian>>Jira_service_management >> Version 부터 (포함) 10.4.0 까지 (미포함) 11.3.12

구성 0

Atlassian>>Bamboo >> Version 부터 (포함) 7.0.1 까지 (미포함) 10.2.24

Atlassian>>Bamboo >> Version 부터 (포함) 11.0.0 까지 (미포함) 12.1.12

구성 0

Atlassian>>Crucible >> Version 까지 (미포함) 4.9.15

구성 0

Atlassian>>Fisheye >> Version 까지 (미포함) 4.9.15

참고 자료

https://jira.atlassian.com/browse/BAM-26567
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/BSERV-20604
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/CONFSERVER-104488
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/CRUC-8741
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/CWD-6610
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/FE-7583
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/JRASERVER-79546
Tags : Issue Tracking, Mitigation, Vendor Advisory
https://jira.atlassian.com/browse/JSDSERVER-16809
Tags : Issue Tracking, Mitigation, Vendor Advisory