Skip to main content

Ubuntu Linux EUVDEUVD-2026-89168

| CVE-2026-95340 MEDIUM
Incorrect Authorization (CWE-863)
2026-09-23 vendor:ubuntu GHSA-28qg-3gvj-3hwf
Medium
Disputed · 4.3 Vendor: vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Insufficient data to construct attack chain
  2. Exploit
    Affected component unknown
  3. Impact
    Retrieve details from Ubuntu Security tracker

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
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

Exploitation conditions cannot be determined - the CVE description is '[Unknown description]', and no CVSS vector, CWE, affected package, or configuration detail was provided. The only established fact is that the CVE is tracked by Ubuntu, suggesting it affects a package shipped in an Ubuntu/Debian-based Linux distribution. Prerequisites, required privileges, authentication level, user interaction, and any non-default configuration dependency are all unknown and must be obtained from the Ubuntu Security tracker entry for CVE-2026-95340.

Impact

Risk cannot be meaningfully assessed from the provided data. The only intelligence signal present is that the CVE was reported by 'vendor:ubuntu' (i.e., it appears in the Ubuntu CVE tracker, typically covering a Linux distribution package). There is no description, no CVSS base score or vector, no CWE, no EPSS probability, no KEV listing, no SSVC decision data, and no POC indicator. With no attack vector, complexity, or privilege metrics available, it is impossible to distinguish a genuine priority from a high-CVSS-but-low-real-risk issue. No public exploit identified at time of analysis. All risk-scoring signals (CVSS/EPSS/KEV/SSVC) are MISSING and must be retrieved directly from the Ubuntu Security tracker (ubuntu.com/security/CVE-2026-95340) and NVD before any prioritization decision is made.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability description, affected component, and vulnerability class (CWE) are all absent from the provided data. The affected Ubuntu package and the nature of the flaw are unknown, so any scenario would be pure speculation. No public exploit identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% 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 is tracking CVE-2026-95340, but the intelligence available for this analysis contains no description, CVSS vector, CWE class, affected package name, or version range, so neither the impact nor the attack surface can be characterised at this time. No public exploit code and no evidence of active exploitation were identified at time of analysis, which reflects an absence of data rather than a confirmed low risk. The Ubuntu Security tracker entry for this CVE is the authoritative source and must be retrieved before any exposure or prioritisation decision is made.

RemediationAI

No vendor-released patch has been identified for CVE-2026-95340 at time of analysis, and because the affected package and vulnerability class are undocumented, no package-specific workaround can be prescribed without inventing detail. The actionable first step is to retrieve the authoritative entry at https://ubuntu.com/security/CVE-2026-95340, which will name the affected source package, mark each Ubuntu release as vulnerable, not-affected, needed, deferred, or released, and point to the corresponding Ubuntu Security Notice (USN) and fixed package version. Once the package is identified, apply the fixed version with apt-get update followed by apt-get install --only-upgrade <package> (or apt-get upgrade / unattended-upgrades for the system as a whole), noting that the relevant service must be restarted for the patched code to be loaded. If the tracker marks the issue as deferred or pending, compensating controls must be scoped to the once-identified component - for example restricting network exposure to that service, disabling the specific feature or module named in the advisory, or removing the package entirely if it is non-essential - each of which trades away functionality or availability and none of which is a substitute for identifying the package.

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 CWE, CPE, CVSS vector, or component identifier was supplied, so the underlying technology, library, or protocol cannot be named and the root-cause weakness class cannot be mapped. The one reliable signal is the reporting source, vendor:ubuntu, which indicates a package maintained and shipped through the Ubuntu/Debian ecosystem - meaning the fix is most likely delivered as a distribution package update (deb) with an Ubuntu-specific patch or backport rather than solely as an upstream point release, and that Ubuntu's own tracker will carry the affected source package together with vulnerable and fixed version information. Distribution trackers frequently mark entries as needs-evaluation or deferred before an upstream fix exists, so the missing detail here may simply reflect an advisory that has not yet been fully triaged. Until that entry is read, any statement about authentication requirements, remote versus local reachability, or required privileges would be speculation.

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 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
None
Integrity
Low
Availability
None

Lifecycle Timeline

1
CVSS changed
Sep 30, 2026 - 17:22 NVD
4.3 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% 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.3%
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

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
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