CVE-2026-128136

Description

A flaw was found in NLTK. When deserializing data, its restricted pickle loader fails to block dangerous NumPy file input and output functions. An attacker can exploit this flaw by convincing a victim to load a crafted model file, allowing the attacker to read sensitive local files or create and overwrite arbitrary files on the system.

Statement

This vulnerability is rated Moderate rather than Important because exploitation requires local user interaction, specifically convincing a user or automated pipeline to load an untrusted model file. When processing untrusted machine learning assets with NLTK's transition parser, an attacker can bypass deserialization restrictions to read or overwrite local files with the privileges of the running application. Because the flaw cannot be triggered without feeding external, untrusted model files to the deserialization routine, typical automated environments that consume only verified internal models remain unaffected.

Mitigation

Avoid loading untrusted model files and execute model processing within an isolated sandbox.

Ensure NLTK deserialization routines only load verified, trusted model files from known sources. If untrusted models must be processed, execute the Python application inside an unprivileged container or sandbox environment with a read-only root filesystem and restricted directory permissions to prevent arbitrary file reading and modification.

Caveats: Isolating workloads or enforcing strict filesystem permissions may restrict application access to local storage and requires modifications to data ingestion workflows.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.1N/A6.1
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactLowN/ALow
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Application Data; Unexpected State

Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.

Availability

Technical Impact: DoS: Resource Consumption (CPU)

If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.

Other

Technical Impact: Varies by Context

The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform unauthorized actions, such as generating a shell.

Frequently Asked Questions

Want to get errata notifications? Sign up here.