CVE-2021-26077 — atlassian-connect-spring-…
HIGHCVE-2021-26077 is a high-severity (CVSS 8.8) Improper Authentication vulnerability in com.atlassian.connect:atlassian-connect-spring-boot. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.atlassian.connect:atlassian-connect-spring-boot — see the affected versions and patch details below.
Improper Authentication in Atlassian Connect Spring Boot
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-26077.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-26077 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
com.atlassian.connect:atlassian-connect-spring-boot☕com.atlassian.connect:atlassian-connect-spring-bootReal-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) in version 1.1.0 before 2.1.3 and from version 2.1.4 before 2.1.5: 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 1.1.0 before 2.1.3 and versions 2.1.4 before 2.1.5 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.atlassian.connect:atlassian-connect-spring-boot | ≥ 1.1.0&&< 2.1.3 | 2.1.3com.atlassian.connect:atlassian-connect-spring-boot:2.1.3 |
| ☕Maven | com.atlassian.connect:atlassian-connect-spring-boot | ≥ 2.1.4&&< 2.1.5 | 2.1.5com.atlassian.connect:atlassian-connect-spring-boot:2.1.5 |
Affected Products
connect spring bootatlassianResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.atlassian.connect:atlassian-connect-spring-boot, 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 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-26077 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
Is CVE-2021-26077 in your dependencies?
Find it across Maven, including transitive dependencies.