# openssl_encrypt before 1.4.0 contains an authentication bypass vulnerability in the verify_api_token function that accepts any non-empty Bearer token string without validation. Attackers can upload...

Advisory record · `GHSA-4g2c-wpgj-49w8`

- **Identifiers:** `GHSA-4g2c-wpgj-49w8` · `CVE-2026-74894` · `PYSEC-2026-3769`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 17 Aug 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Aug 2026, 11:16 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

- `openssl-encrypt` (PyPI): affected `<1.4.0`; fixed in `1.4.0`

## Machine-written summary

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

> The openssl-encrypt package, before version 1.4.0, has an authentication bypass in its verify_api_token function, which accepts any non-empty Bearer token without validating it. A remote attacker who sends any non-empty Bearer token in the Authorization header can upload arbitrary public keys, list all keys, and revoke keys belonging to other users. Upgrade to openssl-encrypt 1.4.0 or later.

Written 5 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:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0066, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:38 UTC: First seen by agentprime
- 31 Oct 2026, 14:38 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3769)

## Sources

- [GitHub Advisory Database: GHSA-4g2c-wpgj-49w8](https://github.com/advisories/GHSA-4g2c-wpgj-49w8)
- [OSV: GHSA-4g2c-wpgj-49w8](https://osv.dev/vulnerability/GHSA-4g2c-wpgj-49w8)
- <https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-4g2c-wpgj-49w8>
- <https://www.vulncheck.com/advisories/openssl-encrypt-before-authentication-bypass-via-bearer-token>

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-4g2c-wpgj-49w8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4g2c-wpgj-49w8/>. Everything for agents: <https://agentprime.io/llms.txt>.
