{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41926 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41926 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41926 is a low-severity vulnerability in nextcloud security-advisories, published on 25 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-41926 and fix it if it is affected.\n\nWhat it is: CVE-2022-41926 is a low-severity vulnerability in nextcloud security-advisories, published on 25 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-41926 in the wild and no public exploit code.\n\nAffected product: nextcloud security-advisories. 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-2022-41926/ (Markdown: https://insights.sbomify.com/CVE-2022-41926/index.md)","id":"CVE-2022-41926","markdown":"https://insights.sbomify.com/CVE-2022-41926/index.md","name":"CVE-2022-41926","record":{"aliases":["GHSA-564v-3rfc-352m"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Nextcloud Talk Android","requires_auth":"none","summary":"Malicious apps can monitor communication due to unprotected broadcast receivers in the Nextcloud Talk Android application.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"talk","vendor":"nextcloud"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Nextcould talk android is the android OS implementation of the nextcloud talk chat system. In affected versions the receiver is not protected by broadcastPermission allowing malicious apps to monitor communication. It is recommended that the Nextcloud Talk Android is upgraded to 14.1.0. There are no known workarounds for this issue.","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":"Nextcloud Talk Android broadcast incorrect permission handling","id":"CVE-2022-41926","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"XWiki Platform vulnerable to Cross-Site Request Forgery (CSRF) allowing to delete or rename tags","id":"CVE-2022-41927"},"packages":[],"prev":{"headline":"Tailscale daemon is vulnerable to information disclosure via CSRF","id":"CVE-2022-41925"},"products":["security-advisories"],"published":"2022-11-25","related":[{"cvss_score":9.9,"headline":"Code injection in Nextcloud Talk","id":"CVE-2020-8180","kev_date_added":null,"published":"2020-06-08"},{"cvss_score":8.1,"headline":"Nextcloud Talk not properly disassociating users from chats after account deletion","id":"CVE-2021-32689","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":7.2,"headline":"Path traversal allows tricking the Talk Android app into writing files into it's root directory","id":"CVE-2023-39957","kev_date_added":null,"published":"2023-08-10"},{"cvss_score":6.5,"headline":"Session Fixation in Nextcloud Talk","id":"CVE-2021-32676","kev_date_added":null,"published":"2021-06-16"},{"cvss_score":6.4,"headline":"XSS in Talk","id":"CVE-2021-39222","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":5.4,"headline":"Cross-site scripting in nextcloud/talk","id":"CVE-2018-3781","kev_date_added":null,"published":"2018-08-13"},{"cvss_score":4.7,"headline":"Geolocation preview links can be set to arbitrary links in nextcloud talk","id":"CVE-2021-41180","kev_date_added":null,"published":"2022-03-08"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["nextcloud"]},"summary":"Malicious apps can monitor communication due to unprotected broadcast receivers in the Nextcloud Talk Android application.","url":"https://insights.sbomify.com/CVE-2022-41926/"}