Skip to main content

Ubuntu Linux EUVDEUVD-2026-89131

| CVE-2026-95290 MEDIUM
Missing Authorization (CWE-862)
2026-09-23 vendor:ubuntu GHSA-hh74-cr8w-qm55
Medium
Disputed · 5.4 Vendor: vendor:ubuntu
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Unknown access vector
  2. Exploit
    Unknown vulnerability trigger
  3. Impact
    Unknown impact

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Cannot be determined - the description is empty and no CVSS vector is provided, so no product feature, protocol, configuration setting, deployment mode, authentication level, or user-interaction requirement can be extracted. Retrieve the Ubuntu Security tracker entry for CVE-2026-95290 and the upstream advisory to establish the affected package and its exploitation prerequisites before defenders act.

Impact

Risk cannot be meaningfully assessed from the available data. No CVSS vector, base score, EPSS probability, KEV status, POC indication, or SSVC decision points were provided, and the description is empty ('[Unknown description]'). The single available signal is that the record was surfaced by Ubuntu's security tooling (reported by vendor:ubuntu), which typically means an Ubuntu Security tracker entry for an upstream package, but the affected package, component, and impact are all unknown. Because attack vector, complexity, privilege, and technical-impact data are entirely missing, no attack-surface, severity, or exploitation-likelihood conclusions can be drawn. This should be treated as an unassessed placeholder pending vendor data, not as either a confirmed high priority or a confirmed low-risk issue - MISSING DATA: obtain the Ubuntu Security Notice / CVE tracker entry and upstream advisory before triage.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown. No public exploit is identified in the provided data. Any scenario stated here would be fabrication.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 24, 2026

Ubuntu Linux is the only identified touchpoint for CVE-2026-95290, which was reported through the vendor's own security channel but arrives with an empty description, no CVSS score or vector, no CWE mapping, and no listed affected versions. Because neither the affected package nor the exploitation prerequisites can be derived from the available data, the actual impact - whether local privilege escalation, denial of service, or remote code execution - remains undetermined, and no public exploit identified at time of analysis. Defenders should treat this as an intelligence gap rather than evidence of low severity, and pull the authoritative record from the Ubuntu Security tracker before making any exposure or patching decision.

RemediationAI

No remediation can be prescribed from the available data because patch status is not confirmed: no vendor advisory, patch reference, or exact fix version was supplied, so it is not established whether a fix exists or is still pending. The immediate action is intelligence retrieval rather than configuration change - look up CVE-2026-95290 in the Ubuntu CVE tracker and the associated Ubuntu Security Notice to identify the source package and the fixed version for each release in use, then apply the vendor package update (apt update followed by upgrading the named package) and restart the dependent services. If the tracker shows no fix yet, compensating controls must be scoped once the package is known - for example restricting network exposure of the service that ships the package, or disabling/removing the component if it is unused - recognizing that blanket hardening carries operational cost and may not address the actual flaw. Ubuntu Pro / Canonical Livepatch covers only selected kernel livepatching CVEs and should not be assumed to mitigate this record. Monitor the Ubuntu security notices feed for the USN that resolves this CVE and re-run triage at that point.

Affected VersionsENISA

Chrome 154.0.8037.57 <154.0.8037.57

Affected Packages

euvd chrome fix: 154.0.8037.57

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

No technical detail can be established for CVE-2026-95290: the description field is empty, the CVSS vector is absent, and no CWE is mapped, so the root-cause class (for example memory corruption, improper input validation, or a logic error) cannot be inferred. The input contains no CPE strings, so the affected component and version range are unknown beyond the single attribution to the Ubuntu vendor channel. In Ubuntu's model, CVEs are tracked against specific source packages in the archive and remediated through Ubuntu Security Notices and updated package builds, so the decisive next step is to resolve CVE-2026-95290 against the Ubuntu CVE tracker, which will name the source package, the vulnerable and fixed versions per release, and any upstream commit or patch reference. Until that mapping exists, no meaningful statement can be made about the protocol, library, subsystem, or deployment mode involved, and no exploitability model - including authentication level or user-interaction requirements - can be constructed; the independent assessment likewise concludes that exploitation conditions cannot be determined from the available data.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Sources disagree (Medium–Critical)
Vendor (vendor:ubuntu) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
SUSE CRITICAL

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: vendor:ubuntu

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
CVSS changed
Sep 30, 2026 - 22:08 NVD
5.4 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy