Skip to main content

Unidentified Ubuntu Package CVE-2026-95507

MEDIUM
2026-09-23 vendor:ubuntu
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Unknown access vector
  2. Exploit
    unknown vulnerability trigger
  3. Impact
    unknown impact

Vulnerability Assessment

Exploitation Conditions

Cannot be determined - the description is empty and no CVSS vector is provided, so no product feature, protocol, configuration setting, deployment mode, authentication level, or user-interaction requirement can be identified. Authentication requirements not confirmed from available data.

Impact

Risk cannot be meaningfully assessed from the available data. The only intelligence signal present is that this CVE was reported by vendor:ubuntu; there is no description, no CVSS base score or vector, no CWE, no EPSS probability, no CISA KEV listing, no public POC reference, no patch/reference URLs, and no CPE strings. With no CVSS vector, attack vector/complexity/privilege requirements are all unknown, and no SSVC decision (exploitation/automatable/technical impact) can be derived. Exploitation status: no public exploit identified at time of analysis. This is neither confirmable as high-risk nor dismissible as low-risk - it is simply unanalyzable until NVD or the vendor publishes details. Note: the CVE ID sits well ABOVE the September-2026 Google Chrome desktop batch (CVE-2026-95344 through CVE-2026-95385, each of which carried a chrome-releases reference); this record has NO such reference, so it must NOT be assumed to be Chrome despite the shared ubuntu-reporter shape. Recommend re-triage once authoritative data lands.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected product, and attack vector are all unknown. No public proof-of-concept is referenced in the provided data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 24, 2026

Impact for CVE-2026-95507 cannot be characterized because the record carries no description, no CVSS vector, no CWE, and no CPE data; the only signal is that the issue was reported through Ubuntu's vendor channel. Nothing in the available intelligence establishes what an attacker could do, which component or version is affected, or whether the flaw is remotely or locally reachable. Exploitation status is likewise unknown: no CISA KEV listing or public proof-of-concept is present in the supplied data, and authentication requirements cannot be confirmed from the available information.

RemediationAI

No vendor-released patch is identified in the available data, and no fix version, commit, or pull request is provided, so a specific upgrade target cannot be named. The primary actionable step is to retrieve the authoritative record: check the Ubuntu CVE tracker entry for CVE-2026-95507 and any associated USN security notice, which will name the affected source package, the fixed package version, and the supported Ubuntu releases, then stage that exact version through the normal apt workflow. Until the affected component is identified, no meaningful compensating control can be recommended - disabling a feature, blocking a port, or restricting an endpoint all require knowing which package and interface are involved, and applying a generic control would carry cost without a demonstrable risk reduction. In the interim, subscribe to Ubuntu security notices and re-run package inventory tooling against the tracker once the entry is populated; treat any third-party claim of patch availability for this CVE as unconfirmed absent a cited advisory.

Affected ProductsAI

Affected products and versions are not specified in the available data. No CPE strings, no vendor advisory text, and no version ranges were supplied, and the only attributable metadata is a report origin of vendor:ubuntu, which suggests the affected component is distributed or maintained through Ubuntu packaging rather than identifying a concrete product. Because no reference URLs were included, there is no Canonical security notice, Ubuntu CVE tracker page, or upstream advisory to cite. Until the Ubuntu security tracker entry (ubuntu.com/security/CVE-2026-95507) is retrieved and any linked upstream advisory is read, the affected package set must be treated as unknown, and any deployment inventory claiming coverage of this CVE should be considered unverified.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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 this identifier. The CWE is unassigned, so the root-cause class (for example injection, memory corruption, deserialization, or access-control failure) cannot be inferred, and no CPE strings are provided to pin the affected product, vendor, or version range. The sole intelligence source is a vendor attribution to Ubuntu, which indicates the issue is tracked inside the Ubuntu security process - most likely a flaw in a package shipped through Ubuntu repositories or in a component Canonical maintains - but vendor attribution alone says nothing about the underlying library, protocol, or subsystem involved. No CVSS vector is present, so privilege requirements (PR), attack vector (AV), and user-interaction (UI) values are all undetermined, and the independent assessment correctly concludes that no product feature, deployment mode, or configuration prerequisite can be identified from the record as given.

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

SUSE 3.5 LOW
AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Red Hat PRIMARY 4.3 MEDIUM

Primary rating from Red Hat.

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

Data Quality
1 sources
Confidence: Low
CVE.org Vendor

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 N/A
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.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Low
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Micro 5.3 Affected
SUSE Linux Enterprise Micro 5.4 Affected
SUSE Linux Enterprise Micro 5.5 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy