Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInsufficient data to map
-
ExploitVulnerability class unknown
-
ImpactImpact 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 description is unavailable ('[Unknown description]') and no CVSS vector is provided, so no product feature, protocol, configuration setting, deployment mode, authentication level, or user-interaction requirement can be identified. Limiting factors are indeterminate until the Ubuntu advisory or NVD entry supplies a description and affected package. |
| Impact | Risk cannot be meaningfully assessed from the provided data. The only intelligence signal is a reporter attribution (vendor:ubuntu); the description is '[Unknown description]', and the CVSS score, CVSS vector, and CWE are all N/A. There is no EPSS score, no CISA KEV listing, no POC indicator, no SSVC decision data, no affected-product identification, and no references. With no attack vector, complexity, or privilege data, it is impossible to distinguish a genuine priority from a high-CVSS-but-low-real-risk issue - in fact no CVSS score exists at all. The Ubuntu Security Team attribution suggests this most likely concerns a package shipped in the Ubuntu/Debian ecosystem (an open-source component), but the specific product is unknown and this is an inference, not a confirmed fact. CRITICAL: every risk-relevant signal (CVSS, EPSS, KEV, POC, affected component) is missing - no defensible risk statement is possible until the vendor advisory (Ubuntu Security Notice / USN) or the NVD record is published. Do not treat this CVE as either high or low risk on current data; it is unscored and undescribed. |
| Exploit ScenarioDerived | No realistic exploit scenario can be constructed: the vulnerability class, affected product, and attack vector are all unknown from the provided data. No public exploit or POC is indicated in the input. Any scenario would be speculation and is therefore withheld pending a published description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
CVE-2026-95342 cannot be characterized beyond its origin: the record is attributed to the Ubuntu vendor source, but no description, CVSS vector, CWE, or CPE data has been published, leaving the affected package, affected versions, and achievable attacker impact entirely unidentified. No CISA KEV entry and no public exploit code are associated with this identifier, so there is no public exploit identified at time of analysis; equally, no EPSS-style likelihood can be derived without a description or score. Ubuntu administrators should treat this as an intelligence gap rather than a confirmed threat and monitor the vendor advisory channel for the first substantive disclosure.
RemediationAI
No vendor-released patch is identified at time of analysis, and because the affected Ubuntu source package is unknown, no upgrade target version can be specified without inventing data. The primary near-term action is intelligence acquisition rather than mitigation: monitor the Ubuntu CVE tracker entry for CVE-2026-95342 and the ubuntu-security-announce mailing list or Ubuntu Security Notices feed at https://ubuntu.com/security/notices so the fixing version is captured the moment it is published, and enable unattended-upgrades on affected hosts so security-pocket updates apply automatically once available - accepting the trade-off that automatic upgrades can restart services and occasionally require a reboot for kernel packages. As a holding measure, keep AppArmor or SELinux confinement enforced on exposed services and restrict inbound access to only the ports those services genuinely require, with the caveat that these are generic hardening controls that cannot be targeted at the real flaw while it remains undefined and should not be represented to stakeholders as a fix for this CVE.
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 only technical fact available is provenance: the record was reported by the Ubuntu vendor source, which in practice means the authoritative detail will appear as an Ubuntu Security Notice (USN) and a matching entry in the Ubuntu CVE tracker, typically including the affected source package, binary package, release codenames, and the fixed version string. No CWE is assigned, so the root-cause class - for example memory corruption, injection, improper access control, or a logic error - is unknown, and no CPE strings are present to anchor the affected product set. Consequently no protocol, library, or component can be named as the locus of the flaw, and no attack surface (network service, local binary, setuid tool, kernel interface, or web application) can be inferred. The absence of a CVSS vector also means authentication requirements and user-interaction prerequisites are not confirmed from available data and must not be assumed in either direction.
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 (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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
Lifecycle Timeline
1DescriptionCVE.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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allVendor 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 |
EUVD-2026-89164
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB