Skip to main content

Ubuntu CVE-2026-95279

| EUVDEUVD-2026-89154 MEDIUM
User Interface (UI) Misrepresentation of Critical Information (CWE-451)
2026-09-23 vendor:ubuntu GHSA-wjv8-w3xw-j2wj
Medium
Disputed · 5.4 Vendor: vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Insufficient data to determine access vector
  2. Exploit
    Vulnerability class unknown
  3. Impact
    Impact unknown

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security UI security representation
Exploitation Conditions

Cannot be determined - the input provides no description, affected feature, protocol, configuration mode, or CVSS vector. The sole datum is that the CVE is reported by the Ubuntu Security team, which implies (but does not confirm) an affected open-source package distributed with Ubuntu/Debian. No prerequisites, required privileges, user interaction, or configuration dependencies can be stated until source data (USN/NVD) is retrieved.

Impact

Risk cannot be meaningfully assessed from the provided data. The input contains no description, no CVSS score or vector, no CWE, no EPSS probability, no KEV listing, and no POC reference - the only signal is that the CVE was reported by 'vendor:ubuntu', indicating it is tracked by the Ubuntu Security team and therefore most likely affects a package shipped in the Ubuntu/Debian ecosystem (open-source software). With no attack vector, complexity, privilege, or impact metrics available, it is impossible to distinguish a genuine priority from a low-real-risk issue. Exploitation status is 'no public exploit identified at time of analysis' (no KEV, no POC in the input). All substantive risk signals are MISSING and must be retrieved from the Ubuntu Security Notice (USN) / CVE tracker and NVD before any prioritization decision can be made.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all absent from the provided data. The only fact available is that Ubuntu tracks this CVE, implying an affected open-source package. No public exploit code is identified in the input.

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

Risk cannot be meaningfully assessed from the provided data for CVE-2026-95279, which arrives with no description, no CVSS vector, no CWE, and no affected-product detail. The only signal is that the record was reported by the Ubuntu security team, implying an affected open-source package distributed with Ubuntu (and likely Debian-derived distributions), but the specific component, attack vector, and impact remain unconfirmed. There is no confirmed actively exploited (CISA KEV) status, no publicly available exploit code, and no EPSS score in the available input, so triage depends on retrieving the underlying Ubuntu Security Notice or NVD entry before any technical conclusion can be drawn.

RemediationAI

No vendor-released patch or exact fix version can be cited, because the input contains no patch data, advisory URL, or affected version range for CVE-2026-95279. The primary actionable step is investigative rather than technical: retrieve the Ubuntu Security Notice referenced by the Ubuntu security team, together with the corresponding NVD entry and Ubuntu CVE tracker record, to establish the affected package, the impacted version range, and the fixed version. In the interim, operators of Ubuntu and Debian-derived systems should maintain routine security-update hygiene - ensure unattended-upgrades or equivalent automated patching is active for the security pocket, and monitor the Ubuntu security announcements feed - recognizing that this is a precaution and not confirmation that any particular package on a given host is vulnerable. Speculative mitigations such as disabling services, blocking ports, or restricting endpoints should be avoided at this stage, since the vulnerable component is unidentified and such changes would impose operational cost and breakage risk without a known threat to counter.

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

Because no CWE, CVSS vector, or CPE data was supplied, the root-cause class and the underlying technology - whether a kernel subsystem, a userland library, a network daemon, or a package build/packaging defect - cannot be identified. The sole attribution is to the Ubuntu security team, which indicates the issue affects a package shipped in the Ubuntu ecosystem and is likely tracked via a Ubuntu Security Notice (USN) with a corresponding Debian-adjacent patch stream; this does not establish whether the defect is Ubuntu-specific, present in the upstream open-source project, or introduced by a downstream delta. With no PR, AV, or UI values available, authentication requirements, network reachability, and user-interaction prerequisites cannot be stated, and any such claim would be speculative rather than evidence-based.

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:N/A:L
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
None
Availability
Low

Lifecycle Timeline

1
CVSS changed
Sep 29, 2026 - 19:22 NVD
5.4 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Data Quality
3 sources
Confidence: Low

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

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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