CVE-2026-35175: Security Vulnerability in Pypi
// Executive Summary
An authenticated user (using the auth_users plugin authentication method) could install a custom package even if this user is not superuser.
The CVE-2026-35175 vulnerability affects Pypi and represents a high-severity Security Vulnerability flaw with real-world consequences for organizations running affected versions.
Security Control Bypass
Exploitation may allow attackers to bypass security controls and gain unauthorized access to protected resources.
Data Exposure Risk
Sensitive organizational data may be exposed to unauthorized parties through exploitation of this flaw.
Compliance Violation
Successful exploitation can result in regulatory non-compliance under GDPR, HIPAA, PCI-DSS, or SOC2 frameworks.
Follow these steps to determine whether your systems are exposed to CVE-2026-35175:
Detection Checklist
- Identify all instances of Pypi deployed in your environment (on-premises, cloud, and containerized deployments).
- Check the version of your Pypi installation — vulnerable versions are indicated in the CVE advisory.
- Review access logs for anomalous request patterns consistent with Security Vulnerability exploitation attempts.
- Search for indicators of compromise (IOCs) including unexpected process spawns, unusual network connections, or modified configuration files.
- Run KENSAI's automated vulnerability scanner against your Pypi deployment to confirm exposure in minutes.
- Check your SIEM/IDS for alerts referencing this CVE or related attack signatures published by threat intelligence vendors.
Immediate Actions Required
- Apply the vendor patch immediately — update Pypi to the latest patched version as specified in the CVE advisory.
- If an immediate patch is not possible, implement temporary mitigations such as WAF rules to block exploit attempts.
- Enforce multi-factor authentication (MFA) on all accounts with access to the affected system as an additional defense-in-depth measure.
- Restrict network access to the vulnerable component using firewall rules, limiting exposure to trusted IP ranges only.
- Audit and rotate all credentials (passwords, API keys, tokens) that may have been accessible to an attacker if exploitation occurred.
- Enable comprehensive logging and alerting for the affected component to detect any ongoing exploitation attempts.
- Conduct a post-patch verification scan to confirm the vulnerability has been remediated before returning the system to production.
- Review related systems and dependencies that may be affected by the same vulnerability class.
What is CVE-2026-35175?
CVE-2026-35175 is a high-severity Security Vulnerability vulnerability affecting Pypi. It has a CVSS score of N/A and requires immediate attention from security teams.
How serious is CVE-2026-35175?
With a HIGH severity rating and CVSS score of N/A, CVE-2026-35175 represents a significant security risk. Organizations using Pypi should treat remediation as a high priority.
Is CVE-2026-35175 actively exploited?
Security researchers have published details about this vulnerability. Monitor CISA's KEV catalog and your threat intelligence feeds for exploitation status updates. Apply the patch regardless of current exploitation status.
How do I fix CVE-2026-35175?
The primary remediation is to apply the vendor-supplied patch for Pypi. If patching is not immediately possible, implement temporary compensating controls such as WAF rules or network access restrictions while the patch is scheduled.
Does CVE-2026-35175 affect my organization?
If your organization uses Pypi, you should assess your exposure immediately. Check the specific affected versions in the CVE advisory and run an automated vulnerability scan to confirm your exposure status.