Secuno
ENNL
Book demo

CVE-2026-90999

9.8 CRITICAL
  1. Published16 Sept 2026

Description

Sentry Seer is vulnerable to a multi-stage trust-boundary violation that allows unauthenticated attacker-controlled telemetry to become code that is executed by an agent in a privileged automation environment. An external attacker can submit fabricated Sentry events without having access to the victim’s Sentry account, source repository, or infrastructure.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-9360310.0
vm2 through 3.12.0 (fixed in 3.12.1) does not correctly handle a nullish `this`…
CVE-2026-136849.8
An improper encoding or escaping of output vulnerability in SCGI in Synology…
CVE-2026-129548.8
The Mapster WP Maps plugin for WordPress is vulnerable to Arbitrary User Meta Write in…
CVE-2026-847389.1
The AF Companion WordPress plugin before 2.2.0 does not validate the type of files…
CVE-2026-933718.3
A security vulnerability has been detected in marcopiovanello yt-dlp-web-ui up to v4.…
CVE-2026-877019.6
Improper neutralization of special elements in output used by a downstream component…

Frequently asked

Is CVE-2026-90999 being actively exploited?

CVE-2026-90999 is not in the CISA KEV catalog.

How severe is CVE-2026-90999?

CVE-2026-90999 has a CVSS 3.1 base score of 9.8, rated critical.

How do I fix CVE-2026-90999?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-90999 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.