CVE-2021-39109 json
Path traversal in atlasboard
published 2021-09-01 5 y ago modified 2026-06-17 4 mo ago also GHSA-25pr-6pr6-68v7 , EUVD-2021-1946
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The renderWidgetResource resource in Atlasian Atlasboard before version 1.1.9 allows remote attackers to read arbitrary files via a path traversal vulnerability.
Patch / fix
- npm atlasboard 1.1.9
- Atlassian Atlasboard 1.1.9
- bitbucket.org/atlassian/atlasboard@9c03df0 commit
- bitbucket.org/atlassian/atlasboard#91 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.67% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | atlasboard | <1.1.9 |
1.1.9 |
Affected products
- Atlassian Atlasboard
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
bitbucket.org
/atlassian/atlasboard/commits/9c03df09f09399e2601010466e8ba3a28236eb9c
web, patch, vendor-advisory
-
bitbucket.org
/atlassian/atlasboard/pull-requests/91/buildeng-19379-apply-only-the-path
web
-
nvd.nist.gov
/vuln/detail/CVE-2021-39109
advisory
-
arxiv.org
/abs/2506.04962
web
-
arxiv.org
/pdf/2506.04962
web
-
bitbucket.org
/atlassian/atlasboard/src/master
web
Sources
- CVE List CVE-2021-39109
- GitHub Advisory GHSA-25pr-6pr6-68v7
- NVD CVE-2021-39109
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.