Is this vulnerability directly exploitable over the network?

Not by itself. Exploitation depends on a workflow where an attacker can provide pickle data that is scanned by Fickling and later deserialized or executed based on the scanner's "LIKELY_SAFE" classification. The actual network exposure depends on where and how pickle inputs are accepted.

What level of access does an attacker need to exploit this issue?

The attacker needs the ability to influence or supply pickle files that will be analyzed by Fickling and subsequently trusted by another component. This can occur via file uploads, API endpoints, shared artifact repositories, or any other channel that feeds into a pipeline using Fickling.

What is the safest general fix pattern for affected systems?

The most robust approach is to stop deserializing untrusted pickle data altogether and migrate to safer serialization formats. Where pickle cannot be removed, apply a strict allowlist of permitted types, sandbox deserialization, and update analysis tools so they treat dynamic resolution mechanisms like `pydoc.locate` and `ctypes` as dangerous.

Severity:

HIGH RISK

(7.8)

Insufficient Unsafe Call Filtering in Pickle Scanner Leading to RCE (CWE-184/CWE-502) in Fickling

CVE-2026-22608

Published:

Jan 9, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Unsafe Deserialization with Incomplete Security Filtering

CWE:

CWE-184;CWE-502

Impact:

Remote Code Execution via Bypassed Pickle Safety Scan

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Unsafe Deserialization with Incomplete Security Filtering

CWE:

CWE-184;CWE-502

Impact:

Remote Code Execution via Bypassed Pickle Safety Scan

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Insufficient Unsafe Call Filtering in Pickle Scanner Leading to RCE (CWE-184/CWE-502) in Fickling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare