CVE-2026-16760

HIGH CVSS 8.8 PoC Available
Published: 2026-10-30
Modified: 2026-10-30
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-16760 is a high-severity vulnerability with a CVSS score of 8.8 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

In Trail of Bits fickling through 0.1.12, the _process_import() method in fickle.py adds an imported name to the likely_safe_imports set whenever the source module is present in sys.stdlib_module_names and the name is absent from the UNSAFE_IMPORTS denylist, without inspecting what the name resolves to or how it behaves. The OvertlyBadEvals analysis pass in analysis.py then unconditionally skips any call whose function name appears in likely_safe_imports, including calls that would otherwise be flagged as overtly dangerous. As a result, any callable reachable through a non-blocked standard library module inherits module-level trust regardless of its own behavior, and check_safety() returns LIKELY_SAFE with zero findings for pickle payloads that reach code execution or file write through such callables. Demonstrated primitives: dataclasses._create_fn, which passes an attacker-controlled function body to exec() and yields arbitrary code execution on Python 3.7 through 3.12 (the internal _create_fn function was removed in Python 3.13); mailcap.findmatch, which internally calls os.system() on a test command taken from an attacker-controlled caps dictionary, yielding arbitrary code execution on Python versions through 3.12 (the mailcap module was removed in Python 3.13); and readline.add_history() followed by readline.write_history_file(), which writes attacker-controlled content to an arbitrary filesystem path (POSIX platforms, where the readline module is available). fickling.load() chains check_safety() into pickle.loads() as an explicit security gate, so a LIKELY_SAFE verdict causes the payload to be deserialized and executed with the privileges of the victim process. The root cause is the inference of callable safety from module origin; it is independent of, and separately fixable from, the dotted __qualname__ resolution weakness tracked as CVE-2026-118938, which this advisory does not address. As of 2026-10-30 the three demonstrated modules were added to UNSAFE_IMPORTS on the vendor master branch (commit d011709) pending release; released versions through 0.1.12 remain affected, and the module-origin trust root cause persists, as demonstrated by the related CVE-2026-118938 remaining exploitable on that same build.

Attack Chain
1
Reconnaissance

Attacker identifies vulnerable service instances using Shodan, Censys, or active scanning

2
Initial Access

Attacker crafts malicious payload exploiting CVE-2026-16760 to achieve remote code execution

3
Execution

Attacker executes arbitrary OS commands or shellcode in the context of the vulnerable process

4
Persistence

Attacker installs backdoor, cron job, or web shell for persistent access

5
Lateral Movement

Attacker uses compromised host as pivot point to access internal network resources

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Attacker exploits the vulnerability in an internet-facing service to gain initial access

T1059 Command and Scripting Interpreter
Execution

Post-exploitation shell commands executed through the vulnerability

T1105 Ingress Tool Transfer
Command and Control

Attacker downloads malware or tools after gaining code execution

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
registry_key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\backdoor Persistence mechanism after successful RCE
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.
Quick Facts
CVE ID CVE-2026-16760
CVSS Score 8.8
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published 2026-10-30
Exploited No
CISA KEV No
PoC Available