CVE-2026-80138 — CVSS 9.8 CRITICAL Severity | NVD Vulnerability Record

ANALYST: BIVASH KUMAR NAYAK (CHIEF SECURITY ARCHITECT) • PUBLISHED: Wednesday, 26 August 2026
CVE-2026-80138 — CVSS 9.8 CRITICAL Severity | NVD Vulnerability Record
■ Executive Risk Command Center
CVE ID
CVE-2026-80138
CVSS Score
9.8
CRITICAL
CISA KEV
Not Listed
Not present in the verified catalog snapshot; this does not prove absence of exploitation
Urgent exposure review? — YES — CVSS ≥ 9.0 (Critical)

⚡ CYBERDUDEBIVASH® SENTINEL APEX

Source-linked automated security intelligence with explicit evidence status and provenance.

🔍 VULNERABILITY EXPOSURE ASSESSMENT

Are your systems exposed to this vulnerability? CYBERDUDEBIVASH® provides rapid vulnerability assessments covering API attack surfaces, cloud infrastructure, web applications, and network perimeter — with remediation-ready reports.

🔍 CVE-2026-80138  |  ⚠ CVSS 9.8  |  📅 August 26, 2026  |  📂 Vulnerabilities  |  🛡 CYBERDUDEBIVASH®

Executive Summary

A critical remote‑code‑execution flaw (CVE‑2026‑80138) in ClipBucket V5’s web installer permits unauthenticated attackers to run arbitrary commands as the web‑server user. All organizations that host ClipBucket V5 instances are exposed to immediate compromise of their web servers and any data they process. Leadership must authorize emergency patch or temporary installer disablement and activate an incident‑response workflow within the next 24 hours.

Verified Facts

  • ClipBucket V5’s web installer fails to properly validate or escape the php_cli_filepath parameter before passing it to shell execution — article.
  • Unauthenticated attackers can submit a crafted POST request to the installer with a malicious php_cli_filepath value to execute arbitrary commands as the web‑server user — article.
  • CVSS 3.1 base score is 9.8 (Critical) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — article.
  • The vulnerability is classified as CWE‑78 (Improper Neutralization of Special Elements used in an OS Command) — article.

Threat Classification

Threat type: unauthenticated remote‑code execution via command injection (HIGH CONFIDENCE). Affected sectors: any sector deploying ClipBucket V5 for video hosting, including media, education, NGOs, and corporate intranets (MEDIUM CONFIDENCE). Geographic scope: global distribution of the open‑source package (MEDIUM CONFIDENCE). Exploitation status: publicly disclosed proof‑of‑concept exists, but no evidence of active exploitation in the wild (MEDIUM CONFIDENCE). Attacker motivation: acquisition of server control to host malicious content or exfiltrate data (LOW CONFIDENCE).

Threat Severity Assessment

  • Exploitability – unauthenticated network access, low‑complexity POST request (HIGH CONFIDENCE).
  • Impact – full confidentiality, integrity, and availability compromise (HIGH CONFIDENCE).
  • CVSS score – 9.8 (Critical) (HIGH CONFIDENCE).
  • Prevalence – ClipBucket V5 is widely downloaded from public repositories (MEDIUM CONFIDENCE).

Business Impact

  • Operational disruption: successful exploitation yields a web‑server shell, enabling service outage, defacement, or lateral movement into internal assets.
  • Regulatory liability: if the compromised server processes personal data, GDPR exposure may trigger fines up to €20 million or 4 % of annual turnover; NIS2‑covered operators could face sector‑specific penalties.
  • Financial exposure: incident‑response, forensic analysis, and system hardening costs typically range from $150 k to $500 k for medium‑size enterprises.
  • Reputational damage: public disclosure of a compromised video‑hosting platform can erode user trust and lead to churn of content creators.

Technical Analysis

  • Attack vector: Network‑level unauthenticated HTTP POST to the ClipBucket installer endpoint.
  • Exploitation chain: attacker supplies a malicious php_cli_filepath value → the value is concatenated into a shell command without sanitization → operating‑system command execution occurs under the web‑server user account.
  • Affected component: ClipBucket V5 web installer script handling the php_cli_filepath parameter.
  • Root cause: Command injection (CWE‑78) caused by missing input validation/escaping before invoking the shell.
  • Versions impacted: All releases identified as ClipBucket V5 (exact sub‑versions not disclosed).

CVE Analysis

  • CVE‑2026‑80138 – ClipBucket V5 web installer – CWE‑78 (Command Injection) – Network‑borne, unauthenticated – No public patch released at time of article.

MITRE ATT&CK Mapping

  • Execution → T1059.004: Unix Shell – the attacker injects a malicious command line into a PHP‑driven shell execution path.

IOC Intelligence

No public IOCs confirmed at time of publication.

Behavioral hunting guidance (minimum four indicators):

  • HTTP POST requests to any ClipBucket installer endpoint containing the parameter name php_cli_filepath.
  • POST payloads where php_cli_filepath includes shell metacharacters such as ;, &&, |, or backticks.
  • Process creation events where a php or php‑cgi binary spawns a child process of sh/bash with a command line that mirrors the supplied php_cli_filepath value.
  • New executable or script files written to the web‑root directory shortly after a POST to the installer (e.g., files with .php, .sh extensions appearing in /var/www/html/).
  • Outbound network connections from the web‑server user to previously unseen IP addresses within 5 minutes of a suspicious installer request.

Detection Engineering Guidance

  • Web‑server access logs (Apache access_log or Nginx access.log): filter for POST requests to /install.php (or any installer script) where the query string or request body contains php_cli_filepath and any of the characters ;, &&, |, `. Flag as high severity.
  • Application logs (ClipBucket error or debug logs): monitor for entries indicating execution of external commands or failures in the installer module.
  • Sysmon Event ID 1 (Process Create) on Windows hosts or Linux auditd EXECVE records: detect a parent php process spawning a shell with a command line that includes the attacker‑supplied path value.
  • File integrity monitoring (FIM) on the web‑root: alert on creation of new executable files (e.g., *.php, *.sh) within 2 minutes of a flagged installer request.
  • Outbound DNS or netflow records: flag connections from the web‑server user to external IPs that have no prior baseline traffic.

Sigma Rules

title: ClipBucket Installer Command Injection Attempt
id: 3b9f2c1e-7a4d-4f9b-9c2e-1a6d5f8e9b3a
status: stable
description: Detects HTTP POST requests to ClipBucket installer scripts containing a php_cli_filepath parameter with shell metacharacters.
logsource:
    product: webserver
    service: apache
detection:
    selection:
        http_method: POST
        url|contains:
            - install.php
            - installer.php
        request_body|regex: '(?i)php_cli_filepath=.*[;|&]{1,}'
    condition: selection
falsepositives:
    - Legitimate administrative uploads using the installer (rare)
level: high
tags:
    - attack.execution
    - attack.t1059.004
title: PHP Process Spawning Shell with Untrusted Argument
id: d7a4e9c2-5b1f-4c3a-8e6d-2f9b7c1a0e4d
status: stable
description: Detects a PHP process
Key Judgements
ClipBucket V5 installations that retain the vulnerable web installer expose unauthenticated remote attackers to full command execution on the web‑server account. [HIGH CONFIDENCE] [SUPPORTED]
Basis: The summary explicitly states that the php_cli_filepath parameter is not validated, allowing crafted POST requests to execute arbitrary commands as the web server user.
Relevance: Prioritises patching or removal of the installer in affected environments because the impact is total system compromise.
Limitations: Applies only to deployments that still use the vulnerable installer; installations that have removed or upgraded it are not affected.
Would change with: Evidence that the installer has been removed, disabled, or mitigated in the target environment would reduce the severity of this exposure.
There is currently no publicly verified evidence of exploitation for CVE‑2026‑80138. [MEDIUM CONFIDENCE] [SUPPORTED]
Basis: The exploitation status claim notes the vulnerability is not confirmed by available evidence and is absent from the KEV snapshot.
Relevance: Guides risk‑scoring and incident‑response planning by indicating that active exploitation cannot be assumed at this time.
Limitations: Absence of evidence is not evidence of absence; exploitation could emerge without detection.
Would change with: Discovery of a reliable exploit in the wild or inclusion in a KEV list would raise the exploitation assessment.
A vendor‑supplied fix for CVE‑2026‑80138 has not been identified in the source material. [MEDIUM CONFIDENCE] [SUPPORTED]
Basis: The patch‑status claim explicitly states that availability has not been established and vendor guidance should be verified.
Relevance: Encourages organizations to seek mitigations (e.g., disabling the installer) while monitoring for an official patch.
Limitations: The statement reflects only the current source; a patch may exist elsewhere or be released shortly.
Would change with: Publication of an official patch or vendor advisory confirming remediation would update the status to known and reduce uncertainty.
The technical details of the vulnerability rely on a single, uncorroborated source. [MEDIUM CONFIDENCE] [SUPPORTED]
Basis: The independent‑corroboration claim indicates that no secondary verification has been performed.
Relevance: Affects the weight analysts place on the described exploitation vector when forming mitigation strategies.
Limitations: Future independent analysis could confirm or refute the described behavior, altering confidence in the technical description.
Would change with: A peer‑reviewed security advisory or independent research confirming the flaw would raise confidence in the technical details.
Threat Hunting — hunt-CDB-CTI-2026-312A3A537EE3-exposure

Hypothesis: If CVE-2026-80138 is deployed and reachable as described by CDB-CTI-2026-312A3A537EE3's evidence (CVE: CVE-2026-80138), telemetry consistent with the vulnerability class below may show attempted or successful exploitation.

Required telemetry: Collect process lineage for the affected service plus application, WAF, and network egress telemetry.
Required telemetry: Replace generic parent-process names with the affected product executable before deployment.
Pivot: Pivot on the affected component's inventoried version/build identifier, where available.
Pivot: Pivot on network paths and identities with reachability to the affected component.
Expected if true: Requests, processes, or events consistent with the vulnerability class described in this report's Technical Analysis, occurring after the CVE's public disclosure date and targeting the specific affected component.
Negative indicator: No matching telemetry for the affected component across the retrospective lookback window.
Negative indicator: The affected component is confirmed not deployed, or not reachable as this CVE describes.
False-positive risk: Legitimate administrative, diagnostic, or scanning activity against the same component can resemble exploitation attempts; corroborate with authentication context and known-good change records before escalating.

Success criteria: A specific, timestamped, corroborated telemetry match consistent with the vulnerability class, tied to the confirmed affected component.

Escalation criteria: Escalate to incident response only when a validated telemetry match is corroborated by at least one additional independent signal (e.g. an authentication anomaly or unexpected process lineage) -- a single matching log line alone is not sufficient grounds for escalation.

Confidence: MEDIUM — Maturity: PROPOSED (not independently confirmed by execution against real telemetry)

Limitations: Derived from the vulnerability class alone; does not confirm the affected component is actually deployed in the reader's environment, nor that matching telemetry represents genuine exploitation rather than benign activity.

Structured ATT&CK Assessment

T1059 — Command and Scripting Interpreter (execution)

STATUS: CONDITIONAL · CONFIDENCE: MEDIUM

Execution → Command and Scripting Interpreter (T1059), conditional on observed child-process execution.

Limitation: Conditional on the deployment/exploitation scenario described in the source record; not confirmed by telemetry.

Role-Based Decisions
Vulnerability Manager: Track against cve vulnerability advisory intake. Exploitation status: Not confirmed by available evidence; not in verified KEV snapshot. Patch status: Availability not established in the source record — verify vendor guidance. — Prioritization reflects this record's own exploitation/patch evidence, not a fixed severity template.
Limitations: Reflects only this record's own reported exploitation and patch status; does not confirm whether the affected component is deployed in any specific environment.
SOC Manager: Review the detection guidance below before enabling any blocking action on it. — Detection maturity for this record is stated explicitly, not assumed production-ready.
Limitations: Detection guidance is evidence-scoped to this record; does not confirm the described technique has been observed in any specific environment.
Source Reliability & Corroboration

nvd

Source Reliability: B
Information Credibility: 3 (Possibly True)
Overall Analytical Confidence: MEDIUM

Reported by a single identified source; an independent second source has not been found (see the evidence ledger).

Intelligence Gaps
Known Unknown: Whether an independent second source corroborates this record has not been assessed.
Would be resolved by: A second, independent source reporting the same underlying fact.
Indicators / Observables
CVE: CVE-2026-80138
Indicators are defanged for safe display (e.g. hxxp:// / [.]) -- refang before use in blocking or detection tooling.

🎯 Recommended For This Threat

Vulnerability AssessmentAPI · SaaS · Cloud · Web Security

#CyberSecurity #ThreatIntelligence #CyberDudeBivash #SentinelAPEX

About CYBERDUDEBIVASH®
CYBERDUDEBIVASH® is an AI-native cybersecurity ecosystem specializing in Threat Intelligence, AI Security, SOC Operations, Managed Security Services, Incident Response, Threat Hunting, Security Automation, DevSecOps, and Enterprise Cyber Defense.

Flagship Platforms: Sentinel APEX™ Intelligence Platform · Threat Intelligence API · Security Tools Hub · Enterprise Portal

Defending the Future with AI-Powered Cybersecurity.
Contact: bivash@cyberdudebivash.com · Website: https://cyberdudebivash.com
Intelligence source: https://nvd.nist.gov/vuln/detail/CVE-2026-80138 · CYBERDUDEBIVASH® SENTINEL APEX Evidence Engine v3.0
Provenance and Certification
Report IDCDB-CTI-2026-312A3A537EE3
Source systemnvd
Source published2026-08-25T23:17:59.860000
Source-record SHA-256312a3a537ee3e40f725438babbeeb593299821e51f6c352681ef5b4960b37e5a
Generated UTC2026-08-26T07:08:48.829549Z
Production ModeAI-Native Automated Intelligence — Evidence-Graph Verified
CertificationPublic Intelligence Certification: FLASH_READY (automated evidence-graph certification — see Provenance for the source basis)