Skip to main content

Unspecified Ubuntu component CVE-2026-95296

| EUVDEUVD-2026-89165 MEDIUM
Missing Authorization (CWE-862)
2026-09-23 vendor:ubuntu GHSA-jxq8-c8p7-9vrc
Medium
Disputed · 4.3 Vendor: vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Unknown access vector
  2. Exploit
    Unknown vulnerability trigger
  3. Impact
    Unknown impact

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
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 description is unavailable and no CVSS metrics are provided, so no product feature, protocol, configuration setting, or deployment mode can be named. Authentication requirements are not confirmed from available data. The only known fact is that the issue was reported via Ubuntu, suggesting it affects an Ubuntu-packaged component; the specific package, enabling configuration, and limiting factors must be obtained from the Ubuntu Security Notice for CVE-2026-95296.

Impact

Risk cannot be meaningfully assessed from the provided data. The description is '[Unknown description]', there is no CVSS score or vector, no CWE, no EPSS probability, no KEV listing, and no POC indicator - the only signal is that the CVE was reported by 'vendor:ubuntu' (i.e. it likely corresponds to an Ubuntu Security Notice / USN for a packaged open-source component). With no attack vector, complexity, privilege, or impact metrics available, it is impossible to distinguish a genuine priority from a low-real-risk issue. All exploitation-related signals are MISSING: no active-exploitation evidence (KEV absent, but absence is not confirmation of non-exploitation), no public exploit identified, and no SSVC decision data. Any severity claim here would be fabricated. Recommendation: retrieve the actual Ubuntu USN / NVD record for CVE-2026-95296 to obtain the affected package, version range, CVSS vector, and CWE before triage.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected product, and attack vector are all unknown. No public exploit has been identified in the provided data. Consult the corresponding Ubuntu Security Notice for the affected package and technical details.

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-95296 currently has no published description, no CVSS score, no CWE classification, and no CPE identifiers; the only intelligence signal available is that it was reported through the Ubuntu vendor channel, indicating the flaw resides in a component packaged, shipped, or maintained within an Ubuntu release. Because the affected package, version range, exposed feature, and attack path are all unidentified, no impact statement can be made and risk cannot be meaningfully assessed from the provided data. There is no evidence of active exploitation (no CISA KEV entry was supplied) and no public exploit identified at time of analysis.

RemediationAI

No vendor-released patch information was included in the provided intelligence, so patch status is undetermined rather than confirmed absent. The primary action is to monitor and consume the Ubuntu fix: check https://ubuntu.com/security/CVE-2026-95296 for the package and release table, subscribe to the ubuntu-security-announce list and to USN notifications at https://ubuntu.com/security/notices, and query the local system with 'pro fix CVE-2026-95296' (or 'pro fix --dry-run CVE-2026-95296') on Ubuntu Pro-enabled hosts and 'ubuntu-security-status' on standard hosts to see whether an update applies to the installed package set. Applying updates normally (apt update && apt full-upgrade) will pull the fixed package once published; if unattended-upgrades is used, note the trade-off that security updates may restart affected services, so schedule maintenance windows or configure service-specific restart policies. Because the vulnerable package is unknown, no targeted compensating control can be recommended - disabling a feature, blocking a port, or restricting an endpoint would be guesswork, and any generic hardening such as network segmentation or tightening firewall rules carries cost without confirmed benefit for this specific issue. Where an affected host cannot be patched promptly, the only defensible interim measure is reducing exposure of the unidentified component by limiting who can reach the service, accepting the operational impact of that restriction, and prioritizing the host for patching as soon as the USN identifies the package and fixed version.

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 underlying technology, library, or protocol involved cannot be determined from the available data. No CWE was assigned in the supplied intelligence, so the root-cause class - whether memory corruption, input validation failure, privilege management error, or logic flaw - is unknown. No CPE strings were provided, which means the exact affected package, upstream project, and version boundaries cannot be mapped to a product identity. The single attribution, 'vendor:ubuntu', places this CVE within the Ubuntu security ecosystem: Ubuntu tracks CVEs for packages in main and universe, publishes Ubuntu Security Notices (USNs) when fixes ship, and backports patches to supported releases including LTS versions under standard maintenance and to older releases under Ubuntu Pro/ESM. In that model, the upstream project may not be Ubuntu itself but a third-party component that Ubuntu packages, meaning the definitive technical detail will come from the Ubuntu CVE tracker entry and its linked USN rather than from the CVE record. Until that tracker entry is enriched with a package name, affected version set, and patch state, any statement about exploitable code paths, protocol exposure, or privilege requirements 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:L/I:N/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
Low
Integrity
None
Availability
None

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

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

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