Hispasec•October 7, 2026•🇪🇸Translated from Spanish

Attackers Exploit Critical Atlassian Data Center Flaw CVE-2026-21589 Hours After PoC Release

Exploitation attempts against the critical vulnerability CVE-2026-21589 in Atlassian Data Center products began within hours of a public proof-of-concept release. The flaw permits unauthenticated reading of specific files and, in environments integrated with Crowd, can lead to privilege escalation up to administrator rights.

The defect affects a wide range of Atlassian Data Center deployments, including Bitbucket Data Center, Confluence Data Center, Jira Software Data Center, Jira Service Management Data Center, Bamboo Data Center, Crowd Data Center, Crucible, and Fisheye. It received a CVSS v4.0 score of 9.3 from Atlassian. The availability of a Nuclei template has lowered the barrier for large-scale automated scanning.

The vulnerability does not allow directory enumeration. Attackers must already know the exact file name and path. It exploits how a shared web resource library converts double-colon sequences into path separators, enabling path traversal requests against plugin resource endpoints.

The most severe scenario occurs when Jira is integrated with Crowd. Reading WEB-INF/classes/crowd.properties can expose plaintext credentials in certain configurations, allowing an attacker to create accounts and gain administrator privileges through the Crowd API.

Atlassian recommends applying fixed versions immediately, removing affected instances from the internet, or restricting external access. Additional mitigations include deploying WAF rules or enabling Tomcat RewriteValve with rewrite rules to block traversal patterns in Confluence, Jira, Jira Service Management, Bamboo, and Crowd. For Bitbucket Data Center the equivalent configuration is applied in urlrewrite.xml.

Administrators hunting for prior activity should examine access logs after double URL decoding and search for sequences containing .. combined with /, \, or ::, or apply the vendor-supplied search expression. If logs show access to sensitive configuration files, organizations must rotate credentials, strengthen network controls, and consider IP allow-listing in Crowd.

Related articles

Habr•Vulnerabilities & Exploits

Zero-Day Vulnerabilities: The Invisible Threats Lurking in Modern Software

Zero-Day vulnerabilities represent one of the most challenging problems in cybersecurity because developers have no time to prepare defenses before exploitation begins. These flaws exist in software components without the knowledge of vendors, leaving antivirus tools and existing security mechanisms unable to detect attacks. Researchers discover such issues through techniques including fuzzing, reverse engineering, and static analysis. High-profile examples such as Heartbleed in OpenSSL, EternalBlue in Windows SMB, and Log4Shell in the Log4j library illustrate how single errors can affect millions of systems worldwide. Bug Bounty programs now allow companies to harness independent researchers to find problems before criminals exploit them. Organizations can reduce risk through regular updates, least-privilege principles, multi-factor authentication, and layered defenses, though complete elimination of zero-day risk remains impossible.

Habr•Vulnerabilities & Exploits

11-Year-Old Linux Kernel Race Condition NoisyTCP (CVE-2026-99288) Enables Remote DoS on Nginx, Apache and SSH Servers

Security researcher Hyunwoo Kim disclosed NoisyTCP (CVE-2026-99288), an 11-year-old race condition in the Linux kernel networking stack that allows unauthenticated remote attackers to trigger kernel panics and crash servers. The flaw stems from concurrent access to the ehash table during TCP socket lookup, where one CPU context may dereference a freed request_sock or full socket while another reuses the memory via SYN cookies. Exploitation requires multiple RX queues or RPS enabled and succeeds reliably on virtualized environments within seconds to minutes. Affected systems include nearly all distributions running kernels from 4.4 onward until the fix landed in November 2026. Temporary mitigations involve disabling SYN cookies or restricting traffic to a single RX queue, though both reduce resilience or performance. The researcher published full technical details on GitHub after coordinated disclosure.

BoletimSec•Vulnerabilities & Exploits

Check Point Gateways Hit by PHP2Shell Exploits Installing TSGA Backdoor via Chained CVEs

An unidentified threat actor has been actively exploiting known vulnerabilities in unpatched Check Point Security Gateways to deploy the TSGA backdoor. The campaign began on 30 October 2026 against Israeli organizations and expanded on 2 November to targets across multiple countries and industries. Initial access leveraged CVE-2026-109618 and CVE-2026-109619 in exposed Mobile Access portals, followed by local privilege escalation through the previously unknown CVE-2026-123039 in Gaia OS. Attackers then installed PHP web shells and the TSGA backdoor, which provides encrypted remote access, configuration theft, persistence mechanisms, and log tampering via the embedded TSProxy component. In the first wave, operators pivoted to VMware ESXi hosts and deployed the destructive wiper destroy_v6. While tooling overlaps with the China-linked Armory Castle group’s PhiliKit framework, the use of a wiper and references to the Israel-Palestine conflict leave attribution open to three scenarios.

Security NEXT•Vulnerabilities & Exploits

Apache Shiro Authentication Bypass Vulnerability Disclosed, Fixed in August Update

A critical authentication bypass vulnerability has been identified in the Java security framework Apache Shiro under specific LDAP caching configurations. The flaw, tracked as CVE-2026-129349, affects versions prior to 3.0.0 and carries a CVSSv4.0 base score of 9.1, rated Critical. Once a valid user authenticates successfully, subsequent login attempts using the cache accept any password for that username, enabling impersonation attacks. The Apache Shiro development team disclosed the issue on November 14, 2026, noting that the vulnerability was already resolved in version 3.0.1 released in August 2026. Version 3.0.2 was made available on November 8, 2026, and users are urged to upgrade immediately to the latest release.