Security readout for executives and security teams
Plain-English summary
Authenticated Jira users could make Jira reveal the full path to its application data directory through an error message. This is not described as code execution or data theft, but path disclosure can help an attacker map the environment for later attacks.
Executive priority
Treat as a routine Jira hygiene fix unless combined with broader Jira exposure or untrusted user access. Prioritize alongside other Jira patching because disclosed filesystem paths can support follow-on attacks.
Technical view
CVE-2021-26075 affects the Jira importers plugin AttachTemporaryFile REST resource in Jira Server and Data Center. In affected versions, an invalid filename could trigger an error message disclosing the full Jira application data directory path to a remote authenticated attacker.
Likely exposure
Exposure is limited to Jira Server and Jira Data Center instances in the affected version ranges where an attacker has valid authentication. Cloud products are not named in the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, exploit code, or unauthenticated exploitation. The known impact is information disclosure through an error message.
Researcher notes
Evidence supports authenticated information disclosure only. No CVSS, CWE, exploit status, or deeper technical root cause is included in the provided bundle, so avoid overstating impact beyond path disclosure.
Mitigation direction
- Upgrade Jira 8.5.x to 8.5.12 or later.
- Upgrade Jira 8.6.x through 8.13.x to 8.13.4 or later.
- Upgrade Jira 8.14.x to 8.15.1 or later.
- Restrict Jira access to trusted authenticated users where feasible.
- Check Atlassian guidance for branch-specific remediation details.
Validation and detection
- Inventory Jira Server and Data Center versions.
- Confirm whether deployed versions fall within the affected ranges.
- Verify the Jira importers plugin is covered by the installed fixed Jira release.
- Review access logs for unusual authenticated importer attachment activity.
- Document remediation status and remaining unsupported versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-26075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-72316CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.