Skip to main content

Ubuntu Linux CVE-2026-91766

| EUVDEUVD-2026-87357 MEDIUM
Information Exposure (CWE-200)
2026-09-24 vendor:ubuntu
5.9
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 determine attack path
  2. Exploit
    Vulnerability class and vector unknown
  3. Impact
    Impact undetermined

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation prerequisites cannot be determined - the description, affected product, protocol, and configuration requirements are all absent from the input. No CVSS vector is available to indicate attack vector, required privileges, or user interaction, so neither the conditions enabling exploitation nor the factors limiting it can be stated. Retrieval of the Ubuntu Security Notice for CVE-2026-91766 is required to establish any concrete condition.

Impact

Risk cannot be meaningfully assessed from the available data. No CVSS base score or vector is provided (attack vector, complexity, and privilege requirements are all unknown), no CWE classifies the weakness, and the description is entirely absent. There is no EPSS exploitation-probability signal, no CISA KEV listing, and no indication of public proof-of-concept code, so exploitation status is 'no public exploit identified at time of analysis.' The only intelligence signal is that the entry was reported by vendor:ubuntu, which suggests this is tracked via an Ubuntu Security Notice for a package shipped in the Ubuntu ecosystem, but the affected component, impact type, and severity are all unconfirmed. This should be treated as an UNTRIAGED placeholder, not a validated priority: it is neither confirmed high-risk nor confirmed low-risk. STATE EXPLICITLY: no description, no CVSS vector, no CWE, and no affected-product identity are available - all substantive analysis is blocked pending retrieval of the Ubuntu advisory and NVD/MITRE record.

Exploit ScenarioDerived

No realistic attack scenario can be constructed because the vulnerability class, affected component, and attack vector are all unknown. No public exploit or proof-of-concept has been identified in the available data. Retrieving the underlying Ubuntu Security Notice is required before any scenario can be described.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 25, 2026

CVE-2026-91766 is referenced only through a vendor-originated report from Ubuntu (vendor:ubuntu), and the identifier arrives with no description, no CVSS score or vector, no CWE classification, no CPE data, and no version information. Because the affected component, attack vector, and required privileges are all undefined, the concrete impact on Ubuntu systems cannot be stated, and risk cannot be meaningfully assessed from the available data. No public exploit has been identified at time of analysis, and patch availability could not be determined from the provided data; analysts must retrieve the corresponding Ubuntu Security Notice or the Ubuntu CVE tracker entry to establish the affected source package, supported releases at risk, and any prerequisites.

RemediationAI

Patch availability could not be determined from the provided data, since no fix version, advisory link, or patch reference was included with this record; no vendor-released patch version is identified at time of analysis. The first actionable step is to resolve the information gap: query the Ubuntu CVE tracker entry for CVE-2026-91766 at https://ubuntu.com/security/CVE-2026-91766 and the Ubuntu Security Notices index at https://ubuntu.com/security/notices to identify the affected source packages, the releases in scope, and the fixed package versions. Where the affected host is enrolled in Ubuntu Pro, the applicable USN will also indicate whether a Livepatch or ESM fix is available for running kernels or end-of-standard-support installations. Once the package is identified, standard Ubuntu update channels apply fixes via apt update followed by apt upgrade (or apt install --only-upgrade for the specific package), and hosts should be inventoried with apt list --upgradable or ubuntu-security-status to confirm every affected system is remediated before the change window closes. Because the attack vector, required privileges, and configuration prerequisites are all unknown, no specific compensating control can be recommended at this stage - measures such as disabling a service, restricting network exposure, or tightening file permissions would be guesswork and could break functionality without reducing risk; confirming the component first is a prerequisite for choosing between an emergency patch cycle and a scheduled one. Until the advisory is retrieved, treat the identifier as unresolved rather than assuming either low or high severity.

Affected VersionsENISA

PHP 8.3.* <8.3.35
PHP 8.2.* <8.2.34
PHP 8.4.* <8.4.26
PHP 8.5.* <8.5.11

Affected Packages

euvd php_8_2 fix: 8.2.34
euvd php_8_3 fix: 8.3.35
euvd php_8_4 fix: 8.4.26
euvd php_8_5 fix: 8.5.11

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Technical context is effectively absent for this identifier. No CPE strings were supplied, so the affected product cannot be pinned to a specific package, library, or kernel subsystem; the only signal is the reporter field, vendor:ubuntu, which indicates the record originates from Canonical's vulnerability tracking process rather than from an upstream project disclosure. No CWE is provided, which means the root-cause class (memory corruption, injection, improper access control, cryptographic weakness, and so on) is unknown and cannot be inferred. In the Ubuntu ecosystem, a CVE identifier is typically tied to one or more Ubuntu Security Notices that enumerate the affected source packages across supported releases (LTS and interim), so the same CVE can affect a kernel module, a language runtime, a networking daemon, or a desktop utility depending on how the flaw was introduced. Without the USN, the CVE tracker page, or any patch reference, there is no way to determine whether this is a remotely reachable service flaw, a local privilege-escalation condition, or a lower-severity correctness issue. The absence of a CVSS vector is especially significant here because it removes the only structured mechanism for knowing whether exploitation requires network access, a valid account (PR:L/PR:H), or user interaction, so authentication requirements are not confirmed from 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

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

Primary rating from Vendor (vendor:ubuntu).

CVSS VectorVendor: vendor:ubuntu

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

Lifecycle Timeline

2
Patch available
Sep 25, 2026 - 22:04 EUVD
CVSS changed
Sep 25, 2026 - 21:22 NVD
5.9 (MEDIUM)

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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 Yes
EPSS 0.3%
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.

SSVC AssessmentENISA

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

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: +20
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
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS Affected
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS Affected
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS Affected
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS Affected

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