Skip to main content

Unknown Ubuntu package EUVDEUVD-2026-89259

| CVE-2026-95294 MEDIUM
User Interface (UI) Misrepresentation of Critical Information (CWE-451)
2026-09-23 vendor:ubuntu GHSA-77jv-fh2r-4vp2
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
  2. Exploit
    Identify affected Ubuntu package
  3. Impact
    Retrieve USN and CVSS details

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 description is missing and no CVSS vector is provided, so required features, protocols, configuration settings, authentication level, and user interaction are all unknown. Consult the Ubuntu Security Notice (USN) and NVD entry for CVE-2026-95294 to establish the affected package, whether exploitation is remote or local, and any configuration or authentication prerequisites before making defensive decisions.

Impact

Risk cannot be meaningfully assessed from the provided data. There is NO description, NO CVSS base score or vector, and NO CWE, so attack vector, complexity, and privilege requirements are all unknown. There is no EPSS score, no CISA KEV listing, and no POC indicator in the input, meaning there is no public exploit identified at time of analysis and no evidence of active exploitation. The only signal is that the record is associated with Ubuntu (vendor:ubuntu), which suggests the affected component is likely a package shipped in Ubuntu (potentially an OS-level library, kernel, or application in the Ubuntu archive), but the specific product is not stated. CONFLICTING/MISSING DATA MUST BE RESOLVED BEFORE PRIORITIZATION: retrieve the Ubuntu Security Notice (USN) and the NVD/vendor description for CVE-2026-95294 to obtain the affected package, CVSS vector, and severity. Until then this cannot be classified as either a real priority or a low-real-risk issue.

Exploit ScenarioDerived

No exploit scenario can be reliably constructed because the vulnerability description and attack vector are unknown. No POC is referenced in the provided data (no public exploit identified at time of analysis). Any scenario would be speculation until the Ubuntu advisory and affected package are identified.

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

Exploitation and impact for CVE-2026-95294 cannot be established from the available intelligence: the description is empty, no CVSS score or vector was assigned, no CWE mapping was provided, and no EPSS or KEV signal accompanies the record. The single traceable data point is the reporter field, which designates Ubuntu as the reporting vendor, meaning the affected component is most likely an Ubuntu-maintained package with a corresponding Ubuntu Security Notice (USN) that has not yet been surfaced in this dataset. No public exploit code has been identified at time of analysis and there is no confirmation of active exploitation (no CISA KEV entry), so any characterization of severity - remote versus local, authenticated versus unauthenticated, code execution versus denial of service - would be speculation until the USN and NVD entry are reviewed.

RemediationAI

No vendor-released patch version is identified in the provided data, and the absence of patch information here should not be read as confirmation that no fix exists - Canonical publishes fixes through USNs and the standard archive update mechanism. The primary action is to resolve the identity of the affected package first: look up CVE-2026-95294 in the Ubuntu CVE tracker and the USN database, then apply the fixed package version named in that notice with 'sudo apt update && sudo apt upgrade <package>' or, on systems managed centrally, through unattended-upgrades; for LTS systems relying on Expanded Security Maintenance, verify that ESM or Ubuntu Pro is enabled so the security pocket is reachable, since a host without it may silently remain on a vulnerable version. As compensating controls while the package identity is unknown: inventory Ubuntu hosts that expose network services and temporarily reduce their internet-facing attack surface, tighten access to administrative interfaces, and enable verbose logging and monitoring for the affected service once identified; each of these carries a cost - reduced surface may break legitimate integrations, and aggressive logging increases storage and noise - so they should be treated as temporary measures. To catch the advisory promptly, subscribe to the ubuntu-security-announce mailing list or an equivalent USN feed and re-scan affected hosts after the fix lands, since patch-free guidance cannot be made more specific until the package and version data are known.

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

The record carries no CWE classification, so the root-cause class (for example memory corruption, path traversal, privilege-handling flaw, or dependency issue) is unknown, and no CVSS vector is present, which removes the usual basis for determining attack vector, privilege requirements, or user interaction. The affected technology stack is likewise unidentified: no CPE strings were supplied, so it is not possible to map the flaw to a specific library, daemon, or protocol implementation within the Ubuntu archive. The only structural clue is the reporting attribution to vendor:ubuntu, which in practice means a USN was or will be published under Canonical's coordinated disclosure process and that the vulnerable artifact is a package distributed through the Ubuntu repositories (main, universe, or a supported LTS/ESM channel). Because Ubuntu packages frequently bundle or depend on upstream projects, the true origin of the defect may be an upstream release that Canonical has backported a fix for, which means downstream consumers should track both the USN and the upstream project's own advisory once identified.

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