CVE-2021-39113Network attack vector

Cached-content disclosure via stale allowlist authorization

Published Aug 30, 2021 · Updated Oct 11, 2024

Broken access control in Atlassian Jira Server and Data Center allows remote attackers to view cached content after anonymous access is revoked. The allowlist cache continues returning previously permitted content after the underlying anonymous permission is removed, so authorization changes are not enforced for cached responses. Network access and content already cached under an anonymously allowed URL are required; the documented consequence is read-only disclosure, not modification or service interruption.

CVSS severity7.5
High
EPSS probability1.81%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Broken access control in Atlassian Jira Server and Data Center allows remote attackers to view cached content after anonymous access is revoked. The allowlist cache continues returning previously permitted content after the underlying anonymous permission is removed, so authorization changes are not enforced for cached responses. Network access and content already cached under an anonymously allowed URL are required; the documented consequence is read-only disclosure, not modification or service interruption.

The record

CVE
CVE-2021-39113
Published
Aug 30, 2021
Updated
Oct 11, 2024
Vendor
Atlassian
Product
Jira Server
Classifications
CWE-613, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 30, 2021CVE publishedPublication date reported by the CVE source.
  2. Oct 11, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <8.13.9
  2. Affected versionversion=8.14.0 <8.18.0
  3. Affected versionversion=8.14.0 <unspecified
  4. Affected versionversion=unspecified <8.13.9
  5. Affected versionversion=unspecified <8.18.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Atlassian · Jira Serverversion=0 <8.13.9; version=8.14.0 <8.18.0; version=8.14.0 <unspecified; version=unspecified <8.13.9; version=unspecified <8.18.0
Atlassian · Jira Data Centerversion=0 <8.13.9; version=8.14.0 <8.18.0; version=8.14.0 <unspecified; version=unspecified <8.13.9; version=unspecified <8.18.0

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N
7.5CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-613Insufficient Session Expiration
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo