{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-112050 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-112050 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-112050 is a low-severity vulnerability in gitify-app gitify, published on 18 Oct 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-112050 and fix it if it is affected.\n\nWhat it is: CVE-2026-112050 is a low-severity vulnerability in gitify-app gitify, published on 18 Oct 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-112050 in the wild and no public exploit code.\n\nAffected product: gitify-app gitify. 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-112050/ (Markdown: https://insights.sbomify.com/CVE-2026-112050/index.md)","id":"CVE-2026-112050","markdown":"https://insights.sbomify.com/CVE-2026-112050/index.md","name":"CVE-2026-112050","record":{"aliases":["GHSA-gh5g-g72j-mxwx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub notification client","requires_auth":"none","summary":"Attackers can bind a victim's Gitify client to their account via missing OAuth state validation, displaying attacker-controlled notifications as the victim's.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Gitify before 7.10.0 contains a login cross-site request forgery vulnerability that allows remote attackers to bind a victim's client to their account because performGitHubWebOAuth() omits OAuth state validation. Attackers can get a gitify://oauth?code= link with their own authorization code opened during a victim's pending login, causing Gitify to display attacker-controlled notifications as the victim's own.","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":"Gitify before 7.10.0 Login CSRF via Missing OAuth State Validation","id":"CVE-2026-112050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Xinference through 4.0.1 Path Traversal via model_name in Custom Model Registration","id":"CVE-2026-112051"},"packages":[],"prev":{"headline":"Vita3K before build 4187 Path Traversal via VPK Package Installation","id":"CVE-2026-112049"},"products":["gitify"],"published":"2026-10-18","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-10-19","vendors":["gitify-app"]},"summary":"Attackers can bind a victim's Gitify client to their account via missing OAuth state validation, displaying attacker-controlled notifications as the victim's.","url":"https://insights.sbomify.com/CVE-2026-112050/"}