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

CVE-2026-2333 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-2333?

Within 24 hours: Inventory all systems running Owl OPDS 2.2.0.4 and isolate affected instances from production networks if possible; implement network-level access controls to restrict inbound connections to OPDS services. Within 7 days: Deploy WAF rules to block malicious payloads targeting command injection vectors; establish monitoring and alerting for suspicious OPDS traffic patterns; brief incident response team on escalation procedures. Within 30 days: Evaluate upgrade paths to patched versions or alternative solutions; conduct security assessment of any affected systems for signs of compromise; establish vendor communication plan for patch availability updates.

Opds Talon CVE-2026-2333

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 to Owl OPDS
Exploit

Inject malicious command in input parameter
Execution

Execute arbitrary system command
Impact

Achieve full system compromise

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 default Owl OPDS 2.2.0.4 installations accepting network requests without input validation.
Impact	CVSS 9.8.
Exploit ScenarioDerived	Command injection.

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

AnalysisAIv1 – Mar 12, 2026

Command injection in Owl OPDS 2.2.0.4 — duplicate of CVE-2026-26093.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:04 CVSS 9.8

Duplicate command injection in Owl OPDS.

RemediationAI

Update.

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.

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 command injection vulnerability (CVE-2026-2333, CVSS 9.8) exists in Owl OPDS 2.2.0.4 that allows attackers to execute arbitrary commands through crafted network requests, potentially leading to complete system compromise. Organizations running this software face immediate risk of data breach, service disruption, and unauthorized access until remediation is deployed.

Business Impact: Severe

Compensating Controls

Implement network segmentation to isolate OPDS services; deploy Web Application Firewall (WAF) with command injection detection rules; restrict network access to OPDS ports (typically 80/443) using IP whitelisting; disable OPDS functionality if not operationally critical; monitor for exploitation attempts via log aggregation and SIEM; enforce strong authentication and API key rotation; consider disabling network-accessible features until patch is available. Monitor vendor advisories closely for patch release timeline.

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.