{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41074 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41074 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41074 is a high-severity vulnerability in bestpractical rt, published on 22 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-41074 and fix it if it is affected.\n\nWhat it is: CVE-2026-41074 is a high-severity vulnerability in bestpractical rt, published on 22 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-41074 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-41074/ (Markdown: https://insights.sbomify.com/CVE-2026-41074/index.md)","id":"CVE-2026-41074","markdown":"https://insights.sbomify.com/CVE-2026-41074/index.md","name":"CVE-2026-41074","record":{"aliases":["GHSA-265j-qx4w-256j","UBUNTU-CVE-2026-41074"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RT ticket tracking system","requires_auth":"none","summary":"An attacker can trick logged-in RT users into performing unauthorized state-changing actions via a malicious webpage.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 through 6.0.2 contain a Cross-Site Request Forgery (CSRF) vulnerability. An attacker who can induce a logged-in RT user to visit a malicious web page can trigger arbitrary state-changing actions in RT on that user's behalf. This issue has been fixed in version 6.0.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"RT has broken CSRF protection for authenticated users","id":"CVE-2026-41074","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"RT: SQL injection via entry_aggregator parameter in JSON search","id":"CVE-2026-41075"},"packages":[],"prev":{"headline":"RT: Spreadsheet downloads vulnerable to CSV/formula injection in Microsoft Excel and similar apps","id":"CVE-2026-41073"},"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":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["bestpractical"]},"summary":"An attacker can trick logged-in RT users into performing unauthorized state-changing actions via a malicious webpage.","url":"https://insights.sbomify.com/CVE-2026-41074/"}