Skip to main content

Ubuntu CVE-2026-95292

| EUVDEUVD-2026-89152 MEDIUM
Incorrect Authorization (CWE-863)
2026-09-23 vendor:ubuntu GHSA-rf7f-gfrm-w249
Medium
Disputed · 4.8 Vendor: vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Insufficient data
  2. Exploit
    Vulnerability class unknown
  3. Impact
    Impact undetermined

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 prerequisites cannot be determined. The provided data contains no description, no CVSS vector, no affected product, and no configuration or deployment details, so it is impossible to state whether the flaw requires authentication, user interaction, a specific feature to be enabled, or a particular platform. This field must be populated from the Ubuntu Security Notice and NVD once the affected package and vulnerability class are known.

Impact

Risk cannot be meaningfully assessed from the provided data. There is no CVSS base score or vector, no CWE, no description, no EPSS probability, no KEV listing, no POC reference, no SSVC decision points, and no affected-product or version information. The single available signal is that the record was reported by vendor:ubuntu, which suggests this is a CVE tracked through Ubuntu's security process (typically a distribution-packaged open-source component), but the affected package is unidentified. Because attack vector, complexity, and privilege requirements are all missing, no priority determination is possible. This record must be enriched from the Ubuntu Security Notice (USN) tracker and NVD before any triage decision is made; treating it as either high or low risk right now would be unsupported by evidence.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown. No public exploit has been identified in the provided data. Any scenario stated here would be speculation rather than analysis.

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

CVE-2026-95292 is tracked against Ubuntu, identified here only through the vendor:ubuntu reporting source, with no description, CVSS vector, CWE classification, CPE data, or affected package name supplied in the available intelligence. Because the vulnerability class, attack vector, and impacted component are all unknown, the exploitable impact on any Ubuntu release cannot be characterized, and remediation cannot name a fixed package version. No public exploit code has been identified at time of analysis, and no CISA KEV entry is present, so there is no indication of confirmed active exploitation; first-sentence risk cannot be meaningfully assessed from the provided data.

RemediationAI

No vendor-released patch version and no upstream PR or commit are identified in the provided data, so no fixed package version can be cited and patch availability is not confirmed at time of analysis. The primary action is to monitor Canonical's Ubuntu Security Notice feed and the CVE-2026-95292 entry in Canonical's CVE database, then apply the exact patched package versions named in the resulting USN via apt (for example a targeted 'apt-get install --only-upgrade <package>' followed by a service restart or reboot where the kernel or libc is involved); enabling unattended-upgrades provides continuous coverage but can restart services unexpectedly, so schedule it against a maintenance window. Because the affected component, attack vector, and prerequisites are unknown, no specific feature disablement, port blocking, or endpoint restriction can be recommended without risking unnecessary loss of functionality - commit to those measures only after the USN identifies the vulnerable subsystem. For the interim, apply host hardening that is low-regret regardless of the eventual root cause: restrict network exposure of Ubuntu services to trusted segments, enforce least privilege on local accounts, keep auditd or equivalent logging enabled for post-incident triage, and snapshot or back up the system before applying a batch update so a regressive patch can be rolled back.

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 only technical anchor in the input is the reporting provenance, vendor:ubuntu, which indicates this identifier is being handled through Ubuntu's security-notice pipeline rather than through a third-party CNA feed with full metadata. Ubuntu is a downstream Debian-derived distribution: an upstream flaw in a library, daemon, or language runtime is typically assigned a CVE, then Canonical publishes a Ubuntu Security Notice (USN) mapping that CVE to the specific binary source packages, affected release series (for example 20.04 LTS, 22.04 LTS, 24.04 LTS, and interim releases), and the patched package versions for each. Since no CWE was supplied, the root-cause class - memory-safety (use-after-free, buffer overflow, integer overflow), injection, race condition (TOCTOU), improper input validation, or access-control failure - is currently undetermined, and each class implies a very different attacker model and mitigation profile. The absence of CVSS metrics and of any CPE string means the affected component (kernel, OpenSSL, systemd, a language runtime, a userspace utility, or a snap) is not yet knowable from this dataset; authoritative detail must be recovered from the corresponding Ubuntu Security Notice and the NVD record once they are populated.

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.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/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
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
CVSS changed
Sep 30, 2026 - 13:22 NVD
4.8 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% 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.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

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