Skip to main content

StationData CVE-2026-73154

MEDIUM
2026-08-13 vendor:ubuntu
View

Attack ChainAIDerived

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

  1. Access
    Supply malformed input to StationData::setData
  2. Exploit
    Trigger stack overflow in setter
  3. Execution
    Corrupt stack memory
  4. Impact
    Potential code execution or crash

Vulnerability Assessment

Exploitation Conditions

Exploitation conditions are not determinable from available data. No CVSS vector is provided, so attack vector, complexity, and privilege requirements are unknown. The vulnerability is in a specific method (StationData::setData), implying a caller must be able to supply input to that method - but whether this is reachable remotely, locally, or only through authenticated interfaces cannot be determined. Authentication requirements not confirmed from available data.

Impact

Risk assessment is severely constrained by missing data: no CVSS score, no CVSS vector, no CWE assignment, no KEV status, no EPSS score, and no POC information are present. The sole intelligence signal is a vendor report from Ubuntu, which indicates the issue was responsibly disclosed through a distribution channel rather than exploited in the wild - though this cannot be confirmed. Without CVSS metrics, attack vector, complexity, and privilege requirements are all unknown. No public exploit identified at time of analysis. Given the sparse data, security teams should treat severity as unconfirmed and consult the Ubuntu Security Notices (USN) tracker directly for updates.

Exploit ScenarioDerived

An attacker capable of supplying malformed or oversized input to the StationData::setData method could trigger a stack overflow, potentially causing a crash or enabling arbitrary code execution depending on memory layout and platform mitigations. No public proof-of-concept exists at time of analysis, and the attack vector and required access level are unconfirmed.

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

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

Alert me

AnalysisAIv1 – Aug 14, 2026

Stack overflow in StationData::setData exposes affected systems to potential memory corruption. The vulnerability is identified via GHSA-5g48-xjmf-7p4q and reported through Ubuntu's vendor channel, suggesting it affects a library or component present in Ubuntu-distributed packages. Specific impact scope is limited by the near-total absence of structured metadata in available intelligence sources.

RemediationAI

No patch version is confirmed from the available data. Monitor the Ubuntu Security Notices page (https://ubuntu.com/security/notices) and the GitHub Security Advisory GHSA-5g48-xjmf-7p4q for patch releases. As a compensating control, restrict access to any service or process invoking StationData::setData to trusted, authenticated callers, and consider deploying stack canary protections or ASLR hardening if not already enabled at the OS level. These mitigations reduce exploitability but do not eliminate the underlying flaw.

Affected ProductsAI

The affected component is identified only as involving the StationData::setData function, referenced in GHSA-5g48-xjmf-7p4q. The reporting source is Ubuntu (vendor channel), suggesting the vulnerability exists in a package distributed via Ubuntu repositories. No CPE strings, specific package names, version ranges, or vendor advisories are available in the current dataset to further scope affected products.

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 vulnerability involves a stack overflow triggered via the StationData::setData method, consistent with CWE-121 (Stack-based Buffer Overflow) or CWE-674 (Uncontrolled Recursion), though no CWE is formally assigned in the available data. Stack overflows in setter methods typically arise from unbounded recursive calls or writing data beyond a fixed-size stack-allocated buffer. No CPE strings are available to precisely identify the affected package, version range, or upstream project.

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

Red Hat CRITICAL

DescriptionCVE.org

[GHSA-5g48-xjmf-7p4q: StationData::setData stack overflow]

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 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.

Attack Technique

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.

Vendor StatusVendor

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