Unauthenticated RCE in Sentry Seer that can execute attacker-controlled code in privileged automation agents used widely by development teams; high risk of broad org compromise.
CVE-2026-90999
Unauthenticated RCE via forged Sentry events executing code in privileged automation agents.
Is CVE-2026-90999 being exploited?
Not confirmed. CVE-2026-90999 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.
How severe is CVE-2026-90999?
CVE-2026-90999 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-90999?
Not known from our data. No patch reference has been recorded for CVE-2026-90999, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-90999 affect?
CVE-2026-90999 affects Sentry Seer, Sentry agents, automation/CI-CD agents, privileged automation environments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-90999?
Isolate agents, block/validate external telemetry, apply vendor patch/mitigations when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can submit fabricated Sentry events that execute attacker-controlled code in privileged automation agents, enabling remote code execution and full system takeover.
Immediate action required
- affectedWeb site
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 18 Sept 2026 (SSVC 2.0.3).
timeline
- 16 Sept 2026Published
- 18 Sept 2026CISA SSVC assessment: exploitation none · 2 days later
- 18 Sept 2026CVE record last updated · same day later
- 18 Sept 2026Analysed by vulneraibility.com · same day later
- Linkkb.cert.org /vuls/id/212479
- Linkkb.cert.org /vuls/id/212479
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.