Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInsufficient data to determine access vector
-
ExploitVulnerability class unknown
-
ImpactImpact unknown
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery 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 extracted - the input provides no description, feature, protocol, configuration setting, deployment mode, or CVSS vector from which to derive prerequisites or limiting factors. The sole available signal (reported by vendor:ubuntu) suggests the affected component is a package shipped or tracked by Ubuntu, but neither the package nor whether default configurations are exploitable can be determined. Retrieve the advisory from the Ubuntu CVE tracker to establish concrete prerequisites. |
| Impact | Risk cannot be meaningfully assessed from the provided data. The description is '[Unknown description]', CVSS score and vector are N/A, and CWE is N/A, so no attack vector, complexity, or privilege signal is available to weigh. There is no EPSS score, no CISA KEV listing, and no POC indicator in the input, which means exploitation status defaults to 'no public exploit identified at time of analysis' - but this reflects absence of data, not confirmed absence of risk. The only signal is that the CVE was reported by vendor:ubuntu, which typically indicates a vulnerability tracked in the Ubuntu Security Notice / CVE tracker for a Linux distribution package, but the specific package, severity, and Ubuntu priority rating are all unknown. CONFLICT/GAP: with zero CVSS metrics and no description, any risk rating (low or high) would be a guess. This CVE must be re-enriched from the Ubuntu CVE tracker (https://ubuntu.com/security/CVE-2026-95312) and NVD before triage; treat current priority as indeterminate, not low. |
| Exploit ScenarioDerived | No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all absent from the provided data. No POC is referenced in the input. Enrichment from the Ubuntu security tracker is required before any realistic scenario can be described. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
CVE-2026-95312 is currently an intelligence gap: the only available signal is a report attributed to vendor:ubuntu, with no description, CVSS score, CVSS vector, CWE classification, CPE mapping, or reference links supplied. Because the affected package, attack vector, and privilege requirements are all unknown, the practical impact on Ubuntu systems cannot be characterized at this time, and no public exploit code has been identified at time of analysis. Notably, EPSS scoring and CISA KEV status were not included in the input, so neither heightened exploitation likelihood nor confirmed actively exploited (CISA KEV) status can be asserted or ruled out; risk cannot be meaningfully assessed from the provided data, and the Ubuntu CVE tracker entry for CVE-2026-95312 should be retrieved as the first analyst action.
RemediationAI
No vendor-released patch identified at time of analysis. With no affected package name, no version range, and no advisory link in the input, specific remediation steps and compensating controls cannot be prescribed without risking misdirection. The concrete next actions are: query the Ubuntu CVE tracker page for CVE-2026-95312 to identify the affected source package(s) and per-release status; if a status of 'released' appears, apply the corresponding package upgrade using apt update && apt full-upgrade (or apt install --only-upgrade <package>) on the affected series, and for Ubuntu Pro subscribers enable esm-apps/esm-infra where the package is covered; if the status is 'needs-triage' or 'deferred', subscribe to the Ubuntu security-announce list and the USN feed so the fix version is captured the moment it lands. The Ubuntu Security Notice for the package, once published, supersedes this analysis. Until the component is identified, avoid speculative mitigations such as disabling services or restricting ports, since applying them to the wrong package imposes availability costs without confirmed security benefit; if a temporary exposure exists in the interim, the defensible generic control is to review and log access to internet-facing Ubuntu hosts running the unknown component rather than to alter configuration blindly.
Affected VersionsENISA
Affected Packages
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 contains no CWE mapping, so the root-cause class - whether memory corruption, injection, deserialization, race condition, path traversal, or a logic error - is undetermined. No CPE strings were provided, meaning the exact affected component (for example a specific source package, a Snap, a kernel module, or an Ubuntu-maintained library) cannot be identified from the input alone; the single attribution to vendor:ubuntu indicates only that the issue is tracked within the Ubuntu security ecosystem, most plausibly as an upstream CVE inherited into one or more Ubuntu source packages. There is also no protocol, subsystem, or configuration context to reason about, so statements about whether default installations are reachable, whether authentication is required, or whether the flaw is local versus remote would be speculation rather than analysis. Establishing technical context requires pulling the Ubuntu CVE page (which typically records the affected source package, Ubuntu release statuses such as needs-triage, not-affected, or released, and links to a USN advisory) plus any linked upstream commit, issue tracker entry, or NVD record that may have appeared after this feed was generated.
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
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Primary rating from Vendor (vendor:ubuntu) · only source for this CVE.
CVSS VectorVendor: vendor:ubuntu
DescriptionCVE.org
[Unknown description]
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-89139
GHSA-hhgr-vg3r-4f5h
NVD
CVE.org
EPSS
Exploit-DB