# wolfSSL Python module vulnerable to Improper Authentication

Advisory record · `GHSA-vj87-jj27-4h9c`

- **Identifiers:** `GHSA-vj87-jj27-4h9c` · `CVE-2025-15346` · `PYSEC-2026-575`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 29 Jun 2026
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `wolfssl` (PyPI): affected `<5.8.4.post0`; fixed in `5.8.4.post0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The wolfssl Python package (wolfssl-py) versions before 5.8.4.post0 do not fully enforce client certificates when verify_mode is CERT_REQUIRED. A client can omit a certificate during the TLS handshake and still be authenticated, bypassing mutual TLS client authentication. Upgrade to 5.8.4.post0 or later.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `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/AU:Y`, from CNA (wolfSSL)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 27th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-vj87-jj27-4h9c](https://github.com/advisories/GHSA-vj87-jj27-4h9c)
- [OSV: GHSA-vj87-jj27-4h9c](https://osv.dev/vulnerability/GHSA-vj87-jj27-4h9c)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-15346>
- <https://github.com/wolfSSL/wolfssl-py/pull/62>
- <https://github.com/wolfSSL/wolfssl-py/commit/b4517dece79f682a8f453abce5cfc0b81bae769d>
- <https://github.com/wolfSSL/wolfssl-py>
- <https://github.com/wolfSSL/wolfssl-py/releases/tag/v5.8.4-stable>
- <https://pypi.org/project/wolfssl>
- <https://github.com/advisories/GHSA-vj87-jj27-4h9c>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vj87-jj27-4h9c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vj87-jj27-4h9c/>. Everything for agents: <https://agentprime.io/llms.txt>.
