Data CenterApplication · Atlassian
CVE-2021-26070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAffected versions of Atlassian Jira Server and Data Center allow remote attackers to evade behind-the-firewall protection of app-linked resources via a Broken Authentication vulnerability in the `makeRequest` gadget resource. The affected versions are before version 8.13.3, and from version 8.14.0 before 8.14.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a broken authentication vulnerability in Atlassian Jira Server and Data Center's `makeRequest` gadget resource. Attackers can exploit this flaw to bypass firewall protections and access internal resources that should be restricted. The vulnerability affects specific versions before 8.13.3 and between 8.14.0 and 8.14.1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Data CenterApplication
< 8.13.3>= 8.14.0, < 8.14.1
JiraApplication
< 8.13.3
Jira ServerApplication
>= 8.14.0, < 8.14.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jira installation versionAccess Jira administration panel and navigate to "About" (or check the /about.jspa endpoint), or look for the version in the installation directory's atlassian-jira/version.properties fileAffected if The installed version is less than 8.13.3, OR between 8.14.0 and 8.14.1 (exclusive of 8.14.1)
-
Confirm product typeDetermine whether the installation is Jira Server, Jira Data Center, or Jira (Cloud is not affected). Check the "About" page or installation artifacts for the product editionAffected if The product is Jira Server, Jira Data Center, or Jira (not Cloud) and the version falls within the affected ranges
-
Verify makeRequest gadget accessibilityAttempt to access the gadget resource endpoint typically found at /rest/gadget/1.0/makeRequest, or check if the gadget framework is enabled in the Jira administration under "Gadgets" or "Dashboard" settingsAffected if The gadget framework is enabled and accessible without proper authentication on the makeRequest endpoint
A user is affected if their Jira Server or Data Center version is below 8.13.3 or falls between 8.14.0 and 8.14.1, and the gadget framework (specifically the makeRequest resource) is accessible to unauthenticated or unauthorized users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data8.13.38.14.1
Upgrade Jira Server or Data Center to version 8.13.3, 8.14.1, or later to patch the broken authentication vulnerability in the makeRequest gadget resource.
Fix this in Data Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data