Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInsufficient data
-
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 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
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
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)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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-89252
GHSA-v39p-rpmc-r9xq
NVD
CVE.org
EPSS
Exploit-DB