Mercurial configuration injectable in repo revision when installing via pip
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: python-pip (Debian:11) 20.3.4-4+deb11u2; python-pip (Debian:13) 23.3+dfsg-1; python-pip (openSUSE:Leap 15.4) 22.3.1-150400.17.12.1.
- Severity is disputed: the assigning authority (CNA) scores it 5.5, NVD 3.3.
Low priority for now. Upgrade to python-pip (Debian:11) 20.3.4-4+deb11u2; python-pip (Debian:13) 23.3+dfsg-1; python-pip (openSUSE:Leap 15.4) 22.3.1-150400.17.12.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
When installing a package from a Mercurial VCS URL (ie "pip install hg+...") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "--config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.
- Published
- Oct 25, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-77
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.3
- CNA · PSF
- 5.5
- 2.2 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pypa | pip | cpe:2.3:a:pypa:pip |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pypa pipbefore 23.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.
Pip maintainers pip
- 23.3not affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | python-pip | before 20.3.4-4+deb11u2 | 20.3.4-4+deb11u2 |
| Debian:12 | python-pip | from 0 | — |
| Debian:13 | python-pip | before 23.3+dfsg-1 | 23.3+dfsg-1 |
| openSUSE:Leap 15.4 | python-pip | before 22.3.1-150400.17.12.1 | 22.3.1-150400.17.12.1 |
| openSUSE:Leap 15.6 | python312-pip | before 23.2.1-150600.3.3.1 | 23.2.1-150600.3.3.1 |
| PyPI | pip | before 23.3 | 23.3 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography-debuginfo | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography-debugsource | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-black | before 0:22.8.0-2.el9ap | 0:22.8.0-2.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography-debugsource | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-idna | before 0:3.7-1.el9ap | 0:3.7-1.el9ap |
+54
Same product
pypa: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-20225An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended32Monitor
- CVE-2019-20916The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition h31Monitor
- CVE-2013-1629pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which all29Monitor
Published before and after this one in the same product
- ← EarlierCVE-2013-5123Nov 5, 2019 · The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers25Monitor
- ← EarlierCVE-2021-3572Nov 10, 2021 · A flaw was found in python-pip in the way it handled Unicode separators in git references.23Monitor
- Later →CVE-2026-8643Jun 1, 2026 · pip can extract console_scripts and gui_scripts outside installation directory16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-pip | 23.3+dfsg-1 · Debian:13 | Package registry (OSV) |
| opensuse:python-pip | 22.3.1-150400.17.12.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:python312-pip | 23.2.1-150600.3.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| PyPI:pip | 23.3 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.7-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python-cryptography-debugsource | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography-debuginfo | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-cryptography-debuginfo | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-pillow | 0:10.3.0-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography-debugsource | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| suse:python-pip | 10.0.1-13.14.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:python-pip | 22.3.1-150400.17.12.1 · SUSE:Linux Enterprise Module for Python 3 15 SP4 | Package registry (OSV) |
| suse:python312-pip | 23.2.1-150600.3.3.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6 | Package registry (OSV) |
| suse:python36-pip | 20.2.4-8.15.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Paul Gerstereporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/622OZXWG72ISQPLM5Y57YCVIMWHD4C3U/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/65UKKF5LBHEFDCUSPBHUN4IHYX7SRMHH/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FXUVMJM25PUAZRQZBF54OFVKTY3MINPW/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KFC2SPFG5FLCZBYY2K3T5MFW2D22NG6E/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YBSB3SUPQ3VIFYUMHPO3MEQI4BJAXKCZ/
- mail.python.org/archives/list/security-announce@python.org/thread/F4PL35U6X4VVHZ5ILJU3PWUWN7H7LZXL/
- lists.debian.org/debian-lts-announce/2025/10/msg00028.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.