Skip to main content

Ubuntu Linux CVE-2026-92842

| EUVDEUVD-2026-87351 MEDIUM
Heap-based Buffer Overflow (CWE-122)
2026-09-24 vendor:ubuntu
Buffer Overflow Heap Overflow Red Hat Suse
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 reconstruct attack chain
  2. Exploit
    Affected component unknown
  3. Impact
    Verify with Ubuntu Security Notice

Vulnerability Assessment

Weakness
CWE
CWE-122
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

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

Sign in to read
Exploitation Conditions

Cannot be determined - the input contains no description, CVSS vector, or affected-product identity, so no product feature, protocol, configuration setting, deployment mode, authentication level, or user-interaction requirement can be named. The only fact available is that the vulnerability was reported through Ubuntu's security process, indicating a package in the Ubuntu/Debian archive, but neither the package nor its exploitation prerequisites are specified. Authentication requirements not confirmed from available data. Consult the corresponding Ubuntu Security Notice (USN) and NVD entry to establish concrete conditions.
Impact

Risk cannot be meaningfully assessed from the provided data. There is no CVSS base score or vector, no CWE, no description, no EPSS exploitation-probability value, no KEV listing, no POC indicator, and no SSVC inputs (exploitation status, automatability, technical impact). The only signal is that the record was reported by the Ubuntu security team (vendor:ubuntu), which implies the flaw affects a package shipped in the Ubuntu/Debian ecosystem, but the specific component, attack vector, privilege requirement, and impact are all unknown. With every scoring dimension missing, this cannot be triaged as either a genuine priority or a high-CVSS-but-low-real-risk issue - status is indeterminate. Exploitation status: no public exploit identified at time of analysis. This record should be re-queried against NVD/Ubuntu Security Notices (USN) once metadata is populated before any prioritization decision is made.
Exploit ScenarioDerived

No realistic scenario can be constructed because the affected component, attack vector, and impact are absent from the input. Any scenario written now would be pure speculation and is therefore withheld. Re-analysis is required once a description and CVSS vector are available.
This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 25, 2026

Ubuntu Linux packages are implicated by a security defect reported through Canonical's coordinated disclosure process, but the intelligence set contains no description, CVSS vector, CWE classification, affected package name, version range, or reference links. Because neither the vulnerable component nor the attack surface can be identified, it is not possible to state whether the issue is remotely or locally exploitable, what privileges an attacker would need, or what level of impact (code execution, privilege escalation, denial of service, information disclosure) would result. No public exploit code and no CISA KEV entry are indicated in the available data, and no vendor patch version is identified at time of analysis; treat this record as unresolved pending retrieval of the corresponding Ubuntu Security Notice (USN) and NVD entry.

RemediationAI

No fix version, patch reference, or vendor advisory is present in the provided data, so patch availability cannot be established; the correct first step is to retrieve the Ubuntu Security Notice and the Ubuntu CVE tracker entry, which will name the affected source package, the affected releases, and the fixed package version per release, then apply that version with apt update && apt install --only-upgrade <package> or by enabling unattended-upgrades for the security pocket. Because the vulnerable component is unknown, no component-specific workaround such as disabling a feature, blocking a port, or restricting an endpoint can be prescribed at this time - any such advice would be invented rather than derived from data. Interim measures an Ubuntu operator can take that are safe regardless of the eventual finding include subscribing to the ubuntu-security-announce list and monitoring the CVE tracker for this identifier so the advisory is actioned quickly, keeping the security pocket enabled and verified so the fix lands automatically once published, and inventorying which Ubuntu hosts and container base images could receive the eventual update; the trade-offs are that these steps reduce time-to-patch but do not mitigate an unknown flaw, and aggressive unattended-upgrade policies can restart services unexpectedly if reboot or service-restart behavior is not pinned. If a USN later indicates an exploitable remote condition and patching must be delayed, the fallback is network-level restriction of the exposed service, accepting the availability and operational cost that implies.

Affected VersionsENISA

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

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.

Sign in to check
Technical ContextAI · show details

No CPE strings, no CWE mapping, and no cross-references were supplied, so the underlying technology, library, or protocol cannot be determined and no root-cause class can be assigned. The single data point is the reporting channel: the issue was reported by the vendor tagged as Ubuntu, which means it flowed through Canonical's security process and therefore most likely affects a source package maintained in the Ubuntu (and by extension Debian-derived) archive - but the specific package, its upstream project, and whether the flaw sits in Ubuntu-specific packaging, a patched delta, or unmodified upstream code are all unknown. Ubuntu advisories of this type typically arrive as a USN describing affected Ubuntu releases, the source package, and the fixed version, with a corresponding entry in the Ubuntu CVE tracker; absent those artifacts, any statement about the vulnerable function, input handling, memory-safety class, or configuration dependency would be speculation. Analysts should retrieve the USN, the Ubuntu CVE tracker page, and the NVD record before attempting to reproduce, triage, or score the issue.

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
Continue with Google Continue with GitHub

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

1
Patch available
Sep 25, 2026 - 22:04 EUVD

DescriptionCVE.org

[Unknown description]

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS MSRC Vendor GitHub VulDB

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.4%
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
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

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

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Heap Overflow HIGH

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

Same weakness CWE-122 – Heap-based Buffer Overflow

View all
CVE-2023-4911 HIGH POC
7.8
CVE-2023-27997 CRITICAL
9.8
CVE-2026-94127 CRITICAL POC
9.3
CVE-2025-25249 CRITICAL POC
9.8
CVE-2026-85880 HIGH POC
7.8
CVE-2025-24985 HIGH POC
7.8
CVE-2026-53362 HIGH POC
7.8
CVE-2025-21418 HIGH
7.8

Same technique Buffer Overflow

View all
CVE-2017-7269 CRITICAL POC
9.8
CVE-2015-5119 CRITICAL POC
9.8
CVE-2015-3113 CRITICAL POC
9.8
CVE-2011-2462 CRITICAL POC
9.8
CVE-2020-0796 CRITICAL POC
10.0
CVE-2019-11043 CRITICAL POC
9.8
CVE-2009-0927 HIGH POC
8.8
CVE-2012-1889 HIGH POC
8.8

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

References

Advisories & patches
ADVISORY https://access.redhat.com/errata/RHSA-2026:70720 ADVISORY https://github.com/php/php-src/security/advisories/GHSA-88hq-2827-7pg6 ADVISORY https://vuldb.com/vuln/410482

Search Externally

GitHub PoC Exploit-DB PacketStorm Snyk Rapid7 Nuclei Templates Trickest PoC
Back

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