Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:maven/Apache Software Foundation/org.apache.shiro:shiro-core

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

CVE-2026-49268 is a high-severity LDAP injection vulnerability in Apache Shiro's DefaultLdapRealm class. It allows remote attackers to inject LDAP special characters into the Distinguished Name (DN) construction by concatenating user-supplied usernames without proper escaping. This can lead to manipulation of the LDAP DN used for bind authentication, potentially enabling authentication bypass or user impersonation. The vulnerability affects all Apache Shiro versions through 2.2.0 and 3.0.0-alpha-1 when using DefaultLdapRealm. Upgrading to Apache Shiro 2.2.1 or 3.0.0-alpha-2 or later addresses the issue.

Join the discussion

Apache Shiro versions 1.0, 3.0.0-alpha, and up to 2.1.0 have a session fixation vulnerability in their default configurations. The issue occurs because existing sessions are not invalidated nor replaced with new session IDs upon successful login. This vulnerability allows an attacker to fixate a user's session ID, potentially leading to unauthorized session use. The vulnerability is fixed in Apache Shiro versions 2.1.1 and 3.0.0-alpha-2 or later.

Join the discussion

Observable Timing Discrepancy vulnerability in Apache Shiro. This issue affects Apache Shiro: from 1.*, 2.* before 2.0.7. Users are recommended to upgrade to version 2.0.7 or later, which fixes the issue. Prior to Shiro 2.0.7, code paths for non-existent vs.existing users are different enough, that a brute-force attack may be able to tell, by timing the requests only, determine if the request failed because of a non-existent user vs.wrong password. The most likely attack vector is a local attack only. Shiro security model  https://shiro.apache.org/security-model.html#username_enumeration  discusses this as well. Typically, brute force attack can be mitigated at the infrastructure level.

Join the discussion

Showing 1 to 3 of 3 results

Filters:Package: pkg:maven/Apache Software Foundation/org.apache.shiro:shiro-core
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses