Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15367: CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection') in Python Software Foundation CPython

0
Medium
VulnerabilityCVE-2025-15367cvecve-2025-15367cwe-77
Published: Tue Jan 20 2026 (01/20/2026, 21:47:09 UTC)
Source: CVE Database V5
Vendor/Project: Python Software Foundation
Product: CPython

Description

The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 08:13:06 UTC

Technical Analysis

CVE-2025-15367 is a command injection vulnerability identified in the poplib module of CPython, the official Python implementation maintained by the Python Software Foundation. The poplib module is used for interacting with POP3 email servers. The vulnerability stems from improper neutralization of special elements (CWE-77), specifically the failure to adequately sanitize user-supplied commands before processing. An attacker can exploit this by injecting newline characters into commands, which the module interprets as separators, allowing additional unintended commands to be executed. This can lead to command injection within the context of the application using poplib, potentially compromising the integrity of the system or application data. The CVSS 4.0 base score is 5.9 (medium severity), reflecting network attack vector, low attack complexity, partial confidentiality impact, high integrity impact, and no availability impact. Exploitation requires privileges (PR:H), no user interaction (UI:N), and no scope change. The vulnerability was reserved on December 30, 2025, and published on January 20, 2026. No known exploits have been reported in the wild. Mitigation involves rejecting commands containing control characters such as newlines to prevent injection of additional commands. No official patches are linked yet, so users should monitor Python Software Foundation advisories and consider implementing input validation or sandboxing as interim measures.

Potential Impact

The primary impact of CVE-2025-15367 is on the integrity of systems using the poplib module in CPython. Successful exploitation allows attackers to inject and execute additional commands, potentially altering application behavior or data. Although confidentiality impact is limited, the integrity compromise could lead to unauthorized actions, data corruption, or further escalation within the affected environment. The vulnerability requires high privileges, limiting exploitation to scenarios where attackers have some level of access, but no user interaction is needed, facilitating automated attacks. Organizations relying on Python for email processing or other services using poplib may face risks of unauthorized command execution, which could disrupt operations or lead to data integrity issues. The lack of known exploits reduces immediate risk, but the vulnerability's presence in a widely used language runtime means potential for future exploitation exists. The medium severity rating suggests moderate urgency for remediation, especially in environments processing untrusted input or exposed to external networks.

Mitigation Recommendations

To mitigate CVE-2025-15367, organizations should first apply any official patches released by the Python Software Foundation once available. In the absence of patches, developers should implement strict input validation to reject or sanitize commands containing control characters, particularly newline characters, before passing them to the poplib module. Employing application-level sandboxing or running Python processes with the least privilege can reduce the impact of potential exploitation. Monitoring and logging usage of the poplib module for anomalous command patterns may help detect exploitation attempts. Additionally, consider isolating email processing components from critical systems to limit lateral movement. Regularly update Python environments to the latest versions to benefit from security fixes. Educate developers and administrators about secure coding practices related to command injection and input sanitization. Finally, conduct security assessments and code reviews focusing on modules handling external input to identify similar injection risks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
PSF
Date Reserved
2025-12-30T16:06:42.288Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 696ff8c24623b1157c513cf2

Added to database: 1/20/2026, 9:50:58 PM

Last enriched: 2/27/2026, 8:13:06 AM

Last updated: 3/25/2026, 12:14:21 AM

Views: 119

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses