Skip to main content

Unspecified Ubuntu package CVE-2026-95297

| EUVDEUVD-2026-89252 MEDIUM
Missing Authorization (CWE-862)
2026-09-23 vendor:ubuntu GHSA-v39p-rpmc-r9xq
Medium
Disputed · 6.5 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 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

Cannot be determined - the input provides no description, affected component, protocol, configuration setting, deployment mode, or CVSS vector from which to extract prerequisites or limiting factors. The affected product and vulnerability class are both unknown, so neither required conditions nor mitigating constraints can be stated. Re-enrichment from the Ubuntu CVE tracker and NVD is required before exploitation conditions can be identified.

Impact

Risk cannot be meaningfully assessed from the provided data. The only available signal is that this CVE was ingested from the Ubuntu security tracker (vendor:ubuntu); the description is '[Unknown description]', and there is no CVSS base score, no CVSS vector, no CWE, no EPSS probability, no KEV status, no POC indication, no SSVC decision data, no CPE strings, and no references. With no attack-vector, complexity, or privilege metrics, it is impossible to distinguish a high-priority remotely-exploitable flaw from a low-impact local issue. No exploitation-probability or active-exploitation signals are present, so no prioritization conclusion can be drawn. This entry appears to be a placeholder/reserved or not-yet-populated record; it must be re-enriched from the authoritative Ubuntu CVE tracker (ubuntu.com/security/CVE-2026-95297) and NVD before any risk judgment is possible.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown. The description is empty and no POC is referenced. Any scenario stated here would be fabrication.

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

CVE-2026-95297 cannot be scoped from the intelligence supplied: the record contains no description, no CVSS score or vector, no CWE classification, and no CPE data. The only attributable signal is that the entry was reported by the Ubuntu vendor source, indicating the CVE is tracked within Ubuntu's vulnerability management process, but neither the affected package nor the vulnerability class is identified, so the impacted versions, attack surface, and required access level are all unknown. No public exploit identified at time of analysis, and no EPSS, KEV, or proof-of-concept signal is present in the input. Risk cannot be meaningfully assessed from the provided data, and re-enrichment from the Ubuntu CVE tracker and NVD is required before any exposure determination can be made.

RemediationAI

No vendor-released patch identified at time of analysis, and the input contains no fix version, no advisory URL, and no upstream patch reference, so no upgrade target can be prescribed. The immediate action is enrichment rather than remediation: retrieve the authoritative record from the Ubuntu CVE tracker (ubuntu.com/security/CVE-2026-95297) and the NVD entry, identify the affected source package and the fixed version, then apply updates through the standard Ubuntu path (apt update followed by apt install --only-upgrade for the named package, or unattended-upgrades for fleets already configured for security pockets). Because the affected component is unknown, targeted compensating controls cannot be named without risking misapplied restrictions: there is no confirmed port, endpoint, configuration flag, or feature to disable, and imposing broad controls such as network segmentation or service shutdown would carry availability costs disproportionate to an unscoped finding. Until package-level detail is available, treat the CVE as unverified triage, monitor the Ubuntu security announcements and USN feed for the matching notice, and re-run this assessment once the description, CWE, CVSS vector, and patch data are populated.

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 technical detail is recoverable from the provided record. There is no CWE entry to indicate the root-cause class (for example injection, memory corruption, deserialization, or access-control failure), no CVSS vector to establish whether exploitation is network-adjacent, local, or physical, and no CPE strings to map the flaw to a specific library, service, or protocol. The single data point is the reporter attribution 'vendor:ubuntu', which places the CVE inside the Ubuntu security tracking workflow and implies an Ubuntu-packaged component is or may be in scope, but that attribution alone does not identify the upstream project, the vulnerable function, or the deployment mode affected. Because the record was reported through a distribution vendor rather than with upstream advisory detail, the authoritative technical description will most likely appear first in the Ubuntu CVE tracker and then propagate to NVD; until that enrichment is performed, any statement about the underlying technology, the attack vector, or the required privileges would be speculation rather than analysis.

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 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
SUSE CRITICAL
Red Hat 6.5 MEDIUM

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
None
Integrity
High
Availability
None

Lifecycle Timeline

1
CVSS changed
Sep 30, 2026 - 20:53 NVD
6.5 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Data Quality
4 sources
Confidence: Medium

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

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