PatchTheCVEBlog · 2-hour update · 2026-10-26
CVE-2026-21589 Atlassian Bitbucket Data Center: exploited in the wild, how to patch
By the PatchTheCVE security team · Updated 2026-10-26 · Data from NVD, CISA KEV, EPSS and vendor advisories
High severity (CVSS 7.5), exploited in the wild, remotely exploitable, no login needed. Recommended action: upgrade to 9.4.26, 10.2.8, 10.5.1.
On 26 October 2026, 39 new CVEs were published that we track: 0 critical, 1 already exploited in the wild (CISA KEV) and 0 with a fix or vendor patch available. Each one is ranked by severity, exploitation signals and how easy it is to reach, so you can patch the right ones first.
Key takeaways
- Most urgent: CVE-2026-21589 (Atlassian Bitbucket Data Center): upgrade to 9.4.26, 10.2.8, 10.5.1.
- 1 exploited in the wild (CISA KEV): patch these before anything else.
- 5 of the top 8 can be attacked over the network without a login.
- 0 of 39 new CVEs already have a fix or vendor patch.
What happened in this 2-hour window: the most serious item is CVE-2026-21589 in bitbucket data center (high, CVSS 7.5, priority 89/100). Recommended action: upgrade to 9.4.26, 10.2.8, 10.5.1. 1 new CVE from the list below is already being exploited (CVE-2026-21589), so those go first. 5 of the 8 top items can be attacked remotely without a login. 0 of 39 new CVEs already have a fix or vendor patch; for the other 39, follow the downgrade or mitigation steps until one ships.
Patch these first
CVE-2026-21589: Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability
- Risk: High (CVSS 7.5), priority 89/100 (patch now)
- Exploitation: exploited in the wild (CISA KEV); attackable over the network without a login
- Affected: atlassian bitbucket data center
- What to do: upgrade to 9.4.26, 10.2.8, 10.5.1 for atlassian bitbucket data center
Why it ranks here: high severity; epss top 1%: very likely to be exploited; exploited in the wild (cisa kev).
References: NVD · Issue Tracking, Mitigation · Issue Tracking, Mitigation
CVE-2026-116257: A vulnerability was determined in BillaBear up to 2025.01.03
- Risk: High (CVSS 7.3), priority 31/100 (routine)
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-116256: A vulnerability was found in geesondog RhaPHP up to 7ae639ccf8dcb627faace096d030bd4cb4cfb905
- Risk: High (CVSS 7.3), priority 31/100 (routine)
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-116253: A vulnerability was determined in DedeCMS 5.7.118
- Risk: High (CVSS 7.3), priority 31/100 (routine)
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-115948: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in David Li
- Risk: High (CVSS 8.5), priority 30/100 (routine)
- What to do: apply the vendor mitigation
Why it ranks here: high severity.
References: NVD
CVE-2026-115608: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Crocoblo
- Risk: High (CVSS 8.5), priority 30/100 (routine)
- What to do: apply the vendor mitigation
Why it ranks here: high severity.
References: NVD
CVE-2026-116237: A vulnerability was found in Oray Pugongying X5 Pro 7.6.1
- Risk: High (CVSS 8.4), priority 29/100 (routine)
- What to do: apply the vendor mitigation
Why it ranks here: high severity.
References: NVD
CVE-2026-116254: A vulnerability was identified in rathena FluxCP up to 98cd4b8fd83228c11b36fb3d097b8e0f7c105a8d
- Risk: Medium (CVSS 6.5), priority 28/100 (routine)
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: remotely exploitable, no login, no user action.
References: NVD
How to act on this list
- Start with anything marked exploited or patch now.
- Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
- Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
- Verify afterwards. Distros often fix a flaw without changing the upstream version, here is how to confirm.
FAQ
What is the most serious vulnerability published on 26 October 2026?
CVE-2026-21589 (Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability) ranks highest, with a priority score of 89/100. Recommended action: upgrade to 9.4.26, 10.2.8, 10.5.1.
Are any of the new CVEs exploited in the wild?
Yes, 1 of the new CVEs appear on the CISA Known Exploited Vulnerabilities list. Patch those first.
Should I downgrade if there is no fix yet?
Only when an older release is confirmed unaffected and the package is not a core system component. Downgrades can break dependent software, so test first and hold the package until a fix ships.
Sources
- NIST National Vulnerability Database: CVE details and affected versions
- CVE Program: official CVE records
- CISA Known Exploited Vulnerabilities catalog: exploitation in the wild
- FIRST EPSS: exploit probability
- Distribution and vendor advisories linked under each item.