Skip to main content

Ubuntu Linux EUVDEUVD-2026-88013

| CVE-2026-96279 MEDIUM
Improper Link Resolution Before File Access (CWE-59)
2026-09-23 vendor:ubuntu
6.5
CVSS 3.1 · Vendor: vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Insufficient data to construct attack chain
  2. Exploit
    Retrieve GHSA-9rww-v4mm-x4jg details
  3. Impact
    Reassess once vector and impact are known

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
Exploitation Conditions

Cannot be determined from available data. The advisory description for GHSA-9rww-v4mm-x4jg was not provided and could not be retrieved, so the specific product feature, protocol, configuration setting, deployment mode, authentication level, or user-interaction requirement that gates exploitation is unknown. No claim about default-configuration exploitability can be made. Analysts must open GHSA-9rww-v4mm-x4jg (and the corresponding Ubuntu Security Notice) to extract the concrete prerequisites and limiting factors.

Impact

Risk cannot be meaningfully assessed from the provided data. The only inputs are the CVE identifier CVE-2026-96279, a single GitHub Security Advisory reference (GHSA-9rww-v4mm-x4jg), and a reporter attribution of 'vendor:ubuntu'. There is NO description text, NO CVSS base score or vector, NO CWE, NO EPSS probability, NO CISA KEV listing, NO SSVC decision data, and NO POC indicator in the supplied intelligence. Consequently attack vector, complexity, privilege requirements, and technical impact are all unknown, and no signal comparison or contrast is possible. The presence of a GHSA reference implies the affected component is likely open-source software tracked in the GitHub Advisory Database and packaged in Ubuntu, but the specific package, ecosystem, and severity are not derivable from the input. This item MUST be treated as unassessed pending retrieval of the GHSA advisory contents - it cannot be judged either a real priority or a low-real-risk issue with the data at hand.

Exploit ScenarioDerived

No exploit scenario can be constructed because the vulnerability class, affected product, and attack vector are entirely absent from the provided data. No POC availability is indicated in the input. Retrieving GHSA-9rww-v4mm-x4jg is required before any realistic scenario can be described.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.6% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 24, 2026

CVE-2026-96279 is tracked against software maintained in the Ubuntu archive, based on the only source of intelligence available: a report attributed to the vendor:ubuntu channel that cross-references GitHub advisory GHSA-9rww-v4mm-x4jg. The advisory text itself was not supplied and could not be retrieved, so the vulnerable component, version range, attack vector, and security impact remain undefined; no CVSS score, CVSS vector, or CWE classification was provided. No public exploit code has been identified at time of analysis, and there is no KEV listing or EPSS signal to indicate active exploitation, so the practical risk cannot be meaningfully assessed until the underlying advisory is read. The authenticated/unauthenticated question cannot be answered because no CVSS vector containing PR metrics was provided, and no fix version appears in the available data.

RemediationAI

No vendor-released patch or fixed version is identified in the available data, and no advisory URL, GitHub PR, or commit was supplied, so remediation cannot yet be tied to a concrete upgrade target; verify fix status directly against GHSA-9rww-v4mm-x4jg and the corresponding Ubuntu Security Notice before taking action. The immediate actionable step is to resolve the information gap: pull the GHSA record and the Ubuntu Security Notice, extract the affected source package and Ubuntu releases, then check whether each host has that package installed via dpkg-query or apt list --installed and compare against the versions the advisory marks as vulnerable. Until the affected feature is known, only provisional controls can be applied and each has real trade-offs - for example, disabling the corresponding service unit or removing the package where it is not required eliminates exposure but may break dependent workloads, and restricting network access to the exposed interface with ufw or an upstream firewall reduces reachable attack surface but does nothing against local or already-authenticated attack paths. If the advisory later indicates a configuration gate, prefer tuning that setting over uninstalling. Patch status cannot be determined from the provided data, so do not defer hardening on the assumption that a fix is imminent; track the Ubuntu Security Notice feed for the CVE ID and apply the update as soon as a fixed package version is published.

Affected ProductsAI

The only confirmed data point is that the affected software is maintained by the Ubuntu security team, so the products in scope are Ubuntu packages within the currently supported release set; the reporter attribution is vendor:ubuntu. No package name, no version range, no CPE strings, and no upstream project name were provided, and the referenced GitHub advisory GHSA-9rww-v4mm-x4jg could not be retrieved to identify the upstream component. Because the specific package and the affected Ubuntu releases (for example 20.04 LTS, 22.04 LTS, 24.04 LTS, or intermediate releases) are unknown, no accurate affected-version statement can be made at this time. Enumerating affected systems requires opening the GHSA record and the matching Ubuntu Security Notice, which together should list the upstream project, the vulnerable windows, and the fixed package versions.

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

The identifier format GHSA-9rww-v4mm-x4jg is a GitHub Security Advisory ID, which means the underlying defect was reported through GitHub's Advisory Database workflow against an open-source project, and the Ubuntu security team subsequently flagged it as affecting a package or packages they maintain and ship. That combination implies a component present in Ubuntu's supported release set, but the CPE data, CWE classification, and affected library/protocol are all absent from the supplied intelligence, so the root-cause class (for example injection, memory-safety, deserialization, or authorization weakness) cannot be stated. Without the advisory body there is no basis to describe the vulnerable feature, the deployment mode it requires, or the trust boundary an attacker would have to cross. Analysts should treat GHSA-9rww-v4mm-x4jg as the authoritative technical source and the corresponding Ubuntu Security Notice as the authoritative packaging and version-range source, then re-run the assessment once both are available.

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

Vendor (vendor:ubuntu) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
SUSE MEDIUM
Red Hat 6.5 MEDIUM

Primary rating from Vendor (vendor:ubuntu).

CVSS VectorVendor: vendor:ubuntu

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

1
CVSS changed
Sep 27, 2026 - 20:22 NVD
6.5 (MEDIUM)

DescriptionCVE.org

[GHSA-9rww-v4mm-x4jg]

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Data Quality
5 sources
Confidence: Medium

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 0.6%
Patch available No
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.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

33
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Module for Desktop Applications 15 SP7 Not-Affected
SUSE Linux Enterprise Server 15 SP7 Not-Affected
SUSE Linux Enterprise Server 16.0 Not-Affected
SUSE Linux Enterprise Server 16.1 Not-Affected

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