Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessUnknown access vector
-
ExploitUnknown vulnerability triggered
-
ImpactUnknown 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 | Cannot be determined - the description is empty and no CVSS vector is provided, so required features, protocols, configuration settings, authentication level, user interaction, or deployment mode are all unknown. No claim can be made about whether default configurations are affected or what limits exploitation, because the affected product and flaw are unidentified in the input. |
| Impact | Risk cannot be meaningfully assessed from the provided data. There is no CVSS score or vector (so attack vector, complexity, privileges, and scope are all unknown), no CWE, no EPSS probability, no KEV listing, no POC indication, and no SSVC decision inputs. The only signal is that the CVE was surfaced via the Ubuntu security tracker (reported by vendor:ubuntu), which mirrors upstream advisories but by itself conveys neither severity nor exploitability. No affected product, version range, or reference URL is supplied, so it is impossible to distinguish a genuine priority from a low-real-risk issue. All exploitation-relevant signals are MISSING and must be retrieved from the authoritative source (NVD record and the upstream vendor advisory the Ubuntu tracker points to) before any prioritization decision is made. |
| Exploit ScenarioDerived | No exploit scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown from the provided data. No public exploit or proof-of-concept is identified at time of analysis. The affected product and the nature of the flaw must first be established from the upstream advisory referenced by the Ubuntu tracker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
CVE-2026-95300 is currently an unpopulated record: the supplied intelligence contains no description, no CVSS score or vector, no CWE classification, and no CPE data, so the flaw's nature and impact cannot be characterized at this time. The single attribution available is that the record was reported by the Ubuntu vendor source, which suggests Ubuntu may be the coordinating or affected vendor, but no package, version, or component is identified. With no KEV listing and no public exploit code referenced in the input, there is no public exploit identified at time of analysis, and risk cannot be meaningfully assessed from the provided data.
RemediationAI
No vendor-released patch identified at time of analysis, because no affected component, version, or fixed release is specified in the input. Because the vulnerable product is unknown, there is no specific feature to disable, port to block, or endpoint to restrict; any such instruction would be guesswork and could cause operational harm without reducing real risk. The actionable steps are intelligence-gathering ones: monitor the authoritative CVE record for the assignment of a description, CWE, CVSS vector, and CPE list; subscribe to the Ubuntu security notices feed and the ubuntu-security-announce mailing list so that a USN is received the moment the Ubuntu security team publishes fixed package versions; and check Ubuntu's CVE tracker entry for this identifier to see whether a package and patch state have been recorded. If an Ubuntu package is subsequently confirmed as affected, the remediation will be to apply the exact patched package version named in that USN via apt upgrade rather than guessing at a version number. Until then, treat this as an unverified record and avoid deploying blanket mitigations against unidentified software.
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 available for CVE-2026-95300. The input provides no CWE, which would normally identify the root-cause class (for example injection, memory corruption, or access-control failure), no CVSS vector, which would normally identify attack vector, complexity, privileges required, and user interaction, and no CPE strings, which would normally pin the vulnerability to a specific product and version range. The sole metadata point is the reporting source, 'vendor:ubuntu', implying that the Ubuntu security team either assigned or relayed this identifier, but that is an attribution signal, not evidence about the affected component, the vulnerable subsystem, or the underlying protocol or library involved. Because the affected technology stack is unidentified, no statement can be made about whether default configurations are affected, whether exploitation requires authentication, or what deployment modes are exposed. Independent assessment concurs with this gap: exploitation conditions cannot be determined, and no claim about prerequisites or configuration limits is supportable from the available data.
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:H/PR:N/UI:N/S:U/C:L/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-89135
GHSA-m457-wf75-q9cx
NVD
CVE.org
EPSS
Exploit-DB