-
Notifications
You must be signed in to change notification settings - Fork 57
vonage-4.7.2-py3-none-any.whl: 2 vulnerabilities (highest severity is: 7.5) #250
Description
Vulnerable Library - vonage-4.7.2-py3-none-any.whl
Path to dependency file: /requirements.txt
Path to vulnerable library: /tmp/ws-ua_20260203151958_QLDRQL/python_VXNOQS/202602031519591/env/lib/python3.9/site-packages/pyjwt-2.11.0.dist-info
Vulnerabilities
| Vulnerability | Severity | Exploit Maturity | EPSS | Dependency | Type | Fixed in (vonage version) | Remediation Possible** | Reachability | |
|---|---|---|---|---|---|---|---|---|---|
| CVE-2026-32597 | 7.5 | Not Defined | 0.0% | pyjwt-2.11.0-py3-none-any.whl | Transitive | N/A* | ❌ | ||
| CVE-2026-25645 | 4.4 | Not Defined | requests-2.32.5-py3-none-any.whl | Transitive | N/A* | ❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2026-32597
Vulnerable Library - pyjwt-2.11.0-py3-none-any.whl
JSON Web Token implementation in Python
Library home page: https://files.pythonhosted.org/packages/6f/01/c26ce75ba460d5cd503da9e13b21a33804d38c2165dec7b716d06b13010c/pyjwt-2.11.0-py3-none-any.whl
Path to dependency file: /requirements.txt
Path to vulnerable library: /tmp/ws-ua_20260203151958_QLDRQL/python_VXNOQS/202602031519591/env/lib/python3.9/site-packages/pyjwt-2.11.0.dist-info
Dependency Hierarchy:
- vonage-4.7.2-py3-none-any.whl (Root Library)
- vonage_http_client-1.5.1-py3-none-any.whl
- vonage_jwt-1.1.5-py3-none-any.whl
- ❌ pyjwt-2.11.0-py3-none-any.whl (Vulnerable Library)
- vonage_jwt-1.1.5-py3-none-any.whl
- vonage_http_client-1.5.1-py3-none-any.whl
Found in base branch: main
Vulnerability Details
PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.
Publish Date: 2026-03-12
URL: CVE-2026-32597
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Origin: GHSA-752w-5fwx-jx9f
Release Date: 2026-03-12
Fix Resolution: pyjwt - 2.12.0
CVE-2026-25645
Vulnerable Library - requests-2.32.5-py3-none-any.whl
Python HTTP for Humans.
Library home page: https://files.pythonhosted.org/packages/1e/db/4254e3eabe8020b458f1a747140d32277ec7a271daf1d235b70dc0b4e6e3/requests-2.32.5-py3-none-any.whl
Path to dependency file: /requirements.txt
Path to vulnerable library: /tmp/ws-ua_20260203151958_QLDRQL/python_VXNOQS/202602031519591/env/lib/python3.9/site-packages/requests-2.32.5.dist-info
Dependency Hierarchy:
- vonage-4.7.2-py3-none-any.whl (Root Library)
- vonage_http_client-1.5.1-py3-none-any.whl
- ❌ requests-2.32.5-py3-none-any.whl (Vulnerable Library)
- vonage_http_client-1.5.1-py3-none-any.whl
Found in base branch: main
Vulnerability Details
Requests is a HTTP library. Prior to version 2.33.0, the function "requests.utils.extract_zipped_paths()" (which is used by "HTTPAdapter.cert_verify()" to load the CA bundle, often from the "certifi" package's zipapp structure) uses a predictable, non-unique filename (the basename of the file, e.g., "cacert.pem") when attempting to extract files into the system's temporary directory ("/tmp"). The vulnerable logic performs a check to see if the target file already exists in "/tmp" and re-uses the existing file if found, instead of securely checking the file's content or ensuring atomic, unique extraction. This allows a Local Attacker to pre-create a malicious CA bundle file (e.g., "/tmp/cacert.pem") before a vulnerable application (running with potentially higher privileges) initializes the "requests" library. Version 2.33.0 contains a patch.
Publish Date: 2026-03-25
URL: CVE-2026-25645
Threat Assessment
Exploit Maturity: Not Defined
EPSS:
CVSS 3 Score Details (4.4)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None