CVE-2026-33164

libde265 is an open source implementation of the h.

Verified by Precogs Threat Research
Last Updated: Mar 20, 2026
Base Score
0UNKNOWN

Executive Summary

CVE-2026-33164 is a unknown severity vulnerability affecting binary-analysis, appsec. It is classified as Heap-based Buffer Overflow. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"The primary vulnerability vector is rooted in within Libde265, allowing flawed state management logic. A threat actor could leverage this oversight to trigger a denial of service state, crashing critical operational components. Precogs Binary SAST/DAST engine uncovers boundary violations in compiled software to block malicious interactions before they reach production."

Exploit Probability (EPSS)
Low (0.1%)
Public POC
Undisclosed
Exploit Probability
Low (<10%)
Public POC
Available
Affected Assets
binary analysisappsecCWE-122

What is this vulnerability?

CVE-2026-33164 is categorized as a critical Code Injection / RCE flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.17, a malformed H.265 PPS NAL unit causes a segmentation fault in ...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score0 (UNKNOWN)
Vector StringN/A
PublishedMarch 20, 2026
Last ModifiedMarch 20, 2026
Related CWEsCWE-122

Impact on Systems

Remote Code Execution: Attackers achieve arbitrary command execution within the context of the application server.

Privilege Escalation: Initial code execution can be exploited to pivot and elevate privileges across the network.

Persistent Backdoors: Attackers can bind reverse shells, modify source files, or inject persistent access mechanisms.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Remove Dynamic Evaluation Completely eliminate the use of dynamic evaluation functions (eval(), exec(), system()) on untrusted input.

2. Sandboxing If dynamic execution is an absolute business requirement, isolate the execution environment in tightly constrained, non-networked sandboxes (e.g., restricted WebAssembly or isolated containers).

3. Network Segmentation Restrict outbound traffic from the application server (egress filtering) to prevent reverse shell connections.

Vulnerability Signature

// Vulnerable Node.js Execution
const exec = require('child_process').exec;
const user_domain = req.query.domain;
// VULNERABLE: Injecting user input directly into system shell commands
exec('ping -c 4 ' + user_domain, (error, stdout, stderr) =\> \{
    res.send(stdout);
\});

// EXPLOIT PAYLOAD: precogs.ai ; cat /etc/passwd

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceNetwork packet or file input
VectorData exceeds the allocated buffer bounds during a copy operation on the heap
Sinkstrcpy(), memcpy(), or pointer arithmetic
ImpactMemory corruption, Remote Code Execution (RCE)

Vulnerable Code Pattern

// ❌ VULNERABLE: Heap-based Buffer Overflow
void process_data(char *input) {
    char *buffer = malloc(64);
    // Taint sink: copies without bounds checking
    strcpy(buffer, input);
}

Secure Code Pattern

// ✅ SECURE: Bounded copy
void process_data(char *input) {
    char *buffer = malloc(64);
    if (buffer != NULL) {
        // Sanitized boundary check
        strncpy(buffer, input, 63);
        buffer[63] = '\0';
    }
}

How Precogs Detects This

Precogs Binary SAST engine explicitly uncovers memory boundary violations and unsafe memory management functions in compiled binaries.\n

Related Vulnerabilitiesvia CWE-122

Is your system affected?

Precogs AI detects CVE-2026-33164 in compiled binaries, LLMs, and application layers — even without source code access.