{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41073 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-41073 is a medium-severity vulnerability in bestpractical rt, published on 22 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-41073 and fix it if it is affected.\n\nWhat it is: CVE-2026-41073 is a medium-severity vulnerability in bestpractical rt, published on 22 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-41073 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-41073/ (Markdown: https://insights.sbomify.com/CVE-2026-41073/index.md)","id":"CVE-2026-41073","markdown":"https://insights.sbomify.com/CVE-2026-41073/index.md","name":"CVE-2026-41073","record":{"aliases":["DEBIAN-CVE-2026-41073","GHSA-6x92-7v65-7m3r","UBUNTU-CVE-2026-41073"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"RT ticket tracking system","requires_auth":"low_privilege","summary":"Attackers can inject malicious formulas into RT spreadsheet exports, leading to code execution when victims open the files in spreadsheet applications.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"RT is an open source, enterprise-grade issue and ticket tracking system. Versions prior to 5.0.10 and 6.0.0 through 6.0.2 contain a spreadsheet (CSV/formula) injection vulnerability. User-controlled data in spreadsheet exports is not sanitized before being written to the output file, which can cause spreadsheet applications to interpret crafted values as formulas or macros when the file is opened. 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 avoiding opening exported RT spreadsheet files directly in spreadsheet applications when the data may contain untrusted user input.","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: Spreadsheet downloads vulnerable to CSV/formula injection in Microsoft Excel and similar apps","id":"CVE-2026-41073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RT has broken CSRF protection for authenticated users","id":"CVE-2026-41074"},"packages":[],"prev":{"headline":"libheif: Heap buffer over-read in SampleAuxInfoReader via crafted HEIF sequence file with mismatched saiz sample count","id":"CVE-2026-41071"},"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-23","vendors":["bestpractical"]},"summary":"Attackers can inject malicious formulas into RT spreadsheet exports, leading to code execution when victims open the files in spreadsheet applications.","url":"https://insights.sbomify.com/CVE-2026-41073/"}