{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-48929 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48929 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48929 is a high-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 16 Jun 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-48929 and fix it if it is affected.\n\nWhat it is: CVE-2026-48929 is a high-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 16 Jun 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-48929 in the wild and no public exploit code.\n\nAffected product: Rocket.chat Rocket.chat. 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-48929/ (Markdown: https://insights.sbomify.com/CVE-2026-48929/index.md)","id":"CVE-2026-48929","markdown":"https://insights.sbomify.com/CVE-2026-48929/index.md","name":"CVE-2026-48929","record":{"aliases":["GHSA-f55j-xv27-8cwj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rocket.Chat","requires_auth":"none","summary":"Unauthenticated attackers can permanently delete uploaded files in Rocket.Chat by exploiting a missing authorization check in the file deletion method.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"rocket.chat","vendor":"rocket.chat"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Rocket.Chat in versions \u003c8.5.1, \u003c8.4.4, \u003c8.3.6, \u003c8.2.6, \u003c8.1.6, \u003c8.0.7, \u003c7.13.9, and \u003c7.10.13 is vulnerable to unauthenticated file deletion. The deleteFileMessage Meteor method permanently deletes any uploaded file by ID without requiring authentication. When called via an unauthenticated DDP WebSocket connection, Meteor.userId() returns null, causing the authorization check to be skipped. Execution falls through to FileUpload.getStore('Uploads').deleteById(fileID), which removes the file from storage and database unconditionally. File IDs are discoverable from public channel message payloads and download URLs.","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":"Missing authorization in Rocket.Chat","id":"CVE-2026-48929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"rocket.chat:rocket.chat","products":["rocket.chat:rocket.chat"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in node","id":"CVE-2026-48930"},"packages":[],"prev":{"headline":"Security feature bypass in node","id":"CVE-2026-48928"},"products":["Rocket.Chat"],"published":"2026-06-16","related":[{"cvss_score":9.8,"headline":"Auth bypass in Rocket.Chat","id":"CVE-2026-58066","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"SQL injection in Rocket.Chat","id":"CVE-2026-29198","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":9.8,"headline":"Security feature bypass in Rocket.Chat","id":"CVE-2023-28316","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":9.8,"headline":"Command injection in Rocket.chat - Electron Desktop","id":"CVE-2022-44567","kev_date_added":null,"published":"2022-12-23"},{"cvss_score":9.8,"headline":"Code injection in Rocket.Chat server","id":"CVE-2021-22910","kev_date_added":null,"published":"2021-08-09"},{"cvss_score":9.8,"headline":"Code injection in Rocket.Chat server","id":"CVE-2021-22911","kev_date_added":null,"published":"2021-05-27"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-29594","kev_date_added":null,"published":"2020-12-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-17","vendors":["Rocket.Chat"]},"summary":"Unauthenticated attackers can permanently delete uploaded files in Rocket.Chat by exploiting a missing authorization check in the file deletion method.","url":"https://insights.sbomify.com/CVE-2026-48929/"}