How severe is CVE-2021-26074?

CVE-2021-26074 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

How do I fix CVE-2021-26074?

Update com.atlassian.connect:atlassian-connect-spring-boot-starter to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-26074 is resolved across your whole dependency graph.

How do I detect CVE-2021-26074 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.atlassian.connect:atlassian-connect-spring-boot-starter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-26074 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2021-26074 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-26074 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-26074?

CVE-2021-26074 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-26074?

CVE-2021-26074 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-26074 published, and has it been updated?

CVE-2021-26074 was published on May 10, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2021-26074 — atlassian-connect-spring-…

MEDIUM

CVE-2021-26074 is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in com.atlassian.connect:atlassian-connect-spring-boot-starter. A fix is available for com.atlassian.connect:atlassian-connect-spring-boot-starter — see the affected versions and patch details below.

Broken Authentication in Atlassian Connect Spring Boot

Published

May 10, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2021-26074.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-26074 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.atlassian.connect:atlassian-connect-spring-boot-starter

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Broken Authentication in Atlassian Connect Spring Boot (ACSB) from version 1.1.0 before version 2.1.3: Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions from version 1.1.0 before version 2.1.3 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.atlassian.connect:atlassian-connect-spring-boot-starter`	≥ 1.1.0&&< 2.1.3	2.1.3`com.atlassian.connect:atlassian-connect-spring-boot-starter:2.1.3`

Affected Products

1 product · 1 configurations

Application

connect spring bootatlassian

≥ 1.1.0 && < 2.1.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.atlassian.connect:atlassian-connect-spring-boot-starter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.atlassian.connect:atlassian-connect-spring-boot-starter to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-26074 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Broken Authentication in Atlassian Connect Spring Boot (ACSB) from version 1.1.0 before version 2.1.3. Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Spring Boot versions between 1.1.0 - 2.1.2 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to

O3 Security · Impact-Aware SCA

Is CVE-2021-26074 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-287Improper Authentication

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

May 10, 2021

Last updated

Nov 8, 2023

Identifiers

CVE-2021-26074

References

Advisorynvd.nist.gov Webcommunity.developer.atlassian.com Webconfluence.atlassian.com

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs with CWE-287 are rated as high or higher (top: critical).

CVE-2026-63472CVE-2026-85716CVE-2026-56666CVE-2026-59151CVE-2026-88007CVE-2026-87016CVE-2026-88018CVE-2026-62669Browse all CWE-287

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

CVE-2021-26074 — atlassian-connect-spring-…

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-26074 in your dependencies?