{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102899 is a high-severity authentication bypass vulnerability in getsentry sentry, published on 14 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-102899 and fix it if it is affected.\n\nWhat it is: CVE-2026-102899 is a high-severity authentication bypass vulnerability in getsentry sentry, published on 14 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-102899 in the wild and no public exploit code.\n\nAffected product: getsentry sentry. 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-102899/ (Markdown: https://insights.sbomify.com/CVE-2026-102899/index.md)","id":"CVE-2026-102899","markdown":"https://insights.sbomify.com/CVE-2026-102899/index.md","name":"CVE-2026-102899","record":{"aliases":["GHSA-w699-8wff-fqxw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Sentry monitoring platform","requires_auth":"none","summary":"Attackers can link their identity to victim accounts via SAML SSO, leading to account takeover, requiring specific browser cookie settings.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Sentry is an application monitoring and error tracking platform. From 26.5.0 until 26.7.2, the SAML SSO identity-linking flow allows an attacker who controls a SAML identity provider to socially engineer an authenticated user into opening a malicious URL, link the attacker's identity to the victim's Sentry account, and take control of that account. The attack requires a browser that accepts the cross-site cookie context, including Firefox with SameSite=None cookies or Chromium with third-party cookies enabled. Sentry SaaS received the remediation on July 27, 2026, and self-hosted Sentry is fixed in version 26.7.2.","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":"Sentry: Improper authentication on SAML SSO process allows user identity linking","id":"CVE-2026-102899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs","id":"CVE-2026-102904"},"packages":[],"prev":{"headline":"Zulip: OpenID Connect authentication ignores the email_verified claim","id":"CVE-2026-102893"},"products":["sentry"],"published":"2026-10-14","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":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["getsentry"]},"summary":"Attackers can link their identity to victim accounts via SAML SSO, leading to account takeover, requiring specific browser cookie settings.","url":"https://insights.sbomify.com/CVE-2026-102899/"}