Newly released CVEs across every platform — sleek to read, verbose on demand, and served raw as markdown for AI and agent ingestion. Severity reads as depth: the deeper the contact, the graver the threat.
Depth = severity + exploitation
CVE-2026-27197Critical· 9.1Sentry: Improper authentication on SAML SSO process allows user identity linking
CVE-2021-47935High· 8.8PoCSentry 8.2.0 contains a remote code execution vulnerability that allows authenticated superusers to execute arbitrary commands by injecting malicious pickle-serialized objects through the audit log entry data parameter. Attackers can sub…
CVE-2024-45606High· 7.1Sentry improperly authorizes muting of alert rules
CVE-2024-45605Medium· 6.5Sentry improperly authorizes deletion of user issue alert notifications
CVE-2024-41656High· 7.1Sentry vulnerable to stored Cross-Site Scripting (XSS)
CVE-2024-35196Low· 2.0Slack integration leaks sensitive information in logs
CVE-2024-32474High· 7.3Sentry vulnerable to leaking superuser cleartext password in logs
CVE-2023-39531Medium· 6.5Sentry vulnerable to incorrect credential validation on OAuth token requests
CVE-2023-39349High· 8.1Privilege escalation via ApiTokensEndpoint
CVE-2023-36826High· 7.7Improper authorization on debug and artifact file downloads
CVE-2023-36829Medium· 6.8Sentry CORS misconfiguration
The beta is over. VulnSea now runs at vulnsea.com, every old beta link redirects to the same page, and your account, API keys and watchlists came with it. Plus a round of hardening, faster pages, and new request limits agents should know about.
A summary of everything that shipped over the last two weeks — the whole corpus is open, agents get change feeds, alias resolution and EPSS movers, and the data now includes CVE.org, vendor CSAF, aggregated exploits and per-source scores.
A step-by-step guide to plugging VulnSea into automated and agentic workflows — poll the delta, triage without burning tokens, match an SBOM, and let an MCP-native model do the reasoning.