What is the CVSS score of CVE-2026-26093?

CVE-2026-26093 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

How to fix or mitigate CVE-2026-26093?

Within 24 hours: Identify and inventory all systems running Owl OPDS 2.2.0.4; isolate affected systems from production networks if operationally feasible; implement network-level access controls restricting inbound connections to OPDS services. Within 7 days: Deploy WAF rules to block command injection patterns; enable comprehensive logging and monitoring on OPDS services; conduct threat hunting for signs of exploitation. Within 30 days: Contact vendor for patch timeline; evaluate alternative OPDS solutions; if patch becomes available, apply immediately after testing in isolated environment.

Opds Talon CVE-2026-26093

CRITICAL

Command Injection (CWE-77)

2026-02-20 prodsec@nozominetworks.com

Command Injection Opds Talon Owlcyberdefense

9.8

CVSS 3.1 · NVD

View

Attack ChainAIDerived

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

Access

Send crafted network request
Exploit

Inject malicious command in input parameter
Execution

Execute arbitrary system command
Impact

Achieve remote code execution

Vulnerability Assessment

Weakness	CWE CWE-77 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Command injection prevention 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	No special conditions — remote unauthenticated exploitation against Owl OPDS 2.2.0.4 default deployment with command injection vulnerability in request handling.
Impact	CVSS 9.8.
Exploit ScenarioDerived	Inject commands via crafted network request.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAI

Command injection in Owl OPDS 2.2.0.4. EPSS 0.29%.

RemediationAI

Update Owl OPDS.

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

CWE-77 command injection.

Know when Opds Talon gets its next vulnerability

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

NVD PRIMARY 9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

Improper Neutralization of Special Elements used in a Command ('Command Injection') in Owl opds 2.2.0.4 allows Command Injection via a crafted network request.

Executive ViewAI

Why It Matters

A critical remote code execution vulnerability (CVE-2026-26093) in Owl OPDS 2.2.0.4 allows unauthenticated attackers to execute arbitrary commands on affected systems with a CVSS score of 9.8. Organizations running this software face immediate risk of complete system compromise, data theft, and operational disruption. No patch is currently available, requiring urgent interim protective measures.

Business Impact: Severe

Compensating Controls

Implement Web Application Firewall (WAF) rules blocking command injection payloads (semicolons, pipes, backticks, $() syntax); restrict network access to OPDS service ports (typically TCP 80/443) to trusted internal networks only; disable Owl OPDS service if not operationally critical; run service with minimal privilege (non-root user); implement strict input validation at application layer if accessible; enable real-time monitoring and alerting for suspicious command patterns; consider running affected instances in isolated containers with restricted system calls.

Threat Intelligence Overview

EPSS Score

0.3%

Top 48% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

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 CRITICAL

CISA KEV No

Public POC No

EPSS 0.3%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

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.