PYSEC-2026-575
Vulnerability from pysec - Published: 2026-06-29 11:50 - Updated: 2026-07-01 20:23A vulnerability in the handling of verify_mode = CERT_REQUIRED in the wolfssl Python package (wolfssl-py) causes client certificate requirements to not be fully enforced.
Because the WOLFSSL_VERIFY_FAIL_IF_NO_PEER_CERT flag was not included, the behavior effectively matched CERT_OPTIONAL: a peer certificate was verified if presented, but connections were incorrectly authenticated when no client certificate was provided.
This results in improper authentication, allowing attackers to bypass mutual TLS (mTLS) client authentication by omitting a client certificate during the TLS handshake.
The issue affects versions up to and including 5.8.2.
| Name | purl | wolfssl | pkg:pypi/wolfssl |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "wolfssl",
"purl": "pkg:pypi/wolfssl"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.8.4.post0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.1.1",
"0.1.2",
"3.12.2.post0",
"3.13.0.post0",
"3.13.0.post1",
"3.14.0.post1",
"4.1.0.post0",
"5.3.0.post0",
"5.4.0.post0",
"5.5.3.post0",
"5.5.4.post0",
"5.6.0.post0",
"5.6.6.post0",
"5.7.2.post0",
"5.7.4.post0",
"5.8.2.post0"
]
}
],
"aliases": [
"CVE-2025-15346",
"GHSA-vj87-jj27-4h9c"
],
"details": "A vulnerability in the handling of verify_mode = CERT_REQUIRED in the wolfssl Python package (wolfssl-py) causes client certificate requirements to not be fully enforced.\u00a0\n\nBecause the WOLFSSL_VERIFY_FAIL_IF_NO_PEER_CERT flag was not included, the behavior effectively matched CERT_OPTIONAL: a peer certificate was verified if presented, but connections were incorrectly authenticated when no client certificate was provided.\u00a0\n\nThis results in improper authentication, allowing attackers to bypass mutual TLS (mTLS) client authentication by omitting a client certificate during the TLS handshake.\u00a0\n\nThe issue affects versions up to and including 5.8.2.",
"id": "PYSEC-2026-575",
"modified": "2026-07-01T20:23:12.060789Z",
"published": "2026-06-29T11:50:51.846296Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15346"
},
{
"type": "WEB",
"url": "https://github.com/wolfSSL/wolfssl-py/pull/62"
},
{
"type": "WEB",
"url": "https://github.com/wolfSSL/wolfssl-py/commit/b4517dece79f682a8f453abce5cfc0b81bae769d"
},
{
"type": "PACKAGE",
"url": "https://github.com/wolfSSL/wolfssl-py"
},
{
"type": "WEB",
"url": "https://github.com/wolfSSL/wolfssl-py/releases/tag/v5.8.4-stable"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/wolfssl"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-vj87-jj27-4h9c"
}
],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "wolfSSL Python module vulnerable to Improper Authentication"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.