Skip to main content

Ubuntu Linux EUVDEUVD-2026-89146

| CVE-2026-95307 MEDIUM
User Interface (UI) Misrepresentation of Critical Information (CWE-451)
2026-09-23 vendor:ubuntu GHSA-97qh-xrc3-2fpq
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 vector
  2. Exploit
    Unknown weakness triggered
  3. Impact
    Unknown impact

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, affected product/feature, protocol, configuration prerequisites, authentication level, and required user interaction are all absent from the input. No statement about default-configuration exploitability or limiting factors can be made without enrichment from an authoritative source such as the Ubuntu security tracker or NVD.

Impact

Risk cannot be meaningfully assessed from the provided data. No CVSS base score or vector is present, so attack vector, complexity, privileges, scope, and impact are all unknown. There is no EPSS probability, no CISA KEV listing, no SSVC decision data, and no indication of public proof-of-concept code. The sole signal is that the CVE is tracked by the Ubuntu security team (vendor:ubuntu), which typically indicates an open-source software package shipped in the Ubuntu distribution, but the specific package, component, and flaw class are not identified in the input. Because every quantitative and qualitative risk signal is missing, this record cannot be triaged as either a genuine priority or a low-real-risk high-CVSS item - it must be enriched from an authoritative source (the Ubuntu CVE tracker / NVD) before any risk conclusion is drawn. State explicitly: no severity, exploitability, or impact determination is possible from the data provided.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown. No proof-of-concept code is indicated in the available data. Enrichment from the Ubuntu security tracker or NVD is required before any realistic scenario can be described.

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 Linux is the only attributed product for CVE-2026-95307, which reaches us solely through a vendor:ubuntu source with no description, CVSS vector, CWE, CPE, or reference data attached. Because the affected component, attack vector, authentication requirements, and user-interaction prerequisites are all missing, the impact an attacker could achieve cannot be stated and the overall risk cannot be meaningfully assessed from the provided data. There is no KEV listing, no public exploit code identified, and no EPSS score available at time of analysis, so no exploitation signal exists in either direction. Treat this identifier as an unresolved tracking item pending enrichment from the Ubuntu security tracker or NVD.

RemediationAI

No fixed version is available in the provided data, so no exact upgrade target can be named; the patch status is simply not established at time of analysis and should not be read as confirmation that no fix exists. The primary action is to monitor the Ubuntu security tracker entry at https://ubuntu.com/security/CVE-2026-95307 and the Ubuntu Security Notices feed at https://ubuntu.com/security/notices, and to apply the fixed package versions via apt (or unattended-upgrades for managed fleets) as soon as a USN is published; the trade-off of enabling unattended-upgrades is that service restarts and reboots may occur during maintenance windows. Targeted compensating controls cannot be responsibly specified here, because without knowing the affected component you cannot know which feature to disable, which port or endpoint to block, or which access control to tighten, and applying blanket mitigations would risk breaking unrelated functionality for no measurable gain. In the interim, reduce exposure by maintaining accurate software inventory of Ubuntu hosts so affected packages can be located quickly when the advisory lands, and by restricting network exposure of Ubuntu services that are not required externally, understanding that this is general hardening rather than a mitigation specific to this CVE. If a USN later identifies a network-reachable daemon, the corresponding firewall restriction or service disablement becomes the appropriate stopgap; if it identifies a local-only privilege issue, kernel livepatch or prompt upgrading becomes the priority instead.

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 is supplied, so the root-cause class cannot be established; the flaw could equally be an injection, memory-safety, authorization, or logic defect. Likewise, no CPE strings are provided, meaning the affected package and version range are unknown, and it is not determinable whether the issue lies in an Ubuntu-maintained package, a distribution-specific patch, or an upstream component that Ubuntu merely rebundles. The single reliable signal is the reporter, vendor:ubuntu, which indicates the issue is tracked within Ubuntu's distribution security process and would ordinarily receive a Ubuntu Security Notice (USN) with fixed package versions. Note that CVSS is absent rather than zero, so no severity, exploitability sub-score (AV, AC, PR, UI), or scope-change information should be inferred. Until an authoritative record surfaces, any statement about default-configuration exposure, privilege level required, or whether exploitation needs local access versus network reachability 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 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