Quick answers
- Is CVE-2026-41076 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41076 being exploited in the wild.
- How severe is CVE-2026-41076?
- High severity, with a CVSS score of 8.1, published 22 May 2026.
- Which products and versions are affected?
- Best Practical Solutions RT < 5.0.10, >= 6.0.0, < 6.0.3.
- Is there a fix for CVE-2026-41076?
- A patch was published on 2026-05-20: RT versions 5.0.10 and 6.0.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41076 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41076?
- Check whether you run Best Practical Solutions RT at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass vulnerability (CWE-287) exists in Request Tracker (RT) versions prior to 5.0.10 and 6.0.x prior to 6.0.3. The flaw occurs when RT is configured to use LDAP or Active Directory for external authentication. If the LDAP server is configured to permit unauthenticated bind attempts (often via empty passwords), RT may incorrectly validate the session, allowing a remote attacker to impersonate any LDAP-backed user. The attack complexity is rated High as it depends on specific LDAP server configurations. Patches are available in versions 5.0.10 and 6.0.3; a temporary workaround involves configuring the LDAP server to reject unauthenticated bind attempts.
Affected products
- Best Practical RT (Request Tracker) < 5.0.10, >= 6.0.0, < 6.0.3
Timeline
- 2026-05-20: patched: RT versions 5.0.10 and 6.0.3 released
- 2026-05-20: advisory: GitHub Security Advisory GHSA-3w28-fmcr-mjjx published
- 2026-05-22: disclosed: NVD publication date