{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41076 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-41076 is a high-severity authentication bypass vulnerability in bestpractical rt, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41076 and fix it if it is affected.\n\nWhat it is: CVE-2026-41076 is a high-severity authentication bypass vulnerability in bestpractical rt, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41076 in the wild and no public exploit code.\n\nAffected product: bestpractical rt. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41076/ (Markdown: https://insights.sbomify.com/CVE-2026-41076/index.md)","id":"CVE-2026-41076","markdown":"https://insights.sbomify.com/CVE-2026-41076/index.md","name":"CVE-2026-41076","record":{"aliases":["DEBIAN-CVE-2026-41076","GHSA-3w28-fmcr-mjjx","UBUNTU-CVE-2026-41076"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"RT ticket tracking system","requires_auth":"none","summary":"Attackers can bypass authentication in RT installations using LDAP/AD under specific server configurations, gaining unauthorized access to user accounts.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.9 and prior in addition to 6.0.0 through 6.0.2 contain an authentication bypass vulnerability in RT installations that use LDAP/AD for user authentication. Under certain LDAP server configurations, an attacker may be able to authenticate as any LDAP-backed RT user without supplying valid credentials.  This issue has been fixed in versions 5.0.10 and 6.0.3. If developers are unable to upgrade immediately, they can temporarily work around this issue by reviewing their LDAP server's authentication policy to ensure it rejects unauthenticated bind attempts. Upgrading RT remains the recommended fix.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RT: LDAP authentication bypass via empty password","id":"CVE-2026-41076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path","id":"CVE-2026-41078"},"packages":[],"prev":{"headline":"RT: SQL injection via entry_aggregator parameter in JSON search","id":"CVE-2026-41075"},"products":["rt"],"published":"2026-05-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["bestpractical"]},"summary":"Attackers can bypass authentication in RT installations using LDAP/AD under specific server configurations, gaining unauthorized access to user accounts.","url":"https://insights.sbomify.com/CVE-2026-41076/"}