{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-58066 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58066 is a critical authentication bypass vulnerability in Rocket.chat Rocket.chat, published on 30 Jul 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-58066 and fix it if it is affected.\n\nWhat it is: CVE-2026-58066 is a critical authentication bypass vulnerability in Rocket.chat Rocket.chat, published on 30 Jul 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-58066 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-58066/ (Markdown: https://insights.sbomify.com/CVE-2026-58066/index.md)","id":"CVE-2026-58066","markdown":"https://insights.sbomify.com/CVE-2026-58066/index.md","name":"CVE-2026-58066","record":{"aliases":["GHSA-f3wj-pr2w-q3fm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Rocket.Chat SAML SSO","requires_auth":"none","summary":"Attackers can bypass SAML authentication in Rocket.Chat by submitting forged identity attributes with a valid signature, allowing them to log in as arbitrary users.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"rocket.chat","vendor":"rocket.chat"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Rocket.Chat's SAML SSO before versions 8.7.0, 8.6.1, 8.5.2, 8.4.5, 8.3.7, 8.2.7, 8.1.7, 8.0.8, and 7.10.14 verified XML signatures but did not bind the validated signature to samlp:Response / saml:Assertion. An attacker could submit a wrapped document carrying forged identity attributes alongside any valid signature made by the trusted IdP certificate, and log in as an arbitrary user.","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":"Auth bypass in Rocket.Chat","id":"CVE-2026-58066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"rocket.chat:rocket.chat","products":["rocket.chat:rocket.chat"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in Service Provider Console","id":"CVE-2026-58067"},"packages":[],"prev":{"headline":"Security feature bypass in Apache Airflow Git provider","id":"CVE-2026-58065"},"products":["Rocket.Chat"],"published":"2026-07-30","related":[{"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":"total"},"state":"PUBLISHED","updated":"2026-07-31","vendors":["Rocket.Chat"]},"summary":"Attackers can bypass SAML authentication in Rocket.Chat by submitting forged identity attributes with a valid signature, allowing them to log in as arbitrary users.","url":"https://insights.sbomify.com/CVE-2026-58066/"}